Modify

Opened 8 years ago

Closed 4 years ago

#7106 closed defect (wontfix)

apsta (one ap, one sta wifi) on brcm-2.4 not working

Reported by: ruder@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Backfire 10.03 RC3
Keywords: Cc:

Description

Hi,

I was using apsta mode with Kamikaze 7.09 successfully to connect to one WLAN via wan-bridge and still broadcast a lan (or even wan) WLAN to share that access with other WLAN clients.

However, with 8.09 this stopped working and also with 10.03 I cannot get this to work.

What happens is, that the sta mode works perfectly, but it is not possible to connect to the ap mode WLAN anymore, eventhough it is still visible. Once the sta mode entry is commented out, the ap mode WLAN works again.

I tried using the same secret, but this doesn't work either.

I use the brcm-2.4 kernel since I learnt that the b43 driver is not yet ready for multi-ssid.

I tried with the standard download image (openwrt-brcm-2.4-squashfs.trx from the website 10.03 rc3) as well as with my own built image.

I use a Buffalo WHR-HP-G54.

This is my config:

config wifi-device  wl0
        option type     broadcom
        option channel  5

        # REMOVE THIS LINE TO ENABLE WIFI:
#       option disabled 1

config wifi-iface
        option device   wl0
        option network  lan
        option mode     ap
        option ssid     'my ap'
        option encryption psk2
        option key 'my secret'

config wifi-iface
        option device   wl0
        option network  wan
        option mode     sta
        option ssid     'other ap'
        option encryption psk2
        option key 'other secret'

Attachments (0)

Change History (21)

comment:1 follow-up: Changed 8 years ago by djsam01@…

Hi,

I have the same problem here with a Linksys WRT54GL; though I noticed that this configuration works if encryption is disabled on both networks, so the encryption may cause problems.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 8 years ago by Tamas Szentendrei <djsam01@…>

I've just found the solution to the problem! The virtual wl0.1 interface (the one in AP mode) gets a virtual MAC address that becomes automatically the BSSID of this AP. However, the physical MAC address is still the same as the MAC address of the STA mode wl0 interface, and this causes a problem in WPA authetication. So, the wl0.1 BSSID must match the MAC of the wl0 interface. This can be specified in /etc/config/wireless with
option bssid 'your wl0 MAC address'

Works for me with OpenWRT 10.03.

comment:3 in reply to: ↑ 2 Changed 8 years ago by ruder@…

Replying to Tamas Szentendrei <djsam01@…>:

I tried this with Kamikaze 8.09.1 but I get the error message:

Command 'set bssid' failed: -1

and iwconfig still shows a 02:... MAC address for wl0.1 which differs from wl0. Also manually changing via

wlc ifname wl0.1 bssid ...

did not do the trick.

comment:4 Changed 8 years ago by koniu

I had a very similar issue - ap+sta, client works, ap shows up but clients can't connect to it. Tracked it down to wan being bridged. If you turn that off and use just wl0 as wan interface,
you can connect to the ap again.

What djsam01 is saying makes sense + someone on IRC mentioned something about nas having issues with mismatching MAC addresses. Haven't tried forcing BSSID in the configuration tho.

# uci show network.wan
network.wan=interface
network.wan.proto=dhcp
network.wan.ifname=wl0
network.wan.defaultroute=0
network.wan.peerdns=0

# uci show wireless
wireless.wl0=wifi-device
wireless.wl0.type=broadcom
wireless.wl0.channel=6
wireless.wl0.disabled=0
wireless.@wifi-iface[0]=wifi-iface
wireless.@wifi-iface[0].device=wl0
wireless.@wifi-iface[0].network=lan
wireless.@wifi-iface[0].mode=ap
wireless.@wifi-iface[0].ssid=blabla
wireless.@wifi-iface[0].encryption=psk2
wireless.@wifi-iface[0].key=blablabla
wireless.@wifi-iface[1]=wifi-iface
wireless.@wifi-iface[1].device=wl0
wireless.@wifi-iface[1].ssid=XXXXX
wireless.@wifi-iface[1].network=wan
wireless.@wifi-iface[1].mode=sta
wireless.@wifi-iface[1].encryption=wep
wireless.@wifi-iface[1].key=XXXXXXXXXX

comment:5 Changed 8 years ago by koniu

Btw according to [1] setting BSSID applies only in adhoc and bssid modes.

[1] http://wiki.openwrt.org/doc/uci/wireless#common.options1

comment:6 Changed 8 years ago by nunojpg

I have the same issue in a WL-500GP V1.

Tried:
Kamikaze 8.09.3
Backfire 10.03

I have psk2 encryption on STA and no encryption on AP.

Tamas Szentendrei solution dont work.

comment:7 Changed 8 years ago by nbd

  • Resolution set to obsolete
  • Status changed from new to closed

brcm-2.4 is gone. should work with the new driver

comment:8 follow-ups: Changed 7 years ago by mbay

  • Resolution obsolete deleted
  • Status changed from closed to reopened

Have the same issue using a Linksys WRT54GL.

Tried: backfire/10.03.1-rc4/brcm-2.4/openwrt-brcm-2.4-squashfs.trx

I Have PSK2 on STA and AP. but cant connect to AP :-(

What do i have to do? Whats about the new Driver? Is it missing in backfire?

Thank you!

comment:9 in reply to: ↑ 8 Changed 7 years ago by anonymous

Replying to mbay:

Tried: backfire/10.03.1-rc4/brcm-2.4/openwrt-brcm-2.4-squashfs.trx

What do i have to do? Whats about the new Driver? Is it missing in backfire?

Please read the answer from nbd, brcm-2.4 is gone afaik use brcm47xx (kernel-2.6)

HtH

comment:9 in reply to: ↑ 8 Changed 7 years ago by anonymous

Replying to mbay:

Tried: backfire/10.03.1-rc4/brcm-2.4/openwrt-brcm-2.4-squashfs.trx

What do i have to do? Whats about the new Driver? Is it missing in backfire?

Please read the answer from nbd, brcm-2.4 is gone afaik use brcm47xx (kernel-2.6)

HtH

comment:10 Changed 7 years ago by mbay

i will try it! Thank you!

comment:11 Changed 7 years ago by mbay

im using brcm47xx (kernel-2.6) now, but wlan isnt working anymore.

WLAN flash is always off, but its enabled in the interface.

any idea?

comment:12 Changed 7 years ago by mbay

fixxed it, you can close =)

comment:13 Changed 7 years ago by nbd

  • Resolution set to worksforme
  • Status changed from reopened to closed

comment:14 follow-up: Changed 7 years ago by anonymous

  • Resolution worksforme deleted
  • Status changed from closed to reopened

at least one more question, sorry.

You told us to use brcm47xx but ticket 7093 says that the b43 driver in brcm47 does not support multi-ssid and won't support multi-ssid, so which driver to use for wrt54gl?

comment:15 in reply to: ↑ 14 Changed 7 years ago by anonymous

Replying to anonymous:

at least one more question, sorry.

You told us to use brcm47xx but ticket 7093 says that the b43 driver in brcm47 does not support multi-ssid and won't support multi-ssid, so which driver to use for wrt54gl?

This is not a support forum, I hope you understand. Reopening old tickets is not nice - there are many actual issues waiting in the queue.

As for your question there are packages for brcm47xx with the proprietary broadcom-wl modules - u need relevant kmods and wl+wlc iirc. You will also probably need to build from source seeing how wrt54gl has pretty small flash, to little to fit b43 as well as wl.

comment:16 Changed 7 years ago by nbd

  • Resolution set to worksforme
  • Status changed from reopened to closed

comment:17 Changed 6 years ago by tachemihai@…

  • Resolution worksforme deleted
  • Status changed from closed to reopened

I dare re-open this ticket because the "worksforme" resolution and the last post aren't correct.
I am testing on a WRT54G v2.2 (corerev 7 - supports multiple SSIDs but not BSSIDs).
Custom built brcm47xx from trunk (r32xxx) with proprietary broadcom driver (as suggested) doesn't work. STA link is OK, AP shows up but stations can't connect and nothing appears in the log.
"Can't set mssid / Can't set ssid" shows up during wifi init.

Also tried the official 10.03.1 brcm-2.4 build and had similar results. no bridges, tried setting bssid, macaddr etc. tried with and without encryption.
With 2.4 if you have WPA on both interfaces, the 2nd nas process doesn't start because the STA one is already running. On brcm47xx trunk I had two nas processes at least.

Also on 2.4 the AP interface has a MAC and BSSID of 00:00:00:00:00:00 that cannot be changed to anything else with wlc or config/wireless

If anyone can run AP+STA with Backfire on any platform / custom built trunk, please post your detailed configuration.

I will now try Kamikaze 7.09 which is reported to work and if not, dd-wrt.
Newer versions are supposed to bring new features and bugfixes, not break old stuff and as long as b43 does not and will not support multi-ssid or ap+sta, the broadcom wl solution should work as it did in the past and should be supported.

LATER EDIT:
7.09 AP+STA works like a charm (I am posting this while connected to it's AP), no config tricks, nothing special. both links on WPA, two nas processes. please port wl and associated tools to backfire properly or don't port it at all. it doesn't even work on backfire brcm-2.4

comment:18 Changed 6 years ago by jow

  • Resolution set to wontfix
  • Status changed from reopened to closed

brcm-2.4 is eol, b43 does not handle multiple ssids and wl on brcm47xx is not officially supported at the moment. If you need repeater on legacy hardware use 8.09.2 or earlier.

comment:19 Changed 4 years ago by anonymous

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Suggestion above isn't acceptable because repeater works only on 7.09 or earlier versions which is too ancient and unacceptable.

comment:20 Changed 4 years ago by jogo

  • Resolution set to wontfix
  • Status changed from reopened to closed

10.03.x and earlier are not supported anymore, you need to implement/fix it yourself or pay someone to implement/fix it.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.