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 #140 (closed defect: invalid)

Opened 14 years ago

Last modified 13 years ago

Wds tests in last night.

Reported by: alexandre.rosa@simtelecom.com.br Assigned to:
Priority: major Milestone:
Component: madwifi: driver Version: trunk
Keywords: Cc:
Patch is attached: Pending:

Description

I have make tests with WDS like this in two FC4 with dlink ag530 in both.

wlanconfig ath0 create wlandev wifi0 wlanmode wds iwpriv ath0 wds_add xx:xx:xx:xx:xx:xx (the mac of other side) iwpriv ath0 wds 1 ifconfig ath0 up ifconfig eth0 up brctl addbr br0 brctl addif br0 ath0 brctl addif br0 eth0 ifconfig br0 up

In this way, i give a full working PtP bridge, but in 11b mode and channel 1.

If i try to change the channel, it's don't change. But if a make a ifconfig down and up again in ath0, the channel change to new channel and mode to 11g, and the PtP bridge stay running with new channel and mode.

For change the mode, i do: ifconfig ath0 down -> iwpriv ath0 mode 1 -> ifconfig ath0 up and i get the 11a, but a lot's of lines with "mode (0) bad rate" are print in the console. To change channel, the same way: iwconfig channel/down/up ath0 and PtP bridge stay fine.

If a try to change the mode without down/newmode/up a get a kernel panic. Any ideia ?

If a try to set mode/channel before fire up ath0, the mode remains 11b and the channel 1.

Exists a better way to set mode/channel in wds mode ?

Thank's.

Alexandre Rosa

Change History

11/09/05 08:23:26 changed by mrenzmann

Your ticket has a lot of different things mixed up, let's sort that out:

If a try to change the mode without down/newmode/up a get a kernel panic. Any ideia ?

Please give us a full dump of the oops message you see in that case.

If a try to set mode/channel before fire up ath0, the mode remains 11b and the channel 1.

That looks like a bug that should be looked into, I agree. But I'm a bit confused, since some lines above that one you wrote that you were able to change mode and channel. So let me try to sum up:

  • load modules, create ath0 in wds mode, iwpriv ath0 mode X, iwconfig ath0 channel Y, ifconfig ath0 up. result: ath0 is still in 11b mode and on channel 1.
  • load modules, create ath0 in wds mode, ifconfig ath0 up, ifconfig ath0 down, iwpriv ath0 mode X, iwconfig ath0 channel Y, ifconfig ath0 up. result: ath0 uses right mode and channel.
  • load modules, create ath0 in wds mode, ifconfig ath0 up, don't do ifconfig ath0 down, iwpriv ath0 mode X. result: kernel panic.

Is that correct?

Side note: support requests should go to the madwifi-users mailing list. Tickets are meant for reporting bugs and feature requests, or submitting patches. More information can be found here.

11/09/05 08:45:40 changed by rudger@hopling.com

Try setting up a basic AP as root device, and create the wds devices later.

wlanconfig ath0 create wlandev wifi0 wlanmode ap wlanconfig wdsath10 create wlandev wifi0 wlanmode wds iwpriv wdsath10 wds_add <Point-to-Point MAC> iwpriv wdsath10 wds 1 ifconfig wdsath0 up <change mode, channels etc > ifconfig ath0 up

This works for me!

12/15/05 09:36:12 changed by mrenzmann

  • status changed from new to closed.
  • resolution set to invalid.

Since the reporter didn't answer so far, I'll close the ticket. Feel free to reopen it along with the requested missing information. Thanks.