WDS with WEP

Kel Modderman kelrin at tpg.com.au
Fri Jul 7 07:39:02 EDT 2006


chandramani wrote:
> Hi all,
>
> Using madwifi-ng and two atheros cards, I have configured two AP-WDS as instructed in 
>
> http://madwifi.org/wiki/UserDocs/WirelessBridging 
>
> Each card has two interfaces one ath0 in 'Master' and other ath1 in 'Repeater' mode.
> It seems that the set is working fine because I am able to ping one from other. 
>
> But now I want to configure this WDS link for security. How can I achieve that. I am not clear when I ping one WDS from another, packet passes through which interfaces ('ath0' or 'ath1' or both). 
>
> I tried following command to set a key for ath2
>
> iwconfig ath2 key [2] s:secretkey
>
> but setup crashed with following message and I had to reboot.
> -------------------------------------------------------------------------------------------------------------
> unexpected operating mode 2<0>------------[ cut here ]------------
> kernel BUG at <bad filename>:23128!
> invalid opcode: 0000 [#1]
> PREEMPT
> Modules linked in: wlan_wep wlan_acl wlan_tkip wlan_xauth wlan_scan_ap bridge sc
> 1200 scx200 natsemi crc32 ohci_hcd usbcore ath_pci ath_rate_sample wlan ath_hal
> CPU:    0
> EIP:    0060:[<c887bb44>]    Tainted: P      VLI
> EFLAGS: 00010282   (2.6.16.18 #1)
> EIP is at ieee80211_node_leave+0x62/0x196 [wlan]
> eax: 0000001e   ebx: c6d22000   ecx: c6defda4   edx: c888d742
> esi: c6d22000   edi: c78ba260   ebp: c128a260   esp: c6defda0
> ds: 007b   es: 007b   ss: 0068
> Process iwconfig (pid: 1806, threadinfo=c6dee000 task=c1246590)
> Stack: <0>c888d742 00000002 0000001e c128abdc c6d22000 000000e5 c128abdc c78ba26
> 0
>        c887b374 c6d22000 c6d22000 c888059e c128a260 c6d76000 c78ba260 00000004
>        c888083c c128abdc c888059e c78ba260 c7138000 00000001 c128a000 c128a260
> Call Trace:
>  [<c887b374>] ieee80211_iterate_nodes+0x6c/0xa1 [wlan]
>  [<c888059e>] sta_disassoc+0x0/0x34 [wlan]
>  [<c888083c>] __ieee80211_newstate+0x211/0x646 [wlan]
>  [<c888059e>] sta_disassoc+0x0/0x34 [wlan]
>  [<c8880dfc>] ieee80211_newstate+0x18b/0x195 [wlan]
>  [<c88a5e62>] ath_newstate+0x4f8/0x5e0 [ath_pci]
>  [<c8880619>] ieee80211_new_state+0x26/0x38 [wlan]
>  [<c8882373>] ieee80211_ioctl_siwencode+0x221/0x260 [wlan]
>  [<c020c046>] wireless_process_ioctl+0x31c/0x62f
>  [<c012ab74>] filemap_nopage+0xb7/0x2d6
>  [<c8882152>] ieee80211_ioctl_siwencode+0x0/0x260 [wlan]
>  [<c0203688>] dev_ioctl+0x247/0x27a
>  [<c01fa7c4>] sock_ioctl+0x1cf/0x1d9
>  [<c01511b0>] do_ioctl+0x28/0x66
>  [<c015145b>] vfs_ioctl+0x17a/0x188
>  [<c0151494>] sys_ioctl+0x2b/0x47
>  [<c01025e9>] syscall_call+0x7/0xb
> Code: 00 00 50 57 e8 94 d5 ff ff 83 c4 14 8b 87 34 02 00 00 83 f8 06 74 18 85 c0
>  74 14 83 f8 03 74 0f 50 68 42 d7 88 c8 e8 4d 60 89 f7 <0f> 0b 58 5a 66 83 7e 2c
>  00 0f 84 c8 00 00 00 8b 87 14 06 00 00
>  <0>Kernel panic - not syncing: Fatal exception in interrupt
> --------------------------------------------------------------------------------------------------------
> thanking in advance for any sort of help
>
>   

Could be related to http://madwifi.org/ticket/575 ?

Thanks, Kel.




More information about the HostAP mailing list