- Mon Sep 05, 2016 3:03 am
#54498
Hi,
First time posting here so apologies if this is the wrong forum. I found a more specific one but I didn't have permissions to post.
For about a year I have had four NodeMCU ESP8266 boards (like this https://shop.pimoroni.com/products/node ... opment-kit) running on my network. Three of them connect to my "main" wireless access point which is also my ADSL router. The other ESP8266 connects to a wireless access point in my garage which, in turn, is connected via Ethernet cable to the main ADSL router/access point.
Obviously I also have other devices (phones, laptops, TVs, etc) connecting to the same ADSL router via WiFi or via RJ45 cables.
That's all been working fine.
A couple of weeks ago I decided to purchase a new ADSL router and access point - the Belkin N300.
Like most routers this has a web based admin system which you can access by pointing your web browser to 192.168.x.1 (in my case I've configured it so as x = 1).
I found that after using it for a while and going through the various config steps, it would suddenly decide not to allow connections to the web interface anymore. The only way to fix it was to do a factory reset. But then at some point during the setup process it would decide to block connections to the admin system again.
I tired a firmware u/g on the router and that made no difference.
Eventually I managed to get it all configured as I wanted it before it kicked me out of the admin system. And it all worked ok but it obviously wasn't ideal because if I wanted to change any settings in the future I wouldn't be able to log in to do so.
Belkin support suggested I swap the router for a replacement one, which I did. And the new router had the same problem.
This weekend I did some more testing and eventually proved that the admin interface remains accessible until the point where any one of my ESP8266 boards connects to the network. As soon as that happens, it is impossible to connect a web browser to 192.168.1.1 (it just sits there with a blank screen in the browser and eventually times out). But if I turn off the ESP8266 boards, and then reboot the router, the admin interface becomes accessible again.
All of the ESP8266 boards case the same problem - even the one that is in the garage and so not directly connecting to the Belkin access point.
The ESP8266 boards all run Arduino sketches that do things like connect to WiFi, connect to an MQTT broker, and then receive or publish various MQTT packets for things like temperature sensing and turning lights on and off using an RF module.
I tried switching off the MQTT broker so as the ESP8266 devices didn't even get as far as broadcasting anything, but that made no difference.
It literally does seem to be the mere act of them connecting to the network which brings down the admin interface on the Belkin router.
Does anyone have any ideas what could be causing this please or how I might go about fixing it?
I've spoken to Belkin support again about this and they didn't have any immediate ideas. At their request I'll be sending them a link to this post so they have a record of the full problem description.
Thanks in advance.
David.
First time posting here so apologies if this is the wrong forum. I found a more specific one but I didn't have permissions to post.
For about a year I have had four NodeMCU ESP8266 boards (like this https://shop.pimoroni.com/products/node ... opment-kit) running on my network. Three of them connect to my "main" wireless access point which is also my ADSL router. The other ESP8266 connects to a wireless access point in my garage which, in turn, is connected via Ethernet cable to the main ADSL router/access point.
Obviously I also have other devices (phones, laptops, TVs, etc) connecting to the same ADSL router via WiFi or via RJ45 cables.
That's all been working fine.
A couple of weeks ago I decided to purchase a new ADSL router and access point - the Belkin N300.
Like most routers this has a web based admin system which you can access by pointing your web browser to 192.168.x.1 (in my case I've configured it so as x = 1).
I found that after using it for a while and going through the various config steps, it would suddenly decide not to allow connections to the web interface anymore. The only way to fix it was to do a factory reset. But then at some point during the setup process it would decide to block connections to the admin system again.
I tired a firmware u/g on the router and that made no difference.
Eventually I managed to get it all configured as I wanted it before it kicked me out of the admin system. And it all worked ok but it obviously wasn't ideal because if I wanted to change any settings in the future I wouldn't be able to log in to do so.
Belkin support suggested I swap the router for a replacement one, which I did. And the new router had the same problem.
This weekend I did some more testing and eventually proved that the admin interface remains accessible until the point where any one of my ESP8266 boards connects to the network. As soon as that happens, it is impossible to connect a web browser to 192.168.1.1 (it just sits there with a blank screen in the browser and eventually times out). But if I turn off the ESP8266 boards, and then reboot the router, the admin interface becomes accessible again.
All of the ESP8266 boards case the same problem - even the one that is in the garage and so not directly connecting to the Belkin access point.
The ESP8266 boards all run Arduino sketches that do things like connect to WiFi, connect to an MQTT broker, and then receive or publish various MQTT packets for things like temperature sensing and turning lights on and off using an RF module.
I tried switching off the MQTT broker so as the ESP8266 devices didn't even get as far as broadcasting anything, but that made no difference.
It literally does seem to be the mere act of them connecting to the network which brings down the admin interface on the Belkin router.
Does anyone have any ideas what could be causing this please or how I might go about fixing it?
I've spoken to Belkin support again about this and they didn't have any immediate ideas. At their request I'll be sending them a link to this post so they have a record of the full problem description.
Thanks in advance.
David.
