#465: Two Atheros cards and briding - cards are cloning themself
-----------------------------------+----------------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:                              
        
          Type:  defect            |      Status:  new                          
       
      Priority:  major             |   Milestone:  version 0.9.0 - move to new 
codebase
     Component:  madwifi: other    |     Version:  trunk                        
       
    Resolution:                    |    Keywords:                               
       
Patch_attached:  0                 |  
-----------------------------------+----------------------------------------
Old description:

> Hi,
>
> there are two atheros cards on one board. When i apply the following
> settings:
>
> wlanconfig ath0 create wlandev wifi0 wlanmode master
> wlanconfig ath1 create wlandev wifi0 wlanmode master
>
> iwconfig ath0 essid netlab2
> iwconfig ath0 channel 1
> iwconfig ath0 key 35000a29631d2130ef66639da49472e1
>
> iwconfig ath1 essid netlab
> iwconfig ath1 channel 10
> iwconfig ath1 key 35000a29631d2130ef66639da49472e1
>
> brctl addbr br0
>
> ifconfig eth0 0.0.0.0
> ifconfig ath0 0.0.0.0
> ifconfig ath1 0.0.0.0
>
> brctl addif br0 ath1
> brctl addif br0 eth0
>
> The cards seem to be cloned. The output after applying the cmds for
> iwconfig is the following:
>
>  ath0 IEEE 802.11g  ESSID:"netlab2"
>  Mode:Master  Frequency:2.412 GHz  Access Point: 00:0E:8E:03:44:B3
>  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
>  Retry:off   RTS thr:off   Fragment thr:off
>  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
> mode:restricted
>  Power Management:off
>  Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
>  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
>  ath1 IEEE 802.11g  ESSID:"netlab"
>  Mode:Master  Frequency:2.412 GHz  Access Point: 06:0E:8E:03:44:B3
>  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
>  Retry:off   RTS thr:off   Fragment thr:off
>  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
> mode:restricted
>  Power Management:off
>  Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
>  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> I played arround and i got a oops after i destroyed the two devices and
> applyed the script again.
> Look at iwconfig... like you see its the same channel frequ... but ath0
> should use channel 10 and ath1 channel 1... so lets see what happens when
> a client connects to ath1:
>
>  ath0      IEEE 802.11g  ESSID:"netlab2"
>  Mode:Master  Frequency:2.412 GHz  Access Point: 00:0E:8E:03:44:B3
>  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
>  Retry:off   RTS thr:off   Fragment thr:off
>  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
> mode:restricted
>  Power Management:off
>  Link Quality=55/94  Signal level=-40 dBm  Noise level=-95 dBm
>  Rx invalid nwid:4  Rx invalid crypt:0  Rx invalid frag:0
>  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
>  ath1      IEEE 802.11g  ESSID:"netlab"
>  Mode:Master  Frequency:2.412 GHz  Access Point: 06:0E:8E:03:44:B3
>  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
>  Retry:off   RTS thr:off   Fragment thr:off
>  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
> mode:restricted
>  Power Management:off
>  Link Quality=55/94  Signal level=-40 dBm  Noise level=-95 dBm
>  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> Ooops... client1 is only connected to ath1 but ath0 also display the link
> quality? wtf? I have tryed to use a other wepkey on ath0 then on ath1 but
> its the same... the client connects to ath1 and ath0 also displays the
> same link quality and such things... The client also got some problem
> with this... it will get a lot of rx invalid pkgs(Rx invalid nwid:15387
> after some minutes). When i kill ath0 so that only ath1 is working... the
> rx invalid pkgs are stopping and it works.
>
> So my next idea was the the bridge is doing some magic foo but its the
> same problem without the brctl stuff.
>
> Does anybody have a idea?
>
> Regards,
>
> red

New description:

 Hi,

 there are two atheros cards on one board. When i apply the following
 settings:
 {{{
 wlanconfig ath0 create wlandev wifi0 wlanmode master
 wlanconfig ath1 create wlandev wifi0 wlanmode master

 iwconfig ath0 essid netlab2
 iwconfig ath0 channel 1
 iwconfig ath0 key 35000a29631d2130ef66639da49472e1

 iwconfig ath1 essid netlab
 iwconfig ath1 channel 10
 iwconfig ath1 key 35000a29631d2130ef66639da49472e1

 brctl addbr br0

 ifconfig eth0 0.0.0.0
 ifconfig ath0 0.0.0.0
 ifconfig ath1 0.0.0.0

 brctl addif br0 ath1
 brctl addif br0 eth0
 }}}

 The cards seem to be cloned. The output after applying the cmds for
 iwconfig is the following:
 {{{
  ath0 IEEE 802.11g  ESSID:"netlab2"
  Mode:Master  Frequency:2.412 GHz  Access Point: 00:0E:8E:03:44:B3
  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
 mode:restricted
  Power Management:off
  Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  ath1 IEEE 802.11g  ESSID:"netlab"
  Mode:Master  Frequency:2.412 GHz  Access Point: 06:0E:8E:03:44:B3
  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
 mode:restricted
  Power Management:off
  Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
 }}}

 I played arround and i got a oops after i destroyed the two devices and
 applyed the script again.
 Look at iwconfig... like you see its the same channel frequ... but ath0
 should use channel 10 and ath1 channel 1... so lets see what happens when
 a client connects to ath1:
 {{{
  ath0      IEEE 802.11g  ESSID:"netlab2"
  Mode:Master  Frequency:2.412 GHz  Access Point: 00:0E:8E:03:44:B3
  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
 mode:restricted
  Power Management:off
  Link Quality=55/94  Signal level=-40 dBm  Noise level=-95 dBm
  Rx invalid nwid:4  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  ath1      IEEE 802.11g  ESSID:"netlab"
  Mode:Master  Frequency:2.412 GHz  Access Point: 06:0E:8E:03:44:B3
  Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=0/3
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:3500-0A29-631D-2130-EF66-639D-A494-72E1   Security
 mode:restricted
  Power Management:off
  Link Quality=55/94  Signal level=-40 dBm  Noise level=-95 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
 }}}
 Ooops... client1 is only connected to ath1 but ath0 also display the link
 quality? wtf? I have tryed to use a other wepkey on ath0 then on ath1 but
 its the same... the client connects to ath1 and ath0 also displays the
 same link quality and such things... The client also got some problem with
 this... it will get a lot of rx invalid pkgs(Rx invalid nwid:15387 after
 some minutes). When i kill ath0 so that only ath1 is working... the rx
 invalid pkgs are stopping and it works.

 So my next idea was the the bridge is doing some magic foo but its the
 same problem without the brctl stuff.

 Does anybody have a idea?

 Regards,

 red

Comment (by mrenzmann):

 Using WikiFormatting as suggested by Trac when entering a ticket helps to
 avoid this kind of formatting problems ;)

-- 
Ticket URL: <http://madwifi.org/ticket/465>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity

Reply via email to