Re: IPSec NAT-T in transport mode
On Fri, 22 Jan 2010, Nat Howard wrote: I'm very interested in this problem -- I want to run an L2TP server myself. Is anyone actually working on this? I might be able to chip in a few bucks... But I'm not seeing bad checksums. Here's my setup: L2tp server AB Freebsd NAT box C ---internal network---D my mac Where should I be seeing the bad checksums? A, B, C, or D? Looking only at B, I don't see any bad udp checksums, but I'm seeing a bunch of these (IP numbers changed to bracketed names): This doesn't say if you are using IPsec but I will asume so, that would mean that you D my mac would initiate the connection and the A node L2tp server would then be the other end. If that's a FreeBSD box as well, you should check statistics there. The NAT gateway in between has nothing to do with this, only the IPsec ends. /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, Jan 23, 2010 at 01:23:28AM +, Adrian Wontroba typed: I concur that the 235 MB size of an amd64 8.0 kernel is a bit of a surprise. An i386 kernel is a mere 135 MB. IMO increasing the sysinstall default root slice size for at least amd64 would be a good thing. To be a little more precise: it's not the kernel that is so big. It's all the (mostly not needed) modules and symbol files that fill up / ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, 23 Jan 2010, Ruben de Groot wrote: On Sat, Jan 23, 2010 at 01:23:28AM +, Adrian Wontroba typed: I concur that the 235 MB size of an amd64 8.0 kernel is a bit of a surprise. An i386 kernel is a mere 135 MB. IMO increasing the sysinstall default root slice size for at least amd64 would be a good thing. To be a little more precise: it's not the kernel that is so big. It's all the (mostly not needed) modules and symbol files that fill up / Maybe they could be put somewhere else.. I don't think you need them unless remote debugging and in that case you are multiuser (I would have thought anyway). If they went into /usr then /boot could remain slim. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: top Segmentation faulting on 8.0p2 amd64 (nss_ldapd problem?)
I had exactly this problem. Removing an old /etc/localtime fixed the problem. /glz --On January 23, 2010 2:02:04 +0100 Harald Schmalzbauer h.schmalzba...@omnilan.de wrote: Mikolaj Golub schrieb am 22.01.2010 23:26 (localtime): On Wed, 20 Jan 2010 08:06:23 +0100 Harald Schmalzbauer wrote: Dear all, I have no idea why top crashes with segmentation fault on my amd64 machine running FreeBSD 8.0-RELEASE-p2. If someone wants to have a loot at the core dump: http://www.schmalzbauer.de/downloads/top.core core file is useless without binary and libraries. So it is better to run gdb on your host, produce backtrace and post here: gdb /usr/bin/top top.core bt And sure a backtrace from the top built with -g would be much better. cd /usr/src/usr.bin/top CFLAGS=-g make Unfortunately nss_ldap seems to be the culprit. gdb /usr/bin/top top.core 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 amd64-marcel-freebsd... Core was generated by `top'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libncurses.so.8...done. Loaded symbols for /lib/libncurses.so.8 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libkvm.so.5...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/nss_ldap.so.1...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 bt: # 0 0x000800d08403 in __nss_compat_gethostbyname () from # /usr/local/lib/nss_ldap.so.1 0 0x000800d08403 in # __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 1 # 0x000800d0606f in _nss_ldap_getpwent_r () from # /usr/local/lib/nss_ldap.so.1 2 0x0008009ffc54 in # __nss_compat_getpwent_r () from /lib/libc.so.7 3 0x000800a84a3d in # nsdispatch () from /lib/libc.so.7 # 4 0x000800a50976 in getpwent_r () from /lib/libc.so.7 # 5 0x000800a50596 in sysctlbyname () from /lib/libc.so.7 # 6 0x00406c6d in machine_init (statics=0x7fffea30, # do_unames=1 '\001') at /usr/src/usr.bin/top/machine.c:257 # 7 0x00407a10 in main (argc=1, argv=0x7fffeb08) at /usr/src/usr.bin/top/../../contrib/top/top.c:458 I'm using nss_ldapd-0.7.2 and there's no way to live without ldap... Any help highly appreciated! Thanks, -Harry ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: top Segmentation faulting on 8.0p2 amd64 (nss_ldapd problem?)
Sorry, noise. Problem can back after a reboot. But now it only affects non super-users, it works just fine for root. When it first happened for me, even root cored. /glz --On January 23, 2010 13:57:41 +0100 Goran Lowkrantz goran.lowkra...@ismobile.com wrote: I had exactly this problem. Removing an old /etc/localtime fixed the problem. /glz --On January 23, 2010 2:02:04 +0100 Harald Schmalzbauer h.schmalzba...@omnilan.de wrote: Mikolaj Golub schrieb am 22.01.2010 23:26 (localtime): On Wed, 20 Jan 2010 08:06:23 +0100 Harald Schmalzbauer wrote: Dear all, I have no idea why top crashes with segmentation fault on my amd64 machine running FreeBSD 8.0-RELEASE-p2. If someone wants to have a loot at the core dump: http://www.schmalzbauer.de/downloads/top.core core file is useless without binary and libraries. So it is better to run gdb on your host, produce backtrace and post here: gdb /usr/bin/top top.core bt And sure a backtrace from the top built with -g would be much better. cd /usr/src/usr.bin/top CFLAGS=-g make Unfortunately nss_ldap seems to be the culprit. gdb /usr/bin/top top.core 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 amd64-marcel-freebsd... Core was generated by `top'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libncurses.so.8...done. Loaded symbols for /lib/libncurses.so.8 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libkvm.so.5...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/nss_ldap.so.1...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 bt: # 0 0x000800d08403 in __nss_compat_gethostbyname () from # /usr/local/lib/nss_ldap.so.1 0 0x000800d08403 in # __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 1 # 0x000800d0606f in _nss_ldap_getpwent_r () from # /usr/local/lib/nss_ldap.so.1 2 0x0008009ffc54 in # __nss_compat_getpwent_r () from /lib/libc.so.7 3 0x000800a84a3d in # nsdispatch () from /lib/libc.so.7 # 4 0x000800a50976 in getpwent_r () from /lib/libc.so.7 # 5 0x000800a50596 in sysctlbyname () from /lib/libc.so.7 # 6 0x00406c6d in machine_init (statics=0x7fffea30, # do_unames=1 '\001') at /usr/src/usr.bin/top/machine.c:257 # 7 0x00407a10 in main (argc=1, argv=0x7fffeb08) at /usr/src/usr.bin/top/../../contrib/top/top.c:458 I'm using nss_ldapd-0.7.2 and there's no way to live without ldap... Any help highly appreciated! Thanks, -Harry ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: top Segmentation faulting on 8.0p2 amd64 (nss_ldapd problem?)
On Sat, 23 Jan 2010 02:02:04 +0100 Harald Schmalzbauer wrote: gdb /usr/bin/top top.core 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 amd64-marcel-freebsd... Core was generated by `top'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libncurses.so.8...done. Loaded symbols for /lib/libncurses.so.8 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libkvm.so.5...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/nss_ldap.so.1...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 bt: #0 0x000800d08403 in __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 #0 0x000800d08403 in __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 #1 0x000800d0606f in _nss_ldap_getpwent_r () from /usr/local/lib/nss_ldap.so.1 It is worth rebuilding and installing nss_ldap.so with debugging symbols. #2 0x0008009ffc54 in __nss_compat_getpwent_r () from /lib/libc.so.7 #3 0x000800a84a3d in nsdispatch () from /lib/libc.so.7 #4 0x000800a50976 in getpwent_r () from /lib/libc.so.7 #5 0x000800a50596 in sysctlbyname () from /lib/libc.so.7 And may be libc.so :-) #6 0x00406c6d in machine_init (statics=0x7fffea30, do_unames=1 '\001') at /usr/src/usr.bin/top/machine.c:257 #7 0x00407a10 in main (argc=1, argv=0x7fffeb08) at /usr/src/usr.bin/top/../../contrib/top/top.c:458 I'm using nss_ldapd-0.7.2 and there's no way to live without ldap... -- Mikolaj Golub ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pack of CAM improvements
In article 4b55d9d4.1000...@freebsd.org you write: Hi. Hi! I've made a patch, that should solve set of problems of CAM ATA and CAM generally. I would like to ask for testing and feedback. What patch does: - It unifies bus reset/probe sequence. Whenever bus attached at boot or later, CAM will automatically reset and scan it. It allows to remove duplicate code from many drivers. - Any bus, attached before CAM completed it's boot-time initialization, will equally join to the process, delaying boot if needed. - New kern.cam.boot_delay loader tunable should help controllers that are still unable to register their buses in time (such as slow USB/ PCCard/ CardBus devices). - To allow synchronization between different CAM levels, concept of requests priorities was extended. Priorities now split between several run levels. Device can be freezed at specified level, allowing higher priority requests to pass. For example, no payload requests allowed, until PMP driver enable port. ATA XPT negotiate transfer parameters, periph driver configure caching and so on. - Frozen requests are no more counted by request allocation scheduler. It fixes deadlocks, when frozen low priority payload requests occupying slots, required by higher levels to manage theit execution. - Two last changes were holding proper ATA reinitialization and error recovery implementation. Now it is done: SATA controllers and Port Multipliers now implement automatic hot-plug and should correctly recover from timeouts and bus resets. Patch can be found here: http://people.freebsd.org/~mav/cam-ata.20100119.patch Feedback as always welcome. Ok, applied this to stable/8, and the good news is the box still seems to run (using ahci(4) on an sb700 controller and siis(4) on a SiI3132 pcie card, altho atm there's only an optical drive on that one.) But what this still doesn't fix is the broken `test unit ready' command on ada devices, which also makes things like `cdrecord -scanbus' hang the bus. :( (A few days ago I also got a hang after wanting to try out xfburn, I suspect for the same reason...) Here is my earlier report: http://docs.freebsd.org/cgi/mid.cgi?20090817163144.GA2991 Oh and I also still use this patch to scsi_cd.c to be able to read discs that fail the `read toc' command, like bluray (data) discs. PR s here: http://www.freebsd.org/cgi/query-pr.cgi?pr=138789 Index: src/sys/cam/scsi/scsi_cd.c === RCS file: /home/scvs/src/sys/cam/scsi/scsi_cd.c,v retrieving revision 1.107.2.6 diff -u -p -u -r1.107.2.6 scsi_cd.c --- src/sys/cam/scsi/scsi_cd.c 25 Dec 2009 08:06:35 - 1.107.2.6 +++ src/sys/cam/scsi/scsi_cd.c 23 Jan 2010 13:29:19 - @@ -2874,11 +2874,17 @@ cdcheckmedia(struct cam_periph *periph) } softc-flags |= CD_FLAG_VALID_TOC; + +bailout: softc-disk-d_sectorsize = softc-params.blksize; softc-disk-d_mediasize = (off_t)softc-params.blksize * softc-params.disksize; +/* if bailout: + * is here read requests will fail when the toc cant be read although + * CD_FLAG_VALID_MEDIA is set. + */ /* * We unconditionally (re)set the blocksize each time the ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS performance degradation over time
On 1/19/2010 12:01 PM, Jeremy Chadwick wrote: On Tue, Jan 19, 2010 at 11:40:50AM -0500, Garrett Moore wrote: I've been watching my memory usage and I have no idea what is consuming memory as 'Active'. Last night I had around 6500MB 'Active' again, 1500MB Wired, no inact, ~30MB buf, no free, and ~100MB swap used. My performance copying ZFS-ZFS was again slow (1MB/s). I tried killing rTorrent and no significant amount of memory was reclaimed - maybe 100MB. `ps aux` showed no processes using any significant amount of memory, and I was definitely nowhere near 6500MB usage. I tried running the perl oneliner again to hog a bunch of memory, and almost all of the Active memory was IMMEDIATELY marked as Free, and my performance was excellent again. I'm having this same issue, although my performance does not go back to freshly booted levels it still goes from 1MBs to ~11MB/s after running that Perl one liner. I'm running RELENG 8 as of about 2 days ago FreeBSD 8.0-STABLE #2 r202777: Fri Jan 22 00:15:43 EST 2010 [...] amd64 Just to be clear it also seems to be related to something rtorrent does while downloading torrents but it's not rtorrent itself using the memory because quitting rtorrent doesn't release more than 100MB of multiple GB of memory marked as active but running the Perl one liner does. I'm not sure what in userland could be causing the issue. The only things I've installed are rTorrent, lighttpd, samba, smartmontools, vim, bash, Python, Perl, and SABNZBd. There is nothing that *should* be consuming any serious amount of memory. I've two recommendations: 1) Have you considered upgrading to RELENG_8 (e.g. 8.0-STABLE) instead of sticking with 8.0-RELEASE? There's been a recent MFC to RELENG_8 which pertain to ARC drainage. I'm referring to the commit labelled revision 1.22.2.2 (RELENG_8): I definitely have that commit, see above. I just checked my arc size and it's only using ~170 of a ~600MB limit. This is after running the Perl script and without the strangely large amount of active memory, I forgot to run on before as well. This machine is just a personal file server so I can restart it as needed for testing and I have serial console access to it if needed. Thanks, Jonathan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD NFS client/Linux NFS server issue
On Fri, 22 Jan 2010 17:13:09 -0500 (EST) Rick Macklem wrote: On Fri, 22 Jan 2010, Rick Macklem wrote: There should probably be some sort of 3 way handshake between the code in nfs_asyncio() after calling nfs_nfsnewiod() and the code near the beginning of nfssvc_iod(), but I think the following somewhat cheesy fix might do the trick: [stuff deleted] I know it's a little weird to reply to my own posting, but I think this might be a reasonable patch (I have only tested it for a few minutes at this point). I basically redefined nfs_iodwant[] as a tri-state variable (although it was a struct proc *, it was only tested NULL/non-NULL). 0 - was NULL 1 - was non-NULL -1 - just created by nfs_asyncio() and will be used by it I'll keep testing it, but hopefully someone else can test and/or review it... rick I applied your patch to FreeBSD8.0 (the box I get on weekend :-), mounted 10 shares, set vfs.nfs.iodmaxidle=10 (to have nfsiod creation more frequently) and have been running tests for 4 hours -- just to check the patch does not break anything. No issues have been detected. It would be very nice to have this patch committed. -- Mikolaj Golub ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make buildkernel failing on zfs - fixed but now everything is slow
Hi again folks. Thanks to all the suggestions I have gotten the new world/kernel up and running finally, unfortunately I seem to be having problems now. The entire system is sluggish and unresponsive. Even trying to scroll through a vi session jumps and pauses all the time. Whether it is bringing up an SSH session, something through apache or anything else on the system is can take anywhere up to 20 second to respond which is not good. top gives me the impression that its not any kind of runaway process or anything like that last pid: 78629; load averages: 0.00, 0.03, 0.06 116 processes: 1 running, 115 sleeping CPU: 0.6% user, 0.0% nice, 0.6% system, 0.0% interrupt, 98.9% idle Mem: 787M Active, 2057M Inact, 200M Wired, 101M Cache, 112M Buf, 114M Free Swap: 8000M Total, 1708K Used, 7998M Free There's nothing obvious that I can see in any other logfiles, are there any tools or other things that I can use to figure out why the system is so sluggish now? Cheers Colin. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Beginning the 7.3-RELEASE release cycle...
Just a quick note to say we're beginning the release cycle for 7.3-RELEASE. Code freeze on stable/7 began now, and stable/7 has been adjusted to say that it is 7.3-PRERELEASE to reflect that. More details will follow but this is the current target schedule: 01/22: code freeze 01/25: BETA 02/08: RC1 02/22: RC2 03/01: RELEASE Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, Jan 23, 2010 at 10:43:49PM +1030, Daniel O'Connor wrote: On Sat, 23 Jan 2010, Ruben de Groot wrote: To be a little more precise: it's not the kernel that is so big. It's all the (mostly not needed) modules and symbol files that fill up / Maybe they could be put somewhere else.. I have a stupid question: Why are modules built and installed for things that are already included in the kernel? That would seem (I haven't looked) to be a simple change that would both speed up builds and shrink /boot/kernel. -- Barney Wolff I never met a computer I didn't like. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pack of CAM improvements
On Sat, 23 Jan 2010 15:07:47 +0100 (CET) Juergen Lock n...@jelal.kn-bremen.de wrote: But what this still doesn't fix is the broken `test unit ready' command on ada devices, which also makes things like `cdrecord -scanbus' hang the bus. :( (A few days ago I also got a hang after wanting to try out xfburn, I suspect for the same reason...) Here is my earlier report: http://docs.freebsd.org/cgi/mid.cgi?20090817163144.GA2991 I started seeing a problem a few days ago with one of my DVD drives (a burner at cd0) under 9-current, which makes it impossible to use it even to simply read a DVD. Here the (rather strange IMO) output in dmesg: cd0: HL-DT-ST DVD-RAM GSA-H54N 1.00 Removable CD-ROM SCSI-0 device cd0: 66.700MB/s transfers (UDMA4, PIO size 65534bytes) cd0: Attempt to query device size failed: UNIT ATTENTION, Power on, reset, or bus device reset occurred cd1 at ata0 bus 0 scbus6 target 1 lun 0 cd1: TSSTcorp DVD-ROM SH-D162D SB01 Removable CD-ROM SCSI-0 device cd1: 33.300MB/s transfers (UDMA2, PIO size 65534bytes) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed I haven't the foggiest why cd0 behaves diffrently from cd1, which is a vanilla DVD drive and just works. --- Gary Jennejohn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: IPSec NAT-T in transport mode
Much obliged for the answer, Bjoern, but I don't follow your logic -- If the NAT-T implementation on the L2TP Server (a freebsd box) is broken, wouldn't it be the one generating things with the wrong checksum? If that's so, then surely the point A wouldn't record seeing any incoming checksum errors, as they would all be outgoing packets, correct? Thanks for helping to shed light on this puzzle! On Jan 23, 2010, at 5:09 AM, Bjoern A. Zeeb wrote: On Fri, 22 Jan 2010, Nat Howard wrote: I'm very interested in this problem -- I want to run an L2TP server myself. Is anyone actually working on this? I might be able to chip in a few bucks... But I'm not seeing bad checksums. Here's my setup: L2tp server AB Freebsd NAT box C ---internal network---D my mac Where should I be seeing the bad checksums? A, B, C, or D? Looking only at B, I don't see any bad udp checksums, but I'm seeing a bunch of these (IP numbers changed to bracketed names): This doesn't say if you are using IPsec but I will asume so, that would mean that you D my mac would initiate the connection and the A node L2tp server would then be the other end. If that's a FreeBSD box as well, you should check statistics there. The NAT gateway in between has nothing to do with this, only the IPsec ends. /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make buildkernel failing on zfs - fixed but now everything is slow
On Sat, Jan 23, 2010 at 03:27:12PM +, Colin wrote: There's nothing obvious that I can see in any other logfiles, are there any tools or other things that I can use to figure out why the system is so sluggish now? A couple things I can think of: vmstat -c 30 -w 1 vmstat -i vmstat -s -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS performance degradation over time
On Wed, Jan 20, 2010 at 11:47:30AM +0100, Alexander Leidinger wrote: Quoting Jeremy Chadwick free...@jdc.parodius.com (from Tue, 19 Jan 2010 09:01:01 -0800): I've two recommendations: 1) Have you considered upgrading to RELENG_8 (e.g. 8.0-STABLE) instead of sticking with 8.0-RELEASE? There's been a recent MFC to RELENG_8 which pertain to ARC drainage. I'm referring to the commit labelled revision 1.22.2.2 (RELENG_8): http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c This patch can be merged stand-alone if necessary, no need to go to RELENG_8 if there are reservations. The commit you refer to above is just doing this: limiting the arc more to the arc_max than it was the case before. This patch is in 7-stable too (in case someone is interested). Two weeks ago, we started experiencing similar symptoms on the pointyhat package cluster. This was on 9.0-CURRENT from last September. Upgrading to last weeks HEAD has solved the problem for us. The system is heavily loaded both on CPU, memory and disk, and since the original patch was committed back in October, my guess is that it was this specific commit that solved the issue. I'd recommend people still experiencing this issue to upgrade to a system that includes this change, be it 8.0-STABLE or 7.2-STABLE after January 8, or manually merging it. Cheers, -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgplvfNZgAtur.pgp Description: PGP signature
Re: make buildkernel failing on zfs - fixed but now everything is slow
Jeremy Chadwick wrote: On Sat, Jan 23, 2010 at 03:27:12PM +, Colin wrote: There's nothing obvious that I can see in any other logfiles, are there any tools or other things that I can use to figure out why the system is so sluggish now? A couple things I can think of: vmstat -c 30 -w 1 vmstat -i vmstat -s Thanks for the reply. I must admit that the ins and outs of paging and interrupts are something I don't have much expertise in. I've asked the colo company to look into it but I've put the output of those commands into pastebin incase anything stands out. http://www.pastebin.org/81107 You guys have been very helpful these couple of months so I guess I'd best go find that donate button. Its the least I can do! Cheers, Colin. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, Jan 23, 2010 at 09:04:57PM +0100, Miroslav Lachman wrote: Jeremy Chadwick wrote: [...] While I'm here, I figure I'd share how I end up partitioning most of the server systems I maintain. I use this general formula when building a new system, unless it's a 4-disk box (see bottom of mail): ad4s1a = /= UFS2= 1GB ad4s1b = swap = (2*RAM) or (2*MaxRAMPossible) ad4s1d = /var = UFS2+SU = 16GB (mandatory: must be= 2*RAM) ad4s1e = /tmp = UFS2+SU = (2*RAM) ad4s1f = /usr = UFS2+SU = 16GB Why you are suggesting /var = 2*RAM? Is it just for saving crash dumps or anything else? 1) Kernel panics/crash dumps are a big focus, yes. There's nothing worse than experiencing one, only to find out that savecore(8) can't do its job because /var/crash lacks the space. The system then boots anyway, swap starts getting used as normal, and the dump is therefore lost. Chance of debugging this post-mortem: zero. Additionally, people these days are often upgrading RAM in their systems as well; they start out with 1-2GB and create /var possibly with the knowledge of the above ordeal (re: crash dumps). Then they later upgrade to 4GB or 8GB RAM, and suddenly realise that they can't grow /var to deal with a crash dump. 2) I tend to keep a large amount of logs on systems, going back weeks if not months. This is intentional; it's amazing how often a customer or user will ask for some information from 3 or 4 months prior. FreeBSD's Apache port out-of-the-box logs to /var/log/httpd-*, and what we do is mostly web content serving. Let's also not forget about /var/log/maillog. I also advocate use of /var/log/all.log. I think it's fairly well-established at this point that I focus on server environments and not workstations (where /var probably doesn't need to be anywhere near that size). Folks should always review their needs, keeping expansion possibility in mind, when doing filesystem creation. And why so big /tmp? I am running servers with smaller sizes for years without any problem. My recommendation above doesn't imply those who don't use it will have problems -- each environment/system is different. That said, it's amazing how much software out there blindly uses /tmp. Last year I ran into this situation: an older server (1GB /tmp) started behaving oddly due to /tmp filling. A user of the system was using lynx to download some large files (an ISO image and something else, I forget what). lynx saves data its downloading to /tmp, and once it completes, the user is prompted where to save the data (CWD being the default). So tune lynx to use /var/tmp or some other path -- sure, that'd work, except lynx is just one of many programs which could do this. I'd rather not tune them all. :-) /tmp is more or less universal. Hope this sheds some light on my decisions. :-) -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Strange symbols in man-pages
Good day! I'm viewing dd man-page in gnome with gnome-terminal and i see some strange symbols instead `-`. For example from man dd(1): http://www.onlinedisk.ru/get_image.php?id=327964 The problem is rised only when i on ru_RU.UTF-8 locale. There is no problem with C-locale. Is this known problem and does anybody have a solution? Thanks in advance and keep me in Cc: please (i'm not subscribed to freebsd-stable@). PS. Using 8.0-STABLE. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Extra keys in multimedia keyboard doesn't work
Hi, I've recently got a new Microsoft Wireless Keyboard v2.0. I am curios whether multimedia keyboards work with FreeBSD out of box or should I configure something or use some quirks to enable extra keys. This keyboard works fine with Linux 2.6.30 all keys work otb. I tried using xev in FreeBSD but none of additional keys returned anything after pressing it. Are multimedia keyboard supported in FreeBSD or am I having bad luck with mine keyboard and should I send PR. My system: uname -a FreeBSD altstation 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 21:11:58 UTC 2010 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 usbconfig -u 1 -a 3 dump_device_desc ugen1.3: Microsoft 2.4GHz Transceiver v Microsoft at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x045e idProduct = 0x0745 bcdDevice = 0x0251 iManufacturer = 0x0001 Microsoft iProduct = 0x0002 Microsoft 2.4GHz Transceiver v6.0 iSerialNumber = 0x no string bNumConfigurations = 0x0001 Thanks in advance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
Jeremy Chadwick wrote: [...] 2) I tend to keep a large amount of logs on systems, going back weeks if not months. This is intentional; it's amazing how often a customer or user will ask for some information from 3 or 4 months prior. FreeBSD's Apache port out-of-the-box logs to /var/log/httpd-*, and what we do is mostly web content serving. Let's also not forget about /var/log/maillog. I also advocate use of /var/log/all.log. I think it's fairly well-established at this point that I focus on server environments and not workstations (where /var probably doesn't need to be anywhere near that size). Folks should always review their needs, keeping expansion possibility in mind, when doing filesystem creation. I keep log files (apache, lighttpd, proftpd, maillog) about 2 weeks on the machine (rotated daily), but I have them all for minimal 3 months on our central backup machine (I have most logs archived for more than 1 year - depending on free space of the backup storage ;]) And why so big /tmp? I am running servers with smaller sizes for years without any problem. My recommendation above doesn't imply those who don't use it will have problems -- each environment/system is different. That said, it's amazing how much software out there blindly uses /tmp. Last year I ran into this situation: an older server (1GB /tmp) started behaving oddly due to /tmp filling. A user of the system was using lynx to download some large files (an ISO image and something else, I forget what). lynx saves data its downloading to /tmp, and once it completes, the user is prompted where to save the data (CWD being the default). So tune lynx to use /var/tmp or some other path -- sure, that'd work, except lynx is just one of many programs which could do this. I'd rather not tune them all. :-) /tmp is more or less universal. Most of our servers are without shell users and without programs like lynx :) So I hope I am safe with 1-2GB /tmp (I don't remember any accident with no space left on device /tmp for past 4-5 years. Maybe I am just lucky guy ;) Hope this sheds some light on my decisions. :-) Thank you for you explanation, it makes sense in your environment. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RELENG_7: SVN rev 202895 fails to compile
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The attached patch corrects the number of arguments given to vfs_unbusy() as introduced by SVN rev 202895 on the assumption that the idea was to migrate from vfs_rel() to vfs_unbusy() in those instances, imb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAktbaG0ACgkQQv9rrgRC1JLiWACeNriU5ahu1GC5BmXKfnn0L5fQ oSgAn0/x4P0joInG0ZKYmzM65MDVns+v =JWN4 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_7: SVN rev 202895 fails to compile
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/10 16:21, Michael Butler wrote: The attached patch corrects the number of arguments given to vfs_unbusy() as introduced by SVN rev 202895 on the assumption that the idea was to migrate from vfs_rel() to vfs_unbusy() in those instances, imb Ugh .. I hate it when that happens :-( *** src/sys/kern/vfs_syscalls.c.origSat Jan 23 16:13:07 2010 - --- src/sys/kern/vfs_syscalls.c Sat Jan 23 16:13:39 2010 *** *** 337,343 } *buf = *sp; out: ! vfs_unbusy(mp); VFS_UNLOCK_GIANT(vfslocked); if (mtx_owned(Giant)) printf(statfs(%d): %s: %d\n, vfslocked, path, error); - --- 337,343 } *buf = *sp; out: ! vfs_unbusy(mp, td); VFS_UNLOCK_GIANT(vfslocked); if (mtx_owned(Giant)) printf(statfs(%d): %s: %d\n, vfslocked, path, error); *** *** 429,435 *buf = *sp; out: if (mp) ! vfs_unbusy(mp); VFS_UNLOCK_GIANT(vfslocked); return (error); } - --- 429,435 *buf = *sp; out: if (mp) ! vfs_unbusy(mp, td); VFS_UNLOCK_GIANT(vfslocked); return (error); } -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAktbaU4ACgkQQv9rrgRC1JJFNACfT1cQo6RUiC6qWc5CfkyTDMhW nQgAn0TZwJxIR7Ijpt39yaAV+KH/+GFN =Fagv -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, Jan 23, 2010 at 12:21:48PM -0800, Jeremy Chadwick wrote: On Sat, Jan 23, 2010 at 09:04:57PM +0100, Miroslav Lachman wrote: Jeremy Chadwick wrote: ... And why so big /tmp? I am running servers with smaller sizes for years without any problem. My recommendation above doesn't imply those who don't use it will have problems -- each environment/system is different. That said, it's amazing how much software out there blindly uses /tmp. Last year I ran into this situation: an older server (1GB /tmp) started behaving oddly due to /tmp filling. A user of the system was using lynx to download some large files (an ISO image and something else, I forget what). lynx saves data its downloading to /tmp, and once it completes, the user is prompted where to save the data (CWD being the default). Another example: the stock /usr/bin/sort uses /tmp for its temporary storage when it needs to start using disk. You can redirect that via -T if you think ahead and realize that it's going to be a problem, but if you are just whipping up a quick shell script and later happen to run it on much bigger inputs than you were expecting you can run out of space on /. (Yes, that happened to me fairly recently on several systems, when some log files weren't being rotated on schedule.) An alternative solution is to symlink /tmp to /var/tmp, which I've done on many systems, assuming that nothing in the /etc/rc sequence will need /tmp before filesystems are mounted. (I suppose putting it on its own filesystem also assumes that.) In general, I think you've got a good idea and I plan to start adopting that in the future. -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pack of CAM improvements
On Tue, 19 Jan 2010, Alexander Motin wrote: Hi. I've made a patch, that should solve set of problems of CAM ATA and CAM generally. I would like to ask for testing and feedback. [snip] Hello, applied this patch to 8-stable recompiled the kernel and rebooted. The kernel did not boot it hangs while probing the ahci-controller. The error message is: ahcich0: Timeout on slot 0 ahcich0: is 0002 cs ss 0 rs 0001 tfs 50 serr run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config After that the kernel hangs forever. A 8-stable without the patch shows ahcich0: Timeout on slot 0 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config and boots but doesn't find any hard disks. It's an Asus M3A-H/HDMI motherboard with AMD SB710 southbridge. The harddisk is an Western Digital WD10EAVS. Both are working with the old ata implementation in AHCI mode. pciconf output of the controller is atap...@pci0:0:17:0: class=0x010601 card=0x43911002 chip=0x43911002 rev=0x00 hdr=0x00 Thanks, Yamagi -- Homepage: www.yamagi.org Jabber: yam...@yamagi.org GnuPG/GPG:0xEFBCCBCB ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_7: SVN rev 202895 fails to compile
On Sat, Jan 23, 2010 at 04:25:35PM -0500, Michael Butler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/10 16:21, Michael Butler wrote: The attached patch corrects the number of arguments given to vfs_unbusy() as introduced by SVN rev 202895 on the assumption that the idea was to migrate from vfs_rel() to vfs_unbusy() in those instances, imb Thank you for the report, it should be fixed by r202902. pgp2nV71WR6zp.pgp Description: PGP signature
Re: FreeBSD NFS client/Linux NFS server issue
On Sat, 23 Jan 2010, Mikolaj Golub wrote: I applied your patch to FreeBSD8.0 (the box I get on weekend :-), mounted 10 shares, set vfs.nfs.iodmaxidle=10 (to have nfsiod creation more frequently) and have been running tests for 4 hours -- just to check the patch does not break anything. No issues have been detected. It would be very nice to have this patch committed. Thanks for doing the testing and good work w.r.t. figuring out the race. (I'll admit I didn't really have a clue what was causing your problem.) rick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8-stable crashes in vmware (possible em driver issue?)
I have a fairly recent 8-stable machine running under VMWare ESXi 3.5 (amd64 guest), which apparently crashes every few days from the same causes: em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o packet header Panic string: sbsndptr: sockbuf 0xff007cca8c20 and mbuf 0xff00490a6400 clashing More information available here: http://ivoras.net/stuff/crash/info.0.txt http://ivoras.net/stuff/crash/core.txt.0.txt The crash looks like is provoked by ssh bruteforce attack attempts, some of which are blocked by an ipfw-based blocker. Any ideas? The machine was previously (until a month ago) running 7.2-RELEASE without these panics. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
From: Steven Friedrich free...@insightbb.com Date: Fri, 22 Jan 2010 22:20:30 -0500 Sender: owner-freebsd-sta...@freebsd.org On Friday 22 January 2010 06:32:02 pm Oliver Brandmueller wrote: Hi, On Fri, Jan 22, 2010 at 03:56:31PM -0500, Steven Friedrich wrote: in your /etc/make.conf, do you have a line like: makeoptions DEBUG=-g if so, comment it out. The GENEREIC kernel by default has the following config: makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols You don't need anything special in your make.conf In fact having the debug symbols is useful in many cases. So raising the default size for the / partition might be the better option (OK, doesn't help for already installed systems of course). - Oliver I'm sorry. My response to him should have been more precise. I was trying to clue him in on how to build a non-debug kernel, but my answer was in fact wrong. I said he may have a line in make.conf, but that was a mistake. I pulled the line from a kernel config file. If he wants to build a kernel with no symbols, as he stated he does, he needs to comment out the line and build a kernel. Could buildworld and installworld, too. But he and I went off topic. I should have changed the subject line to start a new thread to discuss building without symbols. He was complaining that it wasn't in the FAQ or the handbook. It's in GENERIC, which is required reading if you're ever going to build custom kernels. As for the main topic, I have been making 4GB root partitions for some time. Our disk requirements have been soaring over the last decade, while cost per MB have plummeted. I don't want to have to guess what sizes each partition should be. Just for the record and to avoid further confusion, building a kernel with debug symbols does not take any more space in root. Another copy of the kernel is built but not installed into /kernel. The copy of the kernel in /kernel is always symbol-less. Also, at the start of this thread, the OP said that he did a buildkernel and a buildworld. This is broken and may produce a non-bootable kernel. Always buildworld and then buildkernel so that the new toolchain is used to build the kernel. (This also has nothing to do with the original issue of the amount of space in the root partition being too small for amd64 systems, but I am hoping to avoid future issues.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: posting coding bounties, appropriate money amounts?
On Fri, Jan 22, 2010 at 07:20:18PM -0600, Adam Vande More wrote: I'd be willing to put up a thousand USD or possibly more depending on what sort of work was being considered. I suppose a better choice would be for someone here to make a list of issues which the community feels need attention, and put the pooled donations to whatever things had highest priority -- or, if that isn't plausible, then to what interested developers wanted to work on. To the best of my understanding, that is basically what donating to the FreeBSD Foundation accomplishes, although it would be nice so see some more transparency in their decision making process. As stated earlier in this thread, for tax reasons the Foundation can't be in a position to pass through specific funds targeted to specific projects. IMHO there's plenty of room for experimenting with different ways to get projects funded, especially for small specific task xyz needed. I can't really one of the people to try to set up such things, since I want to be one of the people taking advantage of it. A good first task would be for someone (TM) to put up a web page for tasks that the community would be willing to fund, with a sign-up sheet for volunteer donors, to gauge general interest in # of people who would be willing to contribute to particular tasks. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: atheros broadcast/multicast corruption with multiple hostap's
Russell Yount wrote:
On Sun, Jan 17, 2010 at 1:45 PM, Sam Leffler s...@errno.com
mailto:s...@errno.com wrote:
Russell Yount wrote:
On Sat, Jan 16, 2010 at 3:21 PM, Sam Leffler s...@errno.com
mailto:s...@errno.com mailto:s...@errno.com
mailto:s...@errno.com wrote:
Russell Yount wrote:
It seems AP to client broadcasts/multicasts traffic is
broken when using WPA2/802.11i with multiple hostapds in 8.0.
Only the SSID associated with the last hostapd to be
started has
AP to client broadcasts/multicasts being delivered correctly.
The AP and client are 8.0 freebsd systems althought I see
same
problems with windows XP as a client.
The AP has 4 hostapds configured to use TLS with client
certificates for
authentication. (hostapd recompiled with
HOSTAPD_CFLAGS=-DEAP_SERVER)
The AP and client radio are shown as ath0: AR5212 mac 5.9
RF5112
phy 4.3
in dmesg.
Client authenticate using client certificates associate
correctly
to all 4 SSIDs. Unicast traffic flows correctly between
clients
and AP
for all for 4 SSIDs. Client to AP broadcast/multicast
traffic works
on of 4 SSIDs. AP to client broadcast/multicast traffic
only works
on 1 of the SSIDs. I have documented this using ARP
broadcasts,
but normal IP broadcasts also observed to corrupted.
When an ARP request is send through the AP to an
associated client
it seems to be trashed on any of the SSID except the one
associated
with the last hostapd to be started. Here is the output of
client side
tcpdump showing the problems.
In the first client side tcpdump with the hostapd associated
with the SSID
being associaed with the last hostapd started and the traffic
flowing
normally.
In the second client side tcpdump with the hostapd associated
with the SSID
being not the last hostapd started the ARP request is resent
multiple times
and appears corrupted.
I would really like to find a fix for this.
Any help would be greatly appreciated.
This sounds like the crypto encap of the frame is clobbering the
mbuf contents. You can verify this by setting up multiple
vaps w/o
WPA. If this is the problem look for the mbuf copy logic for
mcast
frames and make sure a deep copy is done.
Sam
The four VAPs broadcast traffic works find without WPA if I
do not start hostapds on them
I have been trying to discovery why broadcast traffic only
works correctly on the VAP associated with the last hostapd to
be started. I have move with VAP has the working broadcast
traffic by restarting the hostapd
associated with it.
It would seem something in the WPA/802.1x layer initialization
remembers which hostapd was started last and that affected the
crypto encap.
I keep looking but do not see any place in the code that could
account for this.
It seems the corrupt crypto encap also happens on broadcast
between stations.
Please correct me if I am wrong:
but when using hostapd normally traffic is bridged withing the card.
So if a station sends to the VAP a broadcast it is actaully
sending a non- broadcast frame to the AP
and the AP sends the frame to all the other stations.
I told you waht the likely problem is. Look in the net80211 layer
in the kernel for the problem.
Sam
I tried to find problems in mbuf corruption
in ieee80211_output.c by placing
m = m_unshare(m,M_NOWAIT);
if (m == NULL) {
IEEE80211_DPRINTF(vap, IEEE80211_MSG_OUTPUT,
%s: cannot get writable mbuf\n, __func__);
return NULL;
}
at begining ieee80211_mbuf_adjust() and at
beginning of ieee80211_encap() with no change
in the broadcast traffic behaviour.
I tried then to in ieee80211_crypto.c substituting
flags |= IEEE80211_KEY_SWCRYPT;
for the encryption capabilities test code
if ((ic-ic_cryptocaps (1cipher)) == 0) {
IEEE80211_DPRINTF(vap, IEEE80211_MSG_CRYPTO,
%s: no h/w support for cipher %s, falling back to s/w\n,
__func__, cip-ic_name);
flags |= IEEE80211_KEY_SWCRYPT;
}
to force all the encryption
Re: Extra keys in multimedia keyboard doesn't work
On Sat, Jan 23, 2010 at 08:26:47PM +, Krzysztof Dajka wrote: Hi, I've recently got a new Microsoft Wireless Keyboard v2.0. I am curios whether multimedia keyboards work with FreeBSD out of box or should I configure something or use some quirks to enable extra keys. This keyboard works fine with Linux 2.6.30 all keys work otb. I tried using xev in FreeBSD but none of additional keys returned anything after pressing it. Are multimedia keyboard supported in FreeBSD or am I having bad luck with mine keyboard and should I send PR. Can you define extra keys in this case? I've a feeling you're referring to the multimedia keys and other stuff residing above the Function keys of the keyboard. If so: yes, FreeBSD's USB driver appears to lack support for these. Or, well, it did on RELENG_7 (which is a completely different USB driver), so it sounds like RELENG_8 needs some work in this regard. If someone wants to take up improving the quirks for this capability, let me know and I'll be more than happy to send them a free Microsoft Natural Ergonomic 4000 keyboard. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Strange symbols in man-pages
On Sat, Jan 23, 2010 at 11:34:14PM +0300, Ruslan Mahmatkhanov wrote: I'm viewing dd man-page in gnome with gnome-terminal and i see some strange symbols instead `-`. For example from man dd(1): http://www.onlinedisk.ru/get_image.php?id=327964 The problem is rised only when i on ru_RU.UTF-8 locale. There is no problem with C-locale. Is this known problem and does anybody have a solution? Thanks in advance and keep me in Cc: please (i'm not subscribed to freebsd-stable@). PS. Using 8.0-STABLE. http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/053804.html -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, 23 Jan 2010 16:20:54 -0800 Kevin Oberman ober...@es.net wrote: Just for the record and to avoid further confusion, building a kernel with debug symbols does not take any more space in root. Another copy of the kernel is built but not installed into /kernel. The copy of the kernel in /kernel is always symbol-less. Perhaps my question should be changed to: how do I configure the make world procedure so that no files ending in '*symbol' get installed in /boot/kernel? -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, January 23, 2010 8:35 pm, Torfinn Ingolfsen wrote: On Sat, 23 Jan 2010 16:20:54 -0800 Kevin Oberman ober...@es.net wrote: Just for the record and to avoid further confusion, building a kernel with debug symbols does not take any more space in root. Another copy of the kernel is built but not installed into /kernel. The copy of the kernel in /kernel is always symbol-less. Perhaps my question should be changed to: how do I configure the make world procedure so that no files ending in '*symbol' get installed in /boot/kernel? add the following to /etc/make.conf: INSTALL_NODEBUG=yes -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: device.hints isn't setting what I want
On 01/22/10 08:57, Freddie Cash wrote: Just as a side note: does mergemaster or installworld handle the installation of /boot/device.hints? Easy way to answer this category of questions. Do 'mergemaster -v', then when you get to the prompt for, *** The following files exist only in the installed ... hit ^C, then go look at the created temproot directory. If the file is in there, mergemaster will deal with it for you. If it's not there, mergemaster has no knowledge of it. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Strange symbols in man-pages
On 24.01.2010 04:45, Jeremy Chadwick wrote: On Sat, Jan 23, 2010 at 11:34:14PM +0300, Ruslan Mahmatkhanov wrote: I'm viewing dd man-page in gnome with gnome-terminal and i see some strange symbols instead `-`. For example from man dd(1): http://www.onlinedisk.ru/get_image.php?id=327964 The problem is rised only when i on ru_RU.UTF-8 locale. There is no problem with C-locale. Is this known problem and does anybody have a solution? Thanks in advance and keep me in Cc: please (i'm not subscribed to freebsd-stable@). PS. Using 8.0-STABLE. http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/053804.html So i can avoid this by setting alias in .cshrc: alias man env LANG=C man Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
