Ticket #1866 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

Configuring a Client connection kills working AP configuration

Reported by: anonymous Assigned to:
Priority: major Milestone:
Component: madwifi: driver Version: v0.9.4
Keywords: VAP, client, Accesspoint, AP, more than one configuration Cc: ticketbug@gmx.de
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

My wlan-pci-card: SMCWPCI-G EU EZ Connect g Wireless PCI Adapter 2.4 GHz 54 Mbps Wireless PCI Adapter

I am using the madwifi drivers as part of the fli4l distribution 3.2.0 and later. I configured an AP which works nicely in wep, wpa1 and wpa2 modes. When I configure another VAP on the same pci card (a client connection to a wlan router) the driver seems to be running into problems: The additional client connection works, but the previously working AP doesn't anymore. WinXPpro finds the AP but cannot establish a connection, neither with wep, wpa1 nor wpa2.

The second configuration seems to somehow kill the working first configuration.

Any help is appreciated.

Regards

Frank

Here are my config settings: 

WLAN_1_MAC='00:13:F7:xx:xx:xx'
WLAN_1_ESSID='xyznet'
WLAN_1_MODE='master'
WLAN_1_CHANNEL='6'          # the channel the second configuration is running on after auto-scan
WLAN_1_RATE='auto'
WLAN_1_WPA_KEY_MGMT='WPA-PSK'
WLAN_1_WPA_PSK='xxxx'
WLAN_1_WPA_TYPE='1'
WLAN_1_WPA_ENCRYPTION='CCMP'
WLAN_1_ACL_POLICY='allow'
WLAN_1_ACL_MAC_N='1'
WLAN_1_ACL_MAC_1='00:08:54:xx:xx:xx'

WLAN_2_MAC='00:13:F7:xx:xx:xx'
WLAN_2_ESSID='WLAN123'
WLAN_2_MODE='managed'
WLAN_2_CHANNEL='0'
WLAN_2_RATE='auto'
WLAN_2_ENC_N='1'
WLAN_2_ENC_1='s:xxxxxxxxxxxxxxxx'
WLAN_2_ENC_ACTIVE='1'
WLAN_2_WEP_ROTATE='0'

Attachments

Change History

04/16/08 09:37:22 changed by mrenzmann

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

You need to make sure that the STA VAP is created using the "nosbeacon" flag. r3476 recently changed the driver to take care of that automatically, but that change was made after v0.9.4 was released.

For further information please refer to the relevant section of the users guide, especially the paragraph that follows table 1.

I close this ticket as invalid, as there is no evidence that this is a bug in the driver. If you have further questions, please contact out regular support channels first before reopening this ticket.

Add/Change #1866 (Configuring a Client connection kills working AP configuration)