Resolved by thetechguru!
I am having problems connecting to 2 EZB's at the same time. I have 2 EZBv4's on my InMoov robot. Whichever v4 I turn on first it will connect to but not the other.
I have set the static IP's for both controllers into my router (Asus RT-N12B1) and when I scan the router to see the connected clients, it will only show the first controller that was turned on. I have my router 6 ft from the controllers and my computer is connected to the router with a cable. I am very familiar with setting up the v4's in client mode so that is not an issue.
I have in the past been able to connect to both at the same time, however, I had to shut everything down and now I can't them both to connect again. I have reset the controllers and started all over again but no luck.
Very frustrated! Thanks
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