Yeah - it's just some routers. The module does adhere to the dhcp rfc, but many network hardware does not - so some people like Jack run into this problem. Thankfully they released a new firmware that is available for download in the Software section of this website under the Open IoT link.

It seems no one with a dlink router has the issue. It all has to do with how fast the router responds to a dhcp request. If the ezb doesn't see a response fast enough, it responds itself. Would not be bad unless you want static ips, but it also doesn't supply the dns, so other essentially lose their internet access (they would still work for ip routing, but no name resolution).

DJ, are you saying the new firmware on the IoT page already fixes the issue so I just need to load it and don't need to modify it? I'll test that tonight. I may try to play around with some modifications too.

Alan

OK, I got the PIK programmer working.

Note to anyone else, the header supplied with mine did not fit tightly in the holes in the EZ-B. I had to hold onto it and push it to the side to make sure it had a solid connection to the EZ-B throughout the programming time. A little scary, since I imagine it would be easy to brick if it failed part way through).

I changed the SSID, and also figured out that it changes the MAC address and figured out how to change it back.

I haven't figured out how to turn off DHCP (either in client or AP mode) yet, and I haven't tested to see if the new firmware already fixes the issue in client mode. I need to reconfigure some things on my network to test that and my wife is using the Internet tonight, so I can't do that testing until tomorrow at the earliest.

I do see from the Blue-giga documentation that I can add a switch to the web config page to turn DHCP on and off, so if it isn't fixed and I can't figure out how to force it off just in client mode, I can add the switch to the web page, just need to figure out how the current page it written (and I am hardly an HTML wizard unfortunately) to add a check box to turn it on and off.

I think it is probably possible to do static IPs on your network with the SSID and password pre-configured, but I haven't quite figured that out either.

Alan

Would help if I read the changelog.

Quote:

2015-10-31-00

• Totally disable DHCP when in station mode.

So, looks like just loading the new code does the trick.

@jackphilips1953, it was pretty easy to do, and the programmer is cheap, but if you want some help, send me an email so we can discuss details offline (my email is in my profile). I am thinking you could mail me your EZ-Bs (either one at a time or all at once) and I could program them for you and mail them back. Alternatively, I can loan you my PIK once I am done with it if you are up to doing it yourself.

@DJ, Recommendation for the instructions.txt would be to also change the MAC address, not just the SSID. Otherwise users with multiple EZ-Bs could have a new problem. It was fairly obvious to me where and how to change it, but it might not be to everyone.

Alan

Thanks for the help. I will look into reprogramming as per you details above.

This is something should have had been addressed when introduced.

Especially when you have 2 or more V4s on the same wireless network that is not used for a router to the internet.

My modem and router in basement and I have to have a Access point with DHCP turned OFF for me to able to use throughout the house located above ground.

Of coarse when the V4s come up and 2 are on the same wireless they will go to the first DHCP they find which is probably the one on the wireless.

Also hopefully this will be addressed in the update for the V4 and included in the V5s.

@jackphillips1953 1 or 2 people who suffer from this is hardly a need for a redesign.... but @DJ being the consummate, accommodating guy that he is decided to do something about it anyway.... If it were me with your problem I would not waste any energy complaining about it but instead do something about it myself... That's just me though... To me it is such a minor issue in that it is easily solved by a cheap router update (dlink) (instead of fumbling with reprogramming and risking "bricking" your wifi chip)... just my opinion, however...

It wasn't addressed on release because EZ-Robots didn't know it was happening. It doesn't happen with their Dlink routers because their DHCP servers respond faster than the EZ-B.. If you look at the other thread, I had a knock-down/drag-out with DJ to get him to see that it was actually happening, and then it took months for Blue-Giga (the chip vendor) to get back to him with the root cause. (similar to what you did, I used wireshark to figure out what was going on).

This is kind of typical for first release consumer electronics. You don't know what you don't know, but you learn and make it better. The new comm board currently being developed uses a different chip and doesn't have this issue.

Alan

Hi,

Thank techguru for response. I can understand that have manufactured and sold products in the past. You really do not know sometimes until you get in the field some problems.

Hey Richard .. is probably a bigger problem than you think and I am not knocking down anyone. I was not wasting y energy and I found out I was not alone and what I discovered was true. If these problem are not brought up then how can they be fixed?

It has absolutely nothing to do with Linksys or Dlink routers so stop that. I also swapped 3 different Access points with the same results.

I have over 20 other devices on this network with absolutely no issues connecting.

No ones whining just trying to determine how to handle a complex issue.

BTW- If EZ wants this to go big time with industrial applications possibly, instead working with just toys, a problem like this need to be addressed properly. Since this is the way they want to handle issues on a community board and it bothers you, talk to them.

I would have had preferred to keep this private anyway.

Good luck with your project.