Re: Crash with recent kernel on wireless
On Fri, 2008-04-25 at 18:00 +0200, Roland Smith wrote: > On Fri, Apr 25, 2008 at 04:25:14PM +0400, Vladimir Grebenschikov wrote: > > Hi > > > > Recently I've upgraded 7-STABLE: Mar 11 -> Apr 24 > > > > Everything was fine until I've tried to configure wireless (ath driver, > > WPA) > > It crashes every time after interface becomes UP, > > (I've seen associated in ifconfig output before crash), but before dhcp > > finished to get IP. > You should use the kernel image with the debugging symbols here. If > you > build and install a kernel, you get two kernel images on 7.x; > 1) /boot/kernel/kernel (your regular kernel) > 2) /boot/kernel/kernel.symbols (with the debug symbols) Hm, I've thought before, that it will show back-trace even without debug symbols. Anyway, gdb still complains about "linker_file" and "not as structure pointer" But shows stop point. Not much info here :( cat /var/crash/info.44 Dump header from device /dev/ad0s2b Architecture: i386 Architecture Version: 2 Dump Length: 190091264B (181 MB) Blocksize: 512 Dumptime: Sat Apr 26 10:50:05 2008 Hostname: vbook.fbsd.ru Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #3: Sat Apr 26 10:20:31 MSD 2008 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/VBOOK Panic String: page fault Dump Parity: 4236056142 Bounds: 44 Dump Status: good kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.44 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". No struct type named linker_file. No struct type named linker_file. No struct type named linker_file. No struct type named linker_file. Attempt to extract a component of a value that is not a structure pointer. Attempt to extract a component of a value that is not a structure pointer. Attempt to extract a component of a value that is not a structure pointer. Attempt to extract a component of a value that is not a structure pointer. #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0542757 in boot (howto=260) at ../../../kern/kern_shutdown.c:418 #2 0xc0542a53 in panic (fmt=Variable "fmt" is not available.) at ../../../kern/kern_shutdown.c:572 #3 0xc06a8870 in trap_fatal () #4 0xc06a8c2a in trap_pfault () #5 0xc06a957e in trap () #6 0xc068e80b in calltrap () #7 0xc58b68d5 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Most of crashes even failed to save vmdump due to double faults. Looks like it is really related to wireless code. Effect happens only at my home WiFi network and does not happens at work (WPA-PSK vs PEAP) and always current process in nmbd (broadcasting ?). Crash happens with both 4BSD and ULE schedulers. My system have dual-core Intel x86 CPU (SMP kernel) > Roland -- Vladimir B. Grebenschikov [EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 'nfe' stalls (analysis and partial solution)
On Fri, Apr 25, 2008 at 06:00:39PM +0200, Luigi Rizzo wrote: > just for the record and the mail archives - i have been experiencing > a lot of unrecovered stalls of the network card with the 'nfe' > driver under heavy load (this was on 7.0-i386 and 7.0-amd64, but > it is hardware related so it cross-platform). > > After 2-3 days of investigation, and with the help of > Pyun YongHyeon (yongari) i finally managed to pin down the > problem and start working on a solution. > > I would be grateful if others can report of similar problems > with the 'nfe' driver so we can see if the patch we can come > up with also fix their problem. followup: a patch to address the problem is available at http://info.iet.unipi.it/~luigi/FreeBSD/ (current version is http://info.iet.unipi.it/~luigi/FreeBSD/nfe-20080426.1044.diff but it might change with time as we get more details or info on how to deal with this problem). cheers luigi ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: misc/123066: kernel trap with ipsec
On Fri, Apr 25, 2008 at 07:20:03AM +, misha saf wrote: > The following reply was made to PR kern/123066; it has been noted by GNATS. > > From: misha saf <[EMAIL PROTECTED]> > To: Kris Kennaway <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Subject: Re: misc/123066: kernel trap with ipsec > Date: Fri, 25 Apr 2008 10:59:33 +0400 > > * Kris Kennaway <[EMAIL PROTECTED]> [Fri, 25 Apr 2008 05:46:54 +]: > > On Fri, Apr 25, 2008 at 04:13:40AM +, Mihail wrote: > > > > > (kgdb) backtrace > > > #0 doadump () at pcpu.h:195 > > > #1 0xc075df57 in boot (howto=260) at > > /usr/src/sys/kern/kern_shutdown.c:409 > > > #2 0xc075e219 in panic (fmt=Variable "fmt" is not available. > > > ) at /usr/src/sys/kern/kern_shutdown.c:563 > > > #3 0xc0a9766c in trap_fatal (frame=0xc884e934, eva=3621180904) > > > at /usr/src/sys/i386/i386/trap.c:899 > > > #4 0xc0a978f0 in trap_pfault (frame=0xc884e934, usermode=0, > > eva=3621180904) > > > at /usr/src/sys/i386/i386/trap.c:812 > > > #5 0xc0a9829c in trap (frame=0xc884e934) at > > /usr/src/sys/i386/i386/trap.c:490 > > > #6 0xc0a7e21b in calltrap () at > > /usr/src/sys/i386/i386/exception.s:139 > > > #7 0xc0a952f6 in generic_bcopy () at > > /usr/src/sys/i386/i386/support.s:498 > > > Previous frame inner to this frame (corrupt stack?) > > > > Unfortunately we need the rest of the stack. Can you either try to > > reproduce with DDB in the kernel and obtain a stack trace from there, > > or if this is not possible then try recompiling the kernel with -O > > instead of -O2 which tends to produce better stack traces. > > > > Kris > That's all needed info ? No, stack frames 8 and beyond contained the important parts of the stack trace, but were not displayed by gdb. What we need is what I explained above. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multiple routing tables in action...
A little progress report From a recently installed (6.3) machine (plus patches) wsa02:julian 9] setfib -0 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.28.14.1UGS 0 788 bce1 127.0.0.1 127.0.0.1 UH 0 379lo0 172.28.5/24172.28.14.1UGS 0 10 bce1 172.28.6.32/28 link#2 UC 00em0 172.28.6.3300:15:2b:46:56:90 UHLW10em0 1190 172.28.14/24 link#6 UC 00 bce1 172.28.14.100:04:23:b5:a9:2b UHLW30 bce1 1117 wsa02:julian 10] setfib -1 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.28.6.33UGS 00em0 1.1.1/28 172.28.6.33UGS 00em0 127.0.0.1 127.0.0.1 UH 01lo0 172.28.5/24172.28.6.33UGS 06em0 172.28.6.32/28 link#2 UC 00em0 172.28.6.3300:15:2b:46:56:90 UHLW46em0 1182 wsa02:rjulian 11] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple routing tables in action...
when do we get to see those patches ? :) On Sat, Apr 26, 2008 at 6:44 PM, Julian Elischer <[EMAIL PROTECTED]> wrote: > A little progress report > > From a recently installed (6.3) machine (plus patches) > > wsa02:julian 9] setfib -0 netstat -rn > Routing tables > > Internet: > DestinationGatewayFlagsRefs Use Netif Expire > default172.28.14.1UGS 0 788 bce1 > 127.0.0.1 127.0.0.1 UH 0 379lo0 > 172.28.5/24172.28.14.1UGS 0 10 bce1 > 172.28.6.32/28 link#2 UC 00em0 > 172.28.6.3300:15:2b:46:56:90 UHLW10em0 1190 > 172.28.14/24 link#6 UC 00 bce1 > 172.28.14.100:04:23:b5:a9:2b UHLW30 bce1 1117 > wsa02:julian 10] setfib -1 netstat -rn > Routing tables > > Internet: > DestinationGatewayFlagsRefs Use Netif Expire > default172.28.6.33UGS 00em0 > 1.1.1/28 172.28.6.33UGS 00em0 > 127.0.0.1 127.0.0.1 UH 01lo0 > 172.28.5/24172.28.6.33UGS 06em0 > 172.28.6.32/28 link#2 UC 00em0 > 172.28.6.3300:15:2b:46:56:90 UHLW46em0 1182 > wsa02:rjulian 11] > > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- "UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." Dennis Ritchie ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multiple routing tables in action...
Ivo Vachkov wrote: when do we get to see those patches ? :) for -current: http://www.freebsd.org/~julian/mrt.diff for releng_6: http://www.freebsd.org/~julian/mrt6.diff On Sat, Apr 26, 2008 at 6:44 PM, Julian Elischer <[EMAIL PROTECTED]> wrote: A little progress report From a recently installed (6.3) machine (plus patches) wsa02:julian 9] setfib -0 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.28.14.1UGS 0 788 bce1 127.0.0.1 127.0.0.1 UH 0 379lo0 172.28.5/24172.28.14.1UGS 0 10 bce1 172.28.6.32/28 link#2 UC 00em0 172.28.6.3300:15:2b:46:56:90 UHLW10em0 1190 172.28.14/24 link#6 UC 00 bce1 172.28.14.100:04:23:b5:a9:2b UHLW30 bce1 1117 wsa02:julian 10] setfib -1 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.28.6.33UGS 00em0 1.1.1/28 172.28.6.33UGS 00em0 127.0.0.1 127.0.0.1 UH 01lo0 172.28.5/24172.28.6.33UGS 06em0 172.28.6.32/28 link#2 UC 00em0 172.28.6.3300:15:2b:46:56:90 UHLW46em0 1182 wsa02:rjulian 11] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting P1i to FreeBSD
Sepherosa Ziehau wrote: Are you sure that your device works under IBSS mode? Yes, since Windows doesn't support creating an AP from the card, and it connects to Windows. Unless there are other modes that can do the same thing... BTW, it looks like you have third machine that is equipped with wireless device, so would you please grab a 802_11 tap when your device tries to connect to rum on your freebsd box: tcpdump -ni your_third_wlan_iface -y ieee802_11 -w dump.bin [nomenclature: let's call the FreeBSD machine with the rum interface, the one I wish to associate the device with, the "gateway" and the other one the "laptop"]. I have a scan from the the laptop, but apparently it doesn't record all - only beacons and probe responses are in the dump and only from two nodes - my own and one of the neighbours' (but it's a noisy neigbourhood and the device finds at least three more APs. Here's a sample: 23:08:30.832242 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:08:30.844990 Beacon (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS CH: 6, PRIVACY 23:08:31.011276 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:31.461225 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:08:31.641185 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:32.272083 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:32.721339 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:08:32.902988 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.351839 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:08:33.533886 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.938823 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.940424 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.942064 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.944436 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.949696 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.953018 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 23:08:33.955180 Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 Additionally, I've recorded from the gateway machine: 01:13:53.812038 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:53.812072 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:54.442969 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:54.442993 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:55.073911 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:55.073931 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:55.705028 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:55.705049 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:56.335801 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:56.335821 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:56.966747 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:56.966767 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:57.597697 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:57.597721 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:58.228636 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:58.228656 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:58.859586 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:58.859607 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:13:59.490529 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:13:59.490550 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:14:00.120474 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:14:00.120495 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:14:00.713427 0us Probe Request (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* Mbit] 01:14:00.713446 0us Probe Response (bsd7adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 2 01:14:00.751416 0us Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 01:14:00.7
Re: Connecting P1i to FreeBSD
Ivan Voras wrote: Sepherosa Ziehau wrote: Are you sure that your device works under IBSS mode? Yes, since Windows doesn't support creating an AP from the card, and it connects to Windows. Unless there are other modes that can do the same thing... Actually there is a difference; here's a dump from laptop where the device connects to the Windows machine: 23:49:18.013539 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:18.045340 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:18.148408 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:18.374477 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:18.377198 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:18.379066 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:49:18.659907 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:18.734842 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:18.762218 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:19.005423 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:19.008301 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:49:19.026747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:19.366882 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:19.376645 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:19.411652 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:19.636460 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:19.637575 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:19.888667 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:19.990770 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:19.997530 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.268038 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.269293 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.271670 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:49:20.274467 Beacon (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS CH: 6, PRIVACY 23:49:20.297986 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:20.492967 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.502751 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:20.629491 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.707738 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:20.899123 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.901458 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:20.989459 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:21.124700 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:21.219413 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:21.259747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:21.321793 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY 23:49:21.530624 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:21.531691 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, PRIVACY 23:49:21.533326 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY 23:49:21.833759 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY I didn't get the "Beacon" entries before. I expected to see actual data packets in tcpdump, but I assume they are not in the dump because we're only looking at the 802.11 events with -y ieee802_11? Other than this, all the other oddities are the same, and hopefully insignificant. signature.asc Description: OpenPGP digital signature
Re: Connecting P1i to FreeBSD
It might be a problem in the rum interface, because the device connects perfectly to the iwi interface in the laptop. Here are ifconfigs for the devices: rum0: flags=108843 metric 0 mtu 1500 ether 00:1c:f0:9d:08:b3 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid bsd7adhoc channel 6 (2437 Mhz 11g) bssid c6:98:35:ef:28:ae authmode OPEN privacy OFF txpower 50 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS iwi0: flags=8843 metric 0 mtu 1500 ether 00:0e:35:4a:2d:e8 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid omg channel 10 (2457 Mhz 11g) bssid c6:e6:a6:49:5c:d7 authmode OPEN privacy OFF bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS I don't know if the differences are significant, but the first one doesn't work and the second one does. One other thing: when on Windows (i.e. when it's working), the "link" LED on the rum NIC flashes constantly, as well as the "act" LED. On FreeBSD (when it's not), the "link" LED flashes occasionally (presumably when there's data traffic), and the "act" link flashes as constantly as before. Maybe it has something to do with the missing beacons from my past messages? The rum(4) man page has a CAVEAT about automatic control of transmit speed but forcing it to DS/1Mbps mode 11b doesn't help (the device is 11b-only). signature.asc Description: OpenPGP digital signature
Re: Multiple routing tables in action...
Sorry for my late entry into this interesting subject, however, what exactly was the original post displaying? I have 6.3-Stable running, and I don't even have the first command listed as "setfib", on my system. What did the setfib -l command do, so that you were able to see two distinctly different routing tables? On Sat, 2008-04-26 at 21:09 +0300, Ivo Vachkov wrote: > when do we get to see those patches ? :) > > On Sat, Apr 26, 2008 at 6:44 PM, Julian Elischer <[EMAIL PROTECTED]> wrote: > > A little progress report > > > > From a recently installed (6.3) machine (plus patches) > > > > wsa02:julian 9] setfib -0 netstat -rn > > Routing tables > > > > Internet: > > DestinationGatewayFlagsRefs Use Netif Expire > > default172.28.14.1UGS 0 788 bce1 > > 127.0.0.1 127.0.0.1 UH 0 379lo0 > > 172.28.5/24172.28.14.1UGS 0 10 bce1 > > 172.28.6.32/28 link#2 UC 00em0 > > 172.28.6.3300:15:2b:46:56:90 UHLW10em0 1190 > > 172.28.14/24 link#6 UC 00 bce1 > > 172.28.14.100:04:23:b5:a9:2b UHLW30 bce1 1117 > > wsa02:julian 10] setfib -1 netstat -rn > > Routing tables > > > > Internet: > > DestinationGatewayFlagsRefs Use Netif Expire > > default172.28.6.33UGS 00em0 > > 1.1.1/28 172.28.6.33UGS 00em0 > > 127.0.0.1 127.0.0.1 UH 01lo0 > > 172.28.5/24172.28.6.33UGS 06em0 > > 172.28.6.32/28 link#2 UC 00em0 > > 172.28.6.3300:15:2b:46:56:90 UHLW46em0 1182 > > wsa02:rjulian 11] > > > > ___ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting P1i to FreeBSD
On Sun, Apr 27, 2008 at 7:52 AM, Ivan Voras <[EMAIL PROTECTED]> wrote: > Ivan Voras wrote: > > > Sepherosa Ziehau wrote: > > > > > > > Are you sure that your device works under IBSS mode? > > > > > > > Yes, since Windows doesn't support creating an AP from the card, and it > connects to Windows. Unless there are other modes that can do the same > thing... > > > > Actually there is a difference; here's a dump from laptop where the device > connects to the Windows machine: > > 23:49:18.013539 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.045340 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:18.148408 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.374477 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.377198 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.379066 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:18.659907 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:18.734842 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:18.762218 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.005423 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.008301 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:19.026747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.366882 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.376645 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.411652 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.636460 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.637575 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:19.888667 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.990770 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:19.997530 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.268038 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.269293 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.271670 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:20.274467 Beacon (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 > 36.0 54.0 Mbit] ESS CH: 6, PRIVACY > 23:49:20.297986 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:20.492967 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.502751 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:20.629491 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.707738 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:20.899123 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.901458 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:20.989459 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.124700 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.219413 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:21.259747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.321793 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > 23:49:21.530624 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.531691 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > PRIVACY > 23:49:21.533326 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > 23:49:21.833759 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, PRIVACY > > I didn't get the "Beacon" entries before. I expected to see actual data > packets in tcpdump, but I assume they are not in the dump because we're only > looking at the 802.11 events with -y ieee802_11? > I think you are using iwi to do the tap, could you put iwi into monitor mode, since iwi is "smart" device which may filter certain type of frames in non-monitor mode? I tested my rum: the beacon template set in the hardware is trashed in a strange a pattern What I got in the air; fc duration and certain part of mac address is trashed: 11:04:57.256700 Assoc Request (sephe-adhoc) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 0x: 2a01 0032 0430 4860 6c18 f32f 077a 0x0010: 4e9c 3b6a eb9f b01d afbe e402 0x0020: 6400 2200 000b 7365 7068 652d 6164 686f 0x0030: 6301 0882 848b 960c 1218 2403 0101 0602 0x0040: 9056 e96b 88d0 f6ef 5cc9 1d The actual beacon mbuf content: 80 00 00 00 ff ff ff ff ff ff 00 18 f3 2f 07 7a 4e 9c 3b 6a eb 9f 00 00 00 00 00 00 00 00 00 00 64 00 22 00 0
Re: Connecting P1i to FreeBSD
On Sun, Apr 27, 2008 at 11:51 AM, Sepherosa Ziehau <[EMAIL PROTECTED]> wrote: > > On Sun, Apr 27, 2008 at 7:52 AM, Ivan Voras <[EMAIL PROTECTED]> wrote: > > Ivan Voras wrote: > > > > > Sepherosa Ziehau wrote: > > > > > > > > > > Are you sure that your device works under IBSS mode? > > > > > > > > > > Yes, since Windows doesn't support creating an AP from the card, and it > > connects to Windows. Unless there are other modes that can do the same > > thing... > > > > > > > Actually there is a difference; here's a dump from laptop where the device > > connects to the Windows machine: > > > > 23:49:18.013539 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:18.045340 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:18.148408 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:18.374477 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:18.377198 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:18.379066 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > > 23:49:18.659907 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:18.734842 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:18.762218 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:19.005423 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:19.008301 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > > 23:49:19.026747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:19.366882 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:19.376645 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:19.411652 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:19.636460 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:19.637575 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:19.888667 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:19.990770 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:19.997530 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.268038 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.269293 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.271670 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > > 23:49:20.274467 Beacon (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 > > 36.0 54.0 Mbit] ESS CH: 6, PRIVACY > > 23:49:20.297986 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:20.492967 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.502751 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:20.629491 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.707738 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:20.899123 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.901458 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:20.989459 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:21.124700 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:21.219413 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:21.259747 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:21.321793 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > 23:49:21.530624 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:21.531691 Probe Response (A2) [1.0* 2.0* 5.5* 11.0* Mbit] CH: 6, > > PRIVACY > > 23:49:21.533326 Probe Response (SpeedTouch425488) [1.0* 2.0* 5.5* 11.0* > > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY > > 23:49:21.833759 Beacon (A2) [1.0* 2.0* 5.5* 11.0* Mbit] IBSS CH: 6, > PRIVACY > > > > I didn't get the "Beacon" entries before. I expected to see actual data > > packets in tcpdump, but I assume they are not in the dump because we're > only > > looking at the 802.11 events with -y ieee802_11? > > > > I think you are using iwi to do the tap, could you put iwi into > monitor mode, since iwi is "smart" device which may filter certain > type of frames in non-monitor mode? > > I tested my rum: the beacon template set in the hardware is trashed in > a strange a pattern BTW, the pattern is anything beyond 64bytes will be wrapped. See the dump and the beacon content. > > What I got in the air; fc duration and certain part of mac address is > t
Re: Multiple routing tables in action...
Martes G Wigglesworth wrote: Sorry for my late entry into this interesting subject, however, what exactly was the original post displaying? I have 6.3-Stable running, and I don't even have the first command listed as "setfib", on my system. What did the setfib -l command do, so that you were able to see two distinctly different routing tables? setfib -1 .. (that is "minus one") executes the following command with the default routing table (fib) set to the second table (table 1). setfib -0 (that's "minus zero") runs the folling arguments as a command with it's default routing table set to the first routing table (table 0). the setfib command is added as part of the patch. On Sat, 2008-04-26 at 21:09 +0300, Ivo Vachkov wrote: when do we get to see those patches ? :) On Sat, Apr 26, 2008 at 6:44 PM, Julian Elischer <[EMAIL PROTECTED]> wrote: A little progress report From a recently installed (6.3) machine (plus patches) wsa02:julian 9] setfib -0 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.28.14.1UGS 0 788 bce1 127.0.0.1 127.0.0.1 UH 0 379lo0 172.28.5/24172.28.14.1UGS 0 10 bce1 172.28.6.32/28 link#2 UC 00em0 172.28.6.3300:15:2b:46:56:90 UHLW10em0 1190 172.28.14/24 link#6 UC 00 bce1 172.28.14.100:04:23:b5:a9:2b UHLW30 bce1 1117 wsa02:julian 10] setfib -1 netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.28.6.33UGS 00em0 1.1.1/28 172.28.6.33UGS 00em0 127.0.0.1 127.0.0.1 UH 01lo0 172.28.5/24172.28.6.33UGS 06em0 172.28.6.32/28 link#2 UC 00em0 172.28.6.3300:15:2b:46:56:90 UHLW46em0 1182 wsa02:rjulian 11] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
