I'll test tonight or tomorrow at the latest just to confirm nothing broke in the last release.

Alan

OK, there is something strange, but it isn't in the EZ-B software.

I have 2 EZ-B's, and I have them both set with their MAC addresses reserved in my router.

One gets IP address 192.168.1.105 and the other gets 192.168.1.106.

Whichever one boots up first successfully gets its address. whichever one boots up second gets 192.168.1.2, doesn't show up in my DHCP client list (I found it using the ARC find EZ-B function) and the router log shows this set of errors:

201	Dec 5 19:05:10	DHCP	INFO	DHCPS:Send NAK
200	Dec 5 19:05:10	DHCP	INFO	DHCPS:Wrong Server id or request an invalid ip
199	Dec 5 19:05:10	DHCP	INFO	DHCPS:Recv REQUEST from 00:07:80:01:07:C8
198	Dec 5 19:05:10	DHCP	INFO	DHCPS:Send OFFER with ip 192.168.1.105
197	Dec 5 19:05:09	DHCP	INFO	DHCPS:Recv DISCOVER from 00:07:80:01:07:C8 

if I reverse the startup order, it is the MAC of the other EZ-B and the address of 192.168.1.106 which is offered and refused.

My router is a TP-Link Archer C8 if that makes any difference.

I did a further test. I removed the IP address reservations by MAC address, rebooted my router and tried again. Now the only limit is that my DHCP server starts with addresses starting at 100.

Again, the first EZ-B to start got an address from the DHCP server (192.168.1.105, since I have some other devices that had leases, either permanent, or that grabbed them first for 100-104), and the second one rejected the offer of 192.168.1.106 and came up as 192.168.1.2.

Going to try one more time, but setting my router to start handing out addresses at 192.168.1.2 and see how the EZ-Bs respond.

More to follow.

Alan

Further testing temporarily delayed until my wife is done with the internet so I can reboot the router :)

Alan

Still not working for me either. However, I have discovered, that now that I have my computer hardwired to my router, I can connect to one v4 in Client mode and 2 other v4's in AP mode at the same time. And still be connected to the Internet.

I suspect it may require a (at best) a firmware update. They are definitely not correctly negotiating DHCP, but I would need a wireless sniffer or a router with more verbose logging to see exactly what is happening, and even then, wouldn't be able to fix it, just provide more data to EZ-Robot to work with.

What I want to test though is whether there is a number range where they will except permanent address assignment or negotiate DHCP correctly and a range where they won't, which is why I need to reset the router to give out lower range IP addresses. My wife is chatting with a friend, so it may be a while (and maybe tomorrow since it has been a long day and I kind of want to go to bed soon).

Alan

That's weird.... I was able to have 2 ezbs connected at once... As you guys know I have limited network knowledge so I probably accomplished this by accident... LOL.... I gave all my ezbs static IPs..... So what I did was type in manually in the connection control the IP addresses of the two ezbs and connected that way... They both stayed connected... If I use the scan tool instead to look for the second ezb it would either disconnect the first one or not even find the second one at all....

It is definitely an issue with the final octet and with DHCP having gaps in available IPs vs assigned IPS.

I changed my server to start handing out addresses beginning with 2 instead of 100. Both EZ-Bs successfully negotiated DHCP with no logged errors. One got address 2, and the other got address 3. (my other running computers kept their addresses over 100 because their lease had not expired during the reboot, and two of them have permanently assigned addresses).

I then set those as the reserved addresses, and could still reboot in either order and they would keep the addresses.

However, when I assigned 5 and 6 instead, again, only the first booted would get the assigned address, and the second would fail the negotiation and would take address 2.

Setting the reservations back to 1 and 2 and it worked again, with no errors in the logs regardless of the boot order.

I also discovered they are doing some kind of interaction with each other because while testing the batteries got low on one of the devices and it kept disconnecting and reconnecting to the network. Once I unplugged it to change the batteries, the other EZ-B immediately disconnected from the network and needed to be restarted to connect.

I may try to set up Wireshark to sniff the network (not sure if any of my laptops have WNIC capable of network sniffing. I used to have one, but it was 802.11g only) just because I am curious about what interaction is occurring, but for now the simple solution is to set your router to start handing out addresses a the lowest possible octet, and reserve the lowest possible IP addresses for the EZ-Bs and they will work with reserved addresses.

Alan

Oh, one other test. I reset the DHCP server to hand out unreserved addresses starting at 100 (I want it there for reasons), but left the EZ-B reservations at 2 and 3. They still successfully negotiate their reserved addresses without error.

Alan'

I've been able to connect to two esb's for many, many months with no issues. At first I had many problems but once I bought a newer router and assigned static IP's all that cleated up.

I haven't restarted my router or changed much since then however. I haven't installed any ARC updated in months either. I have noticed that I'll have conflicts with other devices with static IP's on my network when my EZB's are connected. Then sometimes those other device won't connect. Example would be my ipod. If I connect to the two EZB's first the ipod usually can't connect to the network. My wife has problems with some of her devices connecting to our network also. I haven't looked for help on this as I was thinking it was a conflict with the way I have my static IP's listed. If I redo the static IP's for the non connecting devices that seems to clear it up. However I just mention this to maybe illustrate that there may be an DHCP handling issue somewhere.

My suspicion is that the EZ-Bs are still running DHCP, or at least sending some DHCP messages when they are in client mode, which would confuse each other and could confuse other devices on the same network.

Akan

I haven't got this totally solved but I have things working OK for now. Thanks for everyone's comments.

I still plan on setting up a sniffer as soon as I have some time to see what is causing this. I also want to set the EZ-B's to "n only" and see if they still exhibit this weird behavior.

Alan

I finally got the wireless sniffer working, and I can confirm that in client mode, the EZ-Bs are still acting as DHCP servers and confusing additional EZ-Bs on the network when they start up. It isn't a major issue if you don't have your router assigning permanent/reserved IP addresses by MAC address, or if the assigned addresses are the lowest available addresses on the network (ie, last octet 2-5) but if you assign addresses above that, only the first EZ-B to boot will get the correct address.

They also confuse my computers that use 802.11n WiFi if the computer is started after the EZ-B. The computers are unable to get addresses at all until I shut off any running EZ-Bs so that the computer can get its address from the router instead. (the computers with 802.11ac wireless don't see the additional DHCP servers so are not effected).

This is a major networking flaw. It is a very bad thing to have multiple DHCP servers on a network. Hopefully this is something that DJ can fix with a firmware update.

Alan

Where do we use 192.168.1.2 ?

@stha2232 You are responding to a year old thread for a problem that has long since been resolved unless you own an old EZ-B. Might be better to post your question with more details of what you are asking as a new thread.

Alan