[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-wlan-user
Subject:    Re: [lwlan-user] WEP issue -- please help
From:       Michael Anburaj <embeddedneteng () yahoo ! com>
Date:       2004-07-28 16:35:54
Message-ID: 20040728163554.70571.qmail () web51909 ! mail ! yahoo ! com
[Download RAW message or body]


--- Michael Anburaj <embeddedneteng@yahoo.com> wrote:

> Hi,
> 
> I run the “wlan-ng: 0.2.1-pre14” driver on my MIPS
> platform with modified kernel that calls the driver
> APIs directly. It worked fine without WEP.
> 
> Setup #1: without WEP
> 
>  --------                              
> -------------
> | MIPS   |------                -------|  PC windows
> |
> |wlan-ng |MA311 |              | MA401 |            
> |
> |without |      |              |       | without WEP
> |
> |WEP     |------                -------|            
> |
>  --------                              
> -------------
> 
> In AD-HOC mode, without WEP, the MA311 with wlan-ng
> driver can connect with the MA401 with windows
> driver
> & exchange IP packets back & forth.
> 
> Since it is a modified kernel, the wlan-ng APIs are
> called directly from the layer above.
> 
> Pseudo code:
> 
> 1. Driver get initialized
> 2. Prism2sta_ifstate gets called with ifstate_enable
> 3. Prism2mgmt_start gets called with
> p80211msg_dot11req_start_t data structure with all
> the
> necessary info. & bsstype.data = #Independent
> 
> 4. Each time an IP packet needs to be sent out
> p80211knetdev_hard_start_xmit is called with the skb
> that contains the IP packet.
> 
> 
> Setup #2: same setup with WEP enabled:
> 
> --------                               -------------
> | MIPS   |------                -------|  PC windows
> |
> |wlan-ng |MA311 |              | MA401 |            
> |
> |with    |      |              |       | with    WEP
> |
> |WEP     |------                -------|            
> |
>  --------                              
> -------------
> 
> In AD-HOC mode, with WEP, the MA311 with wlan-ng
> driver can connect with the MA401 <even if the keys
> are different it connects> with windows driver, but
> cannot exchange IP packets even if the keys match on
> both sides.
> 
> On the windows driver side:
> 64 bit wep, 10 digit hex – ddddffff00
> default Tx Key: 1 <possible values 1,2,3,4>
> 
> Since it is a modified kernel, the wlan-ng APIs are
> called directly from the layer above.
> 
> Pseudo code:
> 1. Driver get initialized
> 2. WEP setup:
> p80211pstr6_t wep;
> wep.len=5;
> wep.data[0]=0xdd; wep.data[1]=0xdd;
> wep.data[2]=0xff;
> wep.data[3]=0xff; wep.data[4]=0x00;
> 
> wlandev->hostwep =
> HOSTWEP_PRIVACYINVOKED|HOSTWEP_EXCLUDEUNENCRYPTED|
> HOSTWEP_ENCRYPTED|HOSTWEP_DECRYPED;
> 
> wep_change_key(wlandev, 0, wep.data, 5);
> prism2mib_wepdefaultkey(wlandev->priv, &wep,
> HFA384x_RID_CNFWEPDEFAULTKEY0);
> 
> 2. Prism2sta_ifstate gets called with ifstate_enable
> 3. Prism2mgmt_start gets called with
> p80211msg_dot11req_start_t data structure with all
> the
> necessary info. & bsstype.data = #Independent
> 
> 4. Each time a IP packet needs to be sent out
> p80211knetdev_hard_start_xmit is called with the skb
> that contains the IP packet.
> 
> 
> With this setup, after prism2mgmt_start is called
> Info. interrupt gets generated with line status
> (0xf200) as CONNECTED <similar to setup #1>. Then
> when
> the 1st IP packet gets sent out I don’t see it on
> the
> other end (windows PC) on ethereal. But, after a
> while
> an Info. interrupt get generated periodically with
> Tallies (0xf100). Tally info. interrupts info for
> the
> 1st 3 times is included at the bottom of this email.
> 
> Please let me know if I missed something here. Or
> help
> me debug this issue with debug procedure.
> 
> Thanks a lot,
> -Mike.
> 
> 
> DEBUG: Hfa384x_interrupt: Info
> DEBUG: Info type = 0xf100
> 
> Tallies:
> txunicastframes      : 0
> txmulticastframes    : 0
> txfragments          : 2053
> txunicastoctets      : 0
> txmulticastoctets    : 0
> txdeferredtrans      : 2202
> txsingleretryframes  : 0
> txmultipleretryframes: 0
> txretrylimitexceeded : 5
> txdiscards           : 0
> rxunicastframes      : 940
> rxmulticastframes    : 981
> rxfragments          : 1921
> rxunicastoctets      : 58274
> rxmulticastoctets    : 60066
> rxfcserrors          : 677
> rxdiscardsnobuffer   : 0
> txdiscardswrongsa    : 0
> rxdiscardswepundecr  : 1
> rxmsginmsgfrag       : 0
> rxmsginbadmsgfrag    : 0
> 
> DEBUG: Hfa384x_interrupt: Info
> DEBUG: Info type = 0xf100
> 
> Tallies:
> txunicastframes      : 0
> txmulticastframes    : 0
> txfragments          : 4169
> txunicastoctets      : 0
> txmulticastoctets    : 0
> txdeferredtrans      : 4401
> txsingleretryframes  : 0
> txmultipleretryframes: 0
> txretrylimitexceeded : 8
> txdiscards           : 0
> rxunicastframes      : 1891
> rxmulticastframes    : 1959
> rxfragments          : 3850
> rxunicastoctets      : 117236
> rxmulticastoctets    : 120216
> rxfcserrors          : 2159
> rxdiscardsnobuffer   : 0
> txdiscardswrongsa    : 0
> rxdiscardswepundecr  : 5
> rxmsginmsgfrag       : 0
> rxmsginbadmsgfrag    : 0
> 
> 
> 
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail 
> _______________________________________________
> Linux-wlan-user mailing list
> Linux-wlan-user@lists.linux-wlan.com
>
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-user@lists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
[prev in list] [next in list] [prev in thread] [next in thread]