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 #649 (new defect)

Opened 16 years ago

Last modified 15 years ago

wds problemwith latest madwifi-ng

Reported by: pstaszewski@artcom.pl Assigned to:
Priority: major Milestone:
Component: madwifi: other Version:
Keywords: Cc:
Patch is attached: 0 Pending:

Description

hello i have problem : panic on wds settings: steps to reproduce:

~ $ wlanconfig ath0 create wlandev wifi0 wlanmode ap ath0 ~ $ wlanconfig ath1 create wlandev wifi0 wlanmode wds ath1 ~ $ iwconfig ath0 essid "AP" channel 36 ~ $ iwpriv ath1 wds_add 00:0B:6B:3D:FB:AD ~ $ iwpriv ath1 wds 1 ~ $ ifconfig ath1 0.0.0.0 ~ $ ifconfig ath0 0.0.0.0

Kernel panic:

Change History

05/26/06 15:19:58 changed by pstaszewski@artcom.pl

ok solution :

in: http://madwifi.org/wiki/UserDocs/WDSBridge is sample configuration but is broken

interface working in ap mode must be first turned on and second wds interfaces so not linke this:

<broken config> wlanconfig ath0 create wlandev wifi0 wlanmode ap wlanconfig ath1 create wlandev wifi0 wlanmode wds iwconfig ath0 essid "Normal atheros AP" channel 1 iwpriv ath1 wds_add <mac of the peer wds ap> iwpriv ath1 wds 1 ifconfig ath1 up ifconfig ath0 up brctl addbr br0 brctl addif br0 ath1 brctl addif br0 ath0 ifconfig br0 up </broken config>

<good config>

//Create VAP AP-mode interface wlanconfig ath0 create wlandev wifi0 wlanmode ap //Create VAP WDS-mode interface wlanconfig ath1 create wlandev wifi0 wlanmode wds

//Set Access Point Name and channel iwconfig ath0 essid "AP" channel xx //Add remote mac address to wds interface iwpriv ath1 wds_add <mac of the peer wds ap> //Turn on wds iwpriv ath1 wds 1 //Set interface mode 11a/11b/11g iwpriv ath0 mode <mode> iwpriv ath1 mode <mode> //Turn up interfaces ifconfig ath0 up ifconfig ath1 up //Add interfaces to bridge brctl addbr br0 brctl addif br0 ath0 brctl addif br0 ath1 //Turn on bridge interface ifconfig br0 up

</good config>

And this config is working with (Mikrotik WDS) and (CA8-4 WDS)

06/02/06 15:10:23 changed by bhratc@gmail.com

I have a few questions here:

1. My understanding of the configuration is:

client1 --<wireless>-- AP1 ====<WDS>=== AP2 --- <wireless> ---client2 If so, what is the throughput seen between clients over WDS, say the 11g mode?

2. I am interested in:

client1 --<wired>--- AP1 ====<WDS>==== AP2 --- <wired> ---client2 Is this a supported configuration? Apart from the setting up of br0 appropriately, is there anything special required to be done?

06/02/06 18:22:10 changed by Mister_X

Your question should be directed to the mailing-list (tickets are not here to ask questions).

09/28/06 17:09:24 changed by Chey

This works for me. 

brctl addbr br0
wlanconfig ath0 create nounit wlandev wifi1 wlanmode ap
iwpriv ath0 mode 11g
iwconfig ath0 essid 'foobar' channel '11'
wlanconfig ath0wds0 create nounit wlandev wifi1 wlanmode wds
iwpriv ath0wds0 wds_add 00:11:22:33:44:55
iwpriv ath0wds0 wds 1
ip link set ath0 up
ip link set ath0wds0 up
brctl addif br0 ath0
brctl addif br0 ath0wds0
ip link set br0 up

09/29/06 12:04:32 changed by mrenzmann

Can the kernel panics still be reproduced with a current MadWifi revision? If so, please show us a dump of the kernel oops (see: DevDocs/KernelOops) and give details about which steps are necessary to reproduce the issue.

02/07/07 15:45:16 changed by xmxwx@asn.pl

This could be related to #575.