TWO SSIDs on WRT54GS (Wifi guest-Network)

Hi,

I'm trying to setup two SSIDs (Networks) on an WRT54GS (version 22.3.03).

I've tried: https://openwrt.org/docs/guide-user/network/wifi/guestwifi/configuration_webinterface
and https://openwrt.org/docs/guide-user/network/wifi/guestwifi/guest-wlan

same results, I've tried am "Master Reset"...nothing works.

But afert adding the second SSID
grafik

I found these issues: https://github.com/openwrt/openwrt/issues/5659

But Chanel Mode ist not "Auto" I'm using fixed chanel (7).

After disabling one of these SSIDs, everything works like expected.

Thanks

Frank

Does your hardware allow multiple SSIDs on the same radio?

1 Like

That's avery good question! But I don't know where I would have look to answer it....

https://wiki.dd-wrt.com/wiki/index.php/Dual_SSID_one_for_public_network
or

seems to be working but maybe not out of the box...

https://wiki.dd-wrt.com/wiki/index.php/Multiple_WLANs

see Broadcom Based Hardware (Very old) mine is revision "7" so it may work.

1 Like

The valid interface combinations in iw list will tell you, but this hardware is way over its head to begin with (flash, RAM, CPU).

Hi, I'm sorry, but I dont understand your post, back in 2009 with ddwrt it was possible to da that > now in 2023 with open wrt it's not possible?
That does not belong to the HW it belongs to teh SW :wink:

Are you saying that OpenWrt 22.03.3 is running successfully on your WRT54GS???

Cool!

Yea, you need to see the [OpenWrt] Broadcom Warning.

Fix the conflict.

  • Did you run the command slh noted to get your instant answer if you can do multiple SSIDs?
  • DD-WRT != OpenWrt

???

I'm pretty sure back in 2009 DD-Wrt used a closed source Broadcom blob, and (at that time already) ancient kernel to match. With OpenWrt 22.03, you're running kernel 5.10 and a wireless stack from 5.15 - including the FOSS b43 driver.

You are looking at a wholly different software stack. And since b43 was developed without the help from Broadcom, it suffers from limitations, maybe even on old 2,4 GHz hardware (and not just on 5 GHz hardware where the lack of feature parity with the binary Broadcom driver was more visible).

You can more or less safely assume that anything 802.11n and up has some quirks with Broadcom and b43 in one way or another...

1 Like

Okay, Thank you for the input!
Meanwile I did a revert to ddwrt and yes will give my 2 different SSIDs.

But now I'm back an this is the output of iw list:


    root@OpenWrt:~# iw list
Wiphy phy0
        wiphy index: 0
        max # scan SSIDs: 4
        max scan IEs length: 2285 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 1:
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm) (no IR)
                        * 2472 MHz [13] (20.0 dBm) (no IR)
                        * 2484 MHz [14] (20.0 dBm) (no IR)
        interface combinations are not supported
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Supported extended features:
                * [ RRM ]: RRM
                * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
                * [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
                * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
                * [ DEL_IBSS_STA ]: deletion of IBSS station support
                * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
                * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

But what are we looking for?

1 Like

This:

The driver only allows running one AP at a time.

2 Likes

Okay thank you, in my opinion this was only for AP+STA.

1 Like

Put it in the bin!

One could do that, but it's only to reach out for the PV-Inverter to have the data collected....so nothing special needed. And I wanted to have it in a seperated Wifi-Network plus my "normal" privat LAN. No Problem at all, so I will setup a different router for my prvat LAN in a different location of my house.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.