This problem is related to previous post about "One PC discovered... other not".

I upgraded three WRT54GS routers with no problem (Two V2.0, one V2.1).  Upgrade process proceeded normally, and everything worked when upgrade was complete. 

I then upgraded two WRT54GS V1.0 units, and experienced identical DHCP problems with both of them.  The upgrade process appeared to go normally; however, I found that when I setup the router with node name and password, and then rebooted, the DHCP function stopped working.  The DHCP screen showed no current DHCP leases.  Both routers refuise to talk to anything plugged into the LAN ports... to include the PC used for the  upgrade (using  USB to Ethernet adapter), a tablet (also using a USB to Ethernet adaptor), an ATA (reflashed BasicTalk Grandstream), and an IP Camera.  The PC used for node control posted an error message stating "connection has little or no connectivity". 

I re-flashed one of the problem routers with the V2  upgrade firmware, communicating with it through another node... and that process appeared to work OK; however, result was the same.  As soon as I rebooted following entry of node name and passowrd, the LAN ports stopped working. I could still log into the node from other nodes, but not from any client connected to the LAN ports.

I tried to configure DHCP Address Reservations manually for one of the V1.0 routers by plugging in the Name, IP address, MAC address, etc for an ATA and a Camera... and the router accepted the manual DHCP reservations; however, router posted an error message saying "Configuration saved. However, problem with port setup."  Clients could still not communicate with router via the LAN ports.

It appears the V. 1.1.2 firmware is not yet compatible with the WRT54GS v1.0 routers.

Bill WA8APB

Thank you for confirmation on the WRT54GS, this model of the hardware seems to be the only model not affected by the issue with your 2.0 and 2.1 report and a previous V4 report. Your report that a WRT54GS V1 doesn't work is also interesting and let's is know it's not the entire WRT54GS line that works.

A fix will trigger a new version number, one should not expect us to slip fixes under a version that has already been released.

Per BBHN->ticket:55 this has been traced to a flaw in the on board Linksys switch module that shows itself under certain circumstances, Circumstances that just happen to be present in the 1.1.x releases to date.  We do not have the ability to bug fix the switch itself because it is a closed module that just so happens to be inside the same plastic case of the router.

Hi guys,

I've only recently discovered HSMM & have just bought my first router, a WRT54GS v1.0

I've flashed it with v1.12 firmware & it connects via LAN just fine.  I can't vouch for any of the wireless functionality as there's no-one else within miles of me on the mesh-map.  :(

According to the Wikipedia entry for the WRT54G family, the GS v1.0 had serial numbers beginning CGN0 & CGN1... mine begins CGN1... maybe the bug you mentioned was fixed after the CGN0 models?

How do the s/ns begin on your two GS routers, Bill?

73,

Mike

M0MLM

Hi Mike:

Serial numbers for my v1.0 affected routers are:

CGN10D345726 and CGN10D707820.

Those being the same serial number sequence as your units.... which loaded v1.1.2 successfully using (presumably) the "firmware for a non-mesh wrt54gs......

That makes me wonder if there is a difference between using the "upgrade" firmware (listed as "upgrade an existing mesh node") vs. installing the model-specific firmware (listed as "firmware for a non-mesh wrt54gs")  used to install Hamnet from scratch on a stock WRT54GS.

Bill WA8APB

Please keep in mind per BBHN->ticket:55

It only occurs under a specific set of circumstances. Part of the dependency is also on what the internal chips are on the device (laptop,camera, desktop, etc) being used.  It takes a very specific set of circumstances for this to occur. Unless you have a proven "doesn't work" you don't have a "it does work on this version" result because you may not have all the conditions that are needed for this issue to occur.

As for differences in firmware files: negligible, the differences are around telling the router "it's safe to load this firmware" not about any function.

If this will help the discussion... I have two nodes, a WRT54GS v1 and a WRT54G v3. I upgraded both to BBHN v1.1.2 using my home PC, and both of them come up on it and work just fine. However, the GS is used in my shack and is connected to a repurposed HP Compaq t5000 Thin Client running Windows CE .NET 4.2 as a dedicated terminal. With release 1.0.0 the GS and the t5000 worked together beautifully; now after the 1.1.2 upgrade, they won't talk to each other. But, if I connect the G to the thin client it works just fine on 1.1.2, so there's definitely something different in the GS that's keeping it from working exactly like the G. I really would like to get this resolved; I want to take advantage of the extra memory in the GS to support applications, but maintain the direct access to it using the thin client.