Thank you for letting us know about the problem. LED should not behave this way. I will look into this problem and let you know about it quickly.
I have Tomato build 1.25 (3/30/09) running on a WGR614L set to Client Bridge Mode. So far, things are running fine but I notice something strange with the front LEDs that I'm curious about.
1) The orange/yellow check-mark indicator LED always remains lit.
2) The wireless indicator LED remains off even though the unit is communicating wirelessly. Even on a prior Buffalo router I had which also ran Tomato set to Client Bridge, the wireless indicator LED was lit letting you know the unit was communicating over the network.
I don't know if it's supposed to be this way or not but I thought I would ask.
I have tested Wireless LED and it is working fine. This LED should be on after board is booted and it will be blinking whenever packet is transmitted through that interfaces.
In my case it is working fine.
How do you test that wireless LED functionality ?
After noticing that the wireless LED was off, I tried pulling up a few web pages from the PC connected to the WGR614L and it worked fine. As I pulled up different web pages, I was looking to see if the wireless LED was on or even blinking to indicate that any packets were being sent and it remained off. Is the wireless LED even supposed to be on when the unit is configured as Client Bridge? I had a Buffalo router running Tomato which was also configured as Client Bridge and it's wireless indicator always flashed whenever packets were sent/received. Not sure what's going on with the WGR614L. I'm also curious about what's going on with the yellow check-mark LED and why it always remains lit.
Wireless LED should be on irrespective of its mode (AP or Client). It does not even depend on content of the packet. Whenever packet is transmitted through the wireless interface, corresponding LED should blink.
Check-mark LED is the test LED. It always remain yellow (at least in my router, it is true).
Well on this WGR614L the wireless LED remains off during Client Bridge (Ethernet Bridge) mode. I can deal with the test LED remaining on although it would be nice to have it turn off to let you know that the boot process is done like the netgear kernel seems to do. With it remaining on, it looks like the kernel crashed.
I'm running DD-WRT v24-sp2 mini SVN 12307 in client bridge mode on a Wgr614L and the LEDs behave as you'd want them to. The test LED turns off after boot, and the wireless LED indicates activity and connection to the AP. The Tomato build you have probably has some (minor) bugs regarding LED control.
This build of Tomato is just too buggy so I'll be reverting back to DD-WRT (as much as I despise using DD-WRT) on the WGR614L for now. =(


RSS
