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

Opened 15 years ago

VAP: adhoc and ap on the same interface not working

Reported by: polna.antlab@gmail.com Assigned to:
Priority: minor Milestone:
Component: madwifi: driver Version: trunk
Keywords: vap Cc: svn revision: 2319
Patch is attached: 0 Pending:

Description

Hi I am trying to create on the same interface two VAPs: an AP and an adhoc, with WEP encryption. I found that: - if i create the ap first, i can't create the adhoc vap:

# wlanconfig ath0 create wlandev wifi0 wlanmode ap
 ath0
# wlanconfig ath2 create wlandev wifi0 wlanmode adhoc
wlanconfig: ioctl: Input/output error 

- if i create the adhoc first, i am allowed to create the interfaces; after that i configure the interfaces:

iwconfig ath2 essid ACCESS_ESSID
iwconfig ath2 key ACCESS_KEY

iwconfig ath0 essid BACKBONE ESSID
iwconfig ath0 BACKBONE_KEY

if i follow this order (i.e., setting the key on a separate line from the essid), it works; yet if i finally ifconfig the interfaces, the ap doesn't let the stations to associate.

ifconfig ath2 192.168.1.1 up
ifconfig ath0 192.168.2.1 up

Moreover, if i only ifconfig the ap, stations can associate to the ap, but they can't exchange packets with it (no ping or dhclient stuff). This happens both using key (with the s:string_key parameter and with the hex key) and without using them.

The working platform is an embedded device (VIA EPIA board), with CM9 MiniPCI wireless interfaces able to work with the a/b/g technology; the OS is Debian GNU/Linux, kernel 2.6.18.1, self-compiled.