Network problems after firmware upgrade

[svd]

I've recently purchased an IO-204 and have been using it connected via a network bridge on my Vista laptop.  This took a bit of sorting, but eventually I managed to get it to work by making the bridge IP static.

I've now upgraded the module firmware to V4.2 and it works as expected when plugged directly into my router, but it no longer works on the laptop network bridge.  The on board display stops at 1.  Does this mean that DHCP has failed, and is this an known issue in the lastest firmware?

Any comments or help would be appreciated.

Steve

[wlbrycemt]

I also upgraded to 4.2 yesterday. My IO-204 is stuck on #1. I did a full power reset of the 204 and it still got stuck on #1. Worked fine till I did the upgrade, the 204 is hard-mounted is a ugly spot to get to, so Hope the fix is easy.

I will now try a full network reset, but seems strange that I had no problem until the firmware upload.

Thanks

Logan

[iobridge]

We fixed a lot of address issues so it could work using a Mac as a "bridge" so you could connect a cord directly to the Ethernet interface on a Mac. It also works on Windows up to Windows XP. Visit and 7 changed how they did bridging and it's not obvious on how to make it work on those.

There are some tricks though.

The IO-204 can have an address set. If you can get it connected somehow to a network, you can get the IP address of the module by pressing the link button 3 times in a row.

Then you can "telnet" to it via the command prompt or a command shell.

In order for telnet to work, you hold the link button until the display flashes.

From the command prompt type, "telnet [ip]" and hit enter.

From there you can change the IP, subnet mask, and default gateway.

[svd]

Thanks for the comments.  I've tried running the module on an XP machine with a network bridge, but I still have the same problem since upgrading the firmware - the module stops at '1'.  Pressing the link button 3 times reports an IP of 169.254.19.77 - presumably because it has failed DHCP.

I've checked the operation of the network bridge on the Vista and XP machines and they are both working ok.  The iobridge worked on both Vista and XP before I upgraded the firmware, so I can only assume that the problem is down to the new firmware?

Thanks
Steve

[wlbrycemt]

Uh, Hmmm  Mine is still broke. Will crawl into the space tonight and see what the IP is reported as. Will check for the 2nd time that the Internet is working at the port the 204 in plugged into.

I also think it is some firmware bug.

Thanks

Logan

[svd]

Hi Logan

Sounds like you have exactly the same problem as me.  Can you plug your 204 network cable directly into your router?  My 204 still works ok if I do that - it just fails to work on the network bridge.

Steve

[wlbrycemt]

Hi Steve

Yes, when the assembly that contained the 204 was on my bench and connected to a 10/100 hub off my router and it worked fine. I then did the firmware update and tested the unit, all was good.

I then did the install and connected the 204 to the wireless bridge, and it now does not work.
Still stuck on "1". I can ping the bridge and before I installed the 204 I connected to the internet via a laptop off that bridge so I know the connection works.  I added the 204's MAC address to my whitelist so Im sure it is not getting blocked.

This network allows for full management, (www.meraki.com) and I can see all devices and network use including Ip, and MAC.  The network showed the 204 before the firmware upgrade.

I am thinking it is some type of DHCP issue with the 204.

Logan

[svd]

Hi Logan

Yes, I'm sure it's a DHCP problem.  My 204 has a default IP of 169.254.19.77 and the fact that it never progresses to '2' means it's failing to obtain a dynamic IP.

Perhaps someone from ioBridge could comment?

Steve

[iobridge]

What kind of network bridge do you have?

We will look into it. Resolving the bridge on the MAC might interfere with traditional DHCP requests. There are 3-4 ways to do DHCP, I think we have 3 of them covered to make it compatible with the majority of DHCP servers. We find stuff every day that has a bit different here and there to make the DHCP request different. We have products like the SlingBox that have the same issues. The Sling only support one way of DHCP and fails on wireless bridges as well.

If we know what you have we can analyze the requests and see what bit we need to change.

[wlbrycemt]

The 204 worked when it was running the 3.? firmware. So, if possible we would go backward and move back to version 3.?

I have a programmer that is compatable with your processer and the flash connection on your board.

As stated above we use network gear supplied by Meraki, this is a multipoint mesh routing network. We have several other DAQ systems running on this network without problems.

Something in the 4.2 firmware is having a problem, if need be I can send you a node to test with.

I’m sure Steve will share is with you also.

Thanks

Logan

[jason]

DHCP issues are frustrating.  Fixing compatibility bugs for some users just create new bugs for other users with different hardware.  We were hoping the addition of the static IP option would help on "difficult" systems.

Is there any chance you can provide a Wireshark capture of the failed DHCP negotiation? 

It is possible to downgrade your IO-204 if it comes to that.

[wlbrycemt]

Thanks

I will download wireshark and run it on the hub the 204 is on. What test/screen shot do you want me to run with wireshark?

The program has a bunch of options.

Thanks

Logan

[jason]

Actually, I think a switch will work.  The DHCP packets are broadcast UDP, so the other ports on the switch will see the packets.

Can you also capture a successful DHCP negotiation?  You can do this by plugging in a laptop that doesn't seem to have trouble getting an IP address.  This way we can compare the two.  

[svd]

Jason

Just to confirm - the upgrade to 4.3 cures the problem with my Vista network bridge 

Many thanks.

Steve