#1866: Configuring a Client connection kills working AP configuration
----------------------------------+-----------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: closed
Priority: major | Milestone:
Component: madwifi: driver | Version: v0.9.4
Resolution: invalid | Keywords: VAP, client, Accesspoint, AP,
more than one configuration
Patch_attached: 0 |
----------------------------------+-----------------------------------------
Changes (by mrenzmann):
* status: new => closed
* resolution: => invalid
Old description:
> 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'
New description:
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'
}}}
Comment:
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
[wiki:UserDocs/UsersGuide#a1.2Usingwlanconfig 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
[wiki:Support regular support channels] first before reopening this
ticket.
--
Ticket URL: <https://madwifi.org/ticket/1866#comment:1>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
