More on the Orinoco + XI-825 + StrongARM platform...

[Ben Greear]

Btw, here's a tcpdump trace from the strongarm box:

21:24:17.358065 0:2:2d:b:27:a0 0:60:b3:69:56:67 0800 96: ip_hl < 5 (0)
                          0054 0000 4000 4001 e041 ac01 0101 ac01
                          0164 0800 48c3 d10e 0100 9479 743c e074
                          0900 0809 0a0b 0c0d 0e0f 1011 1213 1415
                          1617 1819 1a1b 1c1d 1e1f 2021 2223 2425
                          2627 2829 2a2b 2c2d 2e2f 3031 3233 3435
21:24:18.357950 0:2:2d:b:27:a0 0:60:b3:69:56:67 0800 96: ip_hl < 5 (0)
                          0054 0000 4000 4001 e041 ac01 0101 ac01
                          0164 0800 45c3 d10e 0200 9579 743c e174
                          0900 0809 0a0b 0c0d 0e0f 1011 1213 1415
                          1617 1819 1a1b 1c1d 1e1f 2021 2223 2425
                          2627 2829 2a2b 2c2d 2e2f 3031 3233 3435
21:24:19.357835 0:2:2d:b:27:a0 0:60:b3:69:56:67 0800 96: ip_hl < 5 (0)
                          0054 0000 4000 4001 e041 ac01 0101 ac01
                          0164 0800 3ac3 d10e 0300 9679 743c ea74
                          0900 0809 0a0b 0c0d 0e0f 1011 1213 1415
                          1617 1819 1a1b 1c1d 1e1f 2021 2223 2425
                          2627 2829 2a2b 2c2d 2e2f 3031 3233 3435
21:24:21.357605 0:2:2d:b:27:a0 0:60:b3:69:56:67 0806 72: arp-#2 for proto #1540 (1) hardware #2048 (0)
                          0800 0604 0001 0002 2d0b 27a0 ac01 0101
                          0000 0000 0000 ac01 0164 7267 652d 6963
                          653a 2f65 7463 2f70 636d 6369 6108 0300
                          0000 0000 0000 0000
21:24:21.567581 0:60:b3:69:56:67 0:2:2d:b:27:a0 0806 42: [|arp]
                          0800 0604 0002 0060 b369 5667 ac01 0164
                          0002 2d0b 27a0 ac01 0101


David Gibson wrote:

> On Wed, Feb 20, 2002 at 04:46:01PM -0700, Ben Greear wrote:
> 
>>
>>David Gibson wrote:
>>
>>
>>>On Wed, Feb 20, 2002 at 09:05:50AM -0700, Ben Greear wrote:
>>>
>>>
>>>>Here is what the received packet header looks like with
>>>>the latest 'testing' driver.  It looks like the 08 06
>>>>should be where the 00 44 is, if I understand things correctly.
>>>>
>>>>Packet received, hdr:
>>>>00 60 b3 69 56 67 00 02 2d 0b 27 a0 00 44 aa aa
>>>>03 00 00 00 08 06
>>>>
>>>>
>>>How are you capturing this packet - this the extra stuff here is an
>>>802.2 header.  Over the air, 802.11 always has an encapsulated 802.2
>>>header, but the driver is supposed to convert to Ethernet-II frames.
>>>
>>
>>I put printk statements in the driver, see below.  Can you tell if
>>the header is correct at this stage?  If so, I can add more debugging
>>farther up the stack to see where it gets lost/corrupted, etc...
>>
> 
> Ok, your printk()s are before the decapsulation logic, so you're
> seeing the packet's 802.2 header, and the fake 802.3 header that the
> card generates.  Given that, it looks correct.
> 
> 


-- 
Ben Greear <greearb at candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear