Problem with Broadcast SSID on Client Bridge
Posted: Thu Oct 07, 2010 4:50 pm
Hey all!
First, I want to thank eric and everybody else who may be involved with the Gargoyle firmware. I really appreciate all your hard work and think it's the most user-friendly third-party firmware I've used, and I have migrated most of my wireless routers to it (from DD-WRT and Tomato)
I have a small problem, however. I am using a Linksys WRT54GL router running Gargoyle 1.3.5 as a wireless bridge, and I would like it to broadcast a different SSID from the main one, which appears to be one of the features.
The bridge works when I plug my computer into the wired ethernet port of the router, and I see the SSID show up in the wireless network list, but I can't connect to it. I have the same password and other settings configured to match the original wireless network, but it still refuses to let me connect on the rebroadcast SSID.
I saw another thread mentioning what seems to be this same problem, but it was from back in May and referenced the 1.2.3 firmware, so I didn't know if the issue was fixed or if I am doing something wrong.
Any help or insight would be appreciated. Thanks!
First, I want to thank eric and everybody else who may be involved with the Gargoyle firmware. I really appreciate all your hard work and think it's the most user-friendly third-party firmware I've used, and I have migrated most of my wireless routers to it (from DD-WRT and Tomato)
I have a small problem, however. I am using a Linksys WRT54GL router running Gargoyle 1.3.5 as a wireless bridge, and I would like it to broadcast a different SSID from the main one, which appears to be one of the features.
The bridge works when I plug my computer into the wired ethernet port of the router, and I see the SSID show up in the wireless network list, but I can't connect to it. I have the same password and other settings configured to match the original wireless network, but it still refuses to let me connect on the rebroadcast SSID.
I saw another thread mentioning what seems to be this same problem, but it was from back in May and referenced the 1.2.3 firmware, so I didn't know if the issue was fixed or if I am doing something wrong.
Any help or insight would be appreciated. Thanks!