Re: if_ral regression

From: Sepherosa Ziehau <sepherosa_at_gmail.com>
Date: Fri, 4 Jan 2008 22:11:51 +0800
On Jan 4, 2008 4:51 PM, Dag-Erling Smørgrav <des_at_des.no> wrote:
> "Sepherosa Ziehau" <sepherosa_at_gmail.com> writes:
> > Are you also using freebsd as STA too?  If yes, would you have time to
> > gather following information on the STA side before after and during
> > the rsyncing:
> > 1) wlandebug -i sta_iface +input
> > 2) tcpdump -ni sta_iface -y ieee802_11 -w dump.bin
>
> I'll have to pull out an old laptop to do that, my current one runs
> Ubuntu.  Hopefully, I'll have the results for you later today.  I
> imagine you want to see the output from wlandebug both when the AP is
> working and when it is stuck?

Yes.

I just did some air dump of ral's beacon and data frame
A sample ral(4) broadcast beacon frame:
21:26:26.662250 Beacon (sephe-hostap) [1.0* 2.0* 5.5* 11.0* 6.0 9.0
12.0 18.0 Mbit] ESS CH: 6
        0x0000:  8000 0000 ffff ffff ffff 0015 f2d7 420c
        0x0010:  0015 f2d7 420c 0000 e053 4a10 0000 0000
        0x0020:  6400 2104 000c 7365 7068 652d 686f 7374
        0x0030:  6170 0108 8284 8b96 0c12 1824 0301 0605
        0x0040:  0400 0101 002a 0100 3204 3048 606c

The seq is 0!!

Two sample ral(4) data frames (ICMP echo resps)
21:26:27.810209 IP 192.168.5.2 > 192.168.5.1: ICMP echo request, id
61969, seq 1, length 64
        0x0000:  0801 2c00 0015 f2d7 420c 0014 787a 5990
        0x0010:  0015 f2d7 420c f0b1 aaaa 0300 0000 0800
        0x0020:  4500 0054 0e75 0000 4001 e0e0 c0a8 0502
        0x0030:  c0a8 0501 0800 42b2 f211 0001 477e 3403
        0x0040:  000c 5caa 0809 0a0b 0c0d 0e0f 1011 1213
        0x0050:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
21:26:28.820190 IP 192.168.5.2 > 192.168.5.1: ICMP echo request, id
61969, seq 2, length 64
        0x0000:  0801 2c00 0015 f2d7 420c 0014 787a 5990
        0x0010:  0015 f2d7 420c 00b2 aaaa 0300 0000 0800
        0x0020:  4500 0054 f517 0000 4001 fa3d c0a8 0502
        0x0030:  c0a8 0501 0800 1bb1 f211 0002 477e 3404
        0x0040:  000c 83a9 0809 0a0b 0c0d 0e0f 1011 1213
        0x0050:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223

802.11 stack does the right thing here, seq is incremented between two frames.

This actually brings up two things:
1) I think should ignore seq in multicast frames; this is permitted in
802.11 standard.  In dfly I did that, since one of our users
encountered a broken commercial AP which is not 802.11e but use
different beacon se

-- 
Live Free or Die
Received on Fri Jan 04 2008 - 13:12:22 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:24 UTC