Broadcast SSID diff than Joined SSID in Repeater Bridge

If your problem doesn't fall into one of the other categories, report it here.

Moderator: Moderators

Post Reply
nchall
Posts: 31
Joined: Thu Dec 02, 2010 2:42 am

Broadcast SSID diff than Joined SSID in Repeater Bridge

Post by nchall »

1.3.8 on WRT54GS v1. Mostly working great, but in client bridge configuration I am broadcasting a different ssid than the one I joined. Clients can get on the internet wired, but are unable to join ssid2 wirelessly (the broadcasted ssid). Any idea why this would be happening? Using WPA2 AES.

User avatar
DoesItMatter
Moderator
Posts: 1373
Joined: Thu May 21, 2009 3:56 pm

Re: Broadcast SSID diff than Joined SSID in Repeater Bridge

Post by DoesItMatter »

Just for some simple testing

Leave the security as open

Do some very simple ssid - like TEST

Also enable wireless client isolation
(that way if someone does happen to join your network during
your testing, they can't access other computers, only internet)

Then see if you can connect wirelessly
:twisted: Soylent Green Is People! :twisted:
2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400

starc
Posts: 1
Joined: Mon Jan 31, 2011 3:37 am

Re: Broadcast SSID diff than Joined SSID in Repeater Bridge

Post by starc »

Did you ever find out what happened? I have a similar issue with a Client+AP wireless mode. When I try to join the AP SSID authentication times out on the client side (this is with no Encryption). Wired connections work fine.
Tried 1.2.5 and 1.3.9 with the same results.

User avatar
DoesItMatter
Moderator
Posts: 1373
Joined: Thu May 21, 2009 3:56 pm

Re: Broadcast SSID diff than Joined SSID in Repeater Bridge

Post by DoesItMatter »

starc wrote:Did you ever find out what happened? I have a similar issue with a Client+AP wireless mode. When I try to join the AP SSID authentication times out on the client side (this is with no Encryption). Wired connections work fine.
Tried 1.2.5 and 1.3.9 with the same results.
Starc - are you doing this on a Broadcom device?

I think there was still a broadcom bug issue where you could not do the client+ap mode with different ssid's - it had to stay the same.

I am not sure if that bug was fixed because I think Eric said it was something with the Broadcom drivers, which are not open-source.
:twisted: Soylent Green Is People! :twisted:
2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400

Post Reply