Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #2466 (new defect)

Opened 11 years ago

Last modified 11 years ago

Association Lost after I set up bridge..

Reported by: Eno Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version:
Keywords: Cc:
Patch is attached: 0 Pending: 0


Hello to all,

I have two chips running on two different windows terminals. These chips will have these interfaces:

Terminal 1: One Station, One Access Point Terminal 2: One Station

I first start off associating terminal 1's AP and terminal 2's STA together. I managed to associate them and ping each other on their own terminal. Next, I create a bridge on terminal 1 and try to bridge the STA and AP on terminal 1 together. As soon as I ifconfig up the bridge, the earlier association between terminal 1's STA and terminal 2's AP is lost. I've tried reversing the sequence(ie. create the bridge first then associate but nth seems to work)

Exact Steps Executed: I went to terminal 1 to create AP1: • Wlanconfig ath0 create wlandev wifi0 wlanmode ap • Iwconfig ath0 essid test • Iwpriv ath0 wds 1 • Ifconfig ath0 up

Then I went to terminal 2 to create STA2: • Wlanconfig ath0 create wlandev wifi0 wlanmode sta • Iwconfig ath0 essid test • Iwpriv ath0 wds 1 • Ifconfig ath0 up • Ping (i leave this on so I can know if my connection with AP1 is lost)

Pinging is successful and I know there's association between AP1 and STA1. Now I went back to terminal 1 to create a STA2 and the bridge:

• Wlanconfig ath1 create wlandev wifi0 wlanmode sta nosbeacon • Iwconfig ath1 essid test • Iwpriv ath1 wds 1 • Ifconfig ath1 up

As soon as I type in ifconfig ath1, the association beween AP1 and STA2 is lost. The pinging from terminal 2 that I left it on stops.

Additional Information: I'm using MIPS Linux Starter Kit that have a built in OpenWrt? Kamikaze in it. I am not sure how to check the Madwifi version(the documentation did not mention anything abt it). Thank you for reading. :)

Change History

09/07/11 17:16:36 changed by Matthijs Kooijman <>

Sounds like you're trying to configure two separate networks using the same IP range (192.168.0.x). I suspect that your terminal 1 is sending its ping replies over its STA interface, instead of over its AP interface. If you want to do this, you should either use different IP ranges and set up layer 2 routing and/or NAT, or you should add both the STA and AP interfaces into a software bridge (see the brctl command).

I'm not 100% sure this is your problem, since it seems you've messed up the various numbers in your description (e.g, you say you setup STA2 and then you say STA1 is associated with AP1, etc.).