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

Opened 14 years ago

creation of monitor mode VAP prevents pinging AP VAP

Reported by: mah@cs.umd.edu Assigned to:
Priority: minor Milestone:
Component: madwifi: driver Version: trunk
Keywords: monitor ap ping failure Cc:
Patch is attached: 0 Pending:

Description

This defect is found in revision 3641, running on a suse 2.6.22 kernel with a Netgear WG511T. Setting up a monitor mode VAP with an existing AP VAP prevents use of the AP.

We setup an AP VAP and ping it to test using another machine. First we remove any existing VAPs, for example with:

wlanconfig ath0 destroy

We create the AP VAP, set the ESSID, and bring up the interface with a static IP address.

wlanconfig ath0 create wlandev wifi0 wlanmode ap
iwconfig ath0 essid mytest
ifconfig ath0 10.0.0.1 up

On a second machine we associate a station VAP with the AP, and ping the AP.

wlanconfig ath0 create wlandev wifi0 wlanmode sta
iwconfig ath0 essid mytest
ifconfig ath0 10.0.0.2 up
ping 10.0.0.1

This succeeds with a response from the AP.

Now we create a monitor mode interface on the machine with the AP VAP.

wlanconfig ath1 create wlandev wifi0 wlanmode monitor

Pinging now indicates the destination is unreachable. The expected behavior is for the ping to succeed after the monitor VAP is created, as well as after the monitor interface is brought up.