From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 01:44:42 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5085916A403 for ; Sun, 19 Nov 2006 01:44:42 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4193643D5E for ; Sun, 19 Nov 2006 01:44:35 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.6/8.13.6) with ESMTP id kAJ1ieqM029364; Sat, 18 Nov 2006 17:44:40 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200611181621.kAIGLblS075218@lava.sentex.ca> Date: Sat, 18 Nov 2006 17:44:40 -0800 (PST) From: John Polstra To: Mike Tancsa Cc: freebsd-net@freebsd.org Subject: Re: Serious em problems under -current on two different platforms X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 01:44:42 -0000 On 18-Nov-2006 Mike Tancsa wrote: > Havent had too much experience with PCIe riser cards yet, but have > had some experience with bad PCI-X risers. Any way to test to see if > its a bad riser card? The behaviour almost looks to be a hardware issue ? I agree. There's another slot (with its own riser) in the system, so I can try the card there and see what happens. I'll let you know. It could also be a bad card, of course. I have never seen it work properly yet. However, this wouldn't explain why the same kernel, driver, and userland is also failing to work with my Tyan 2721's onboard 82546EB. (It works flawlessly with earlier versions of the driver, even when ported to the up-to-date kernel.) The symptoms are pretty different on the Tyan, though. There, neither port will transmit anything, and you get TX watchdog timeouts every time you try. Go figure. Back to the Dell. Here's an interesting thing. I went away from the system for a few hours, and now I see that both ports are working again. I can ping flood either port and it works fine. But get this. I started a ping flood on em0, and it's sitting there drawing and erasing the ".", with no loss whatsoever. Now I start a normal 1-per-second ping on em1. Once a second, every time a ping goes through em1, the flood ping on em0 drops exactly 1 packet and draws an extra ".". Very strange. Clearly, operations on one port are affecting what happens on the other port. >>Are you using both ports of the NIC? With an older driver, em0 >>worked fine but em1 did not. > > Yes, actually I am testing the forwarding ability of the box. So far > with FreeBSD, I found that the 2 kernel options below > >#options ADAPTIVE_GIANT # Giant mutex is adaptive. > options NO_ADAPTIVE_MUTEXES > > and turning on fast_forwarding increases performance and > responsiveness of the box. Thanks for that info. It'll be useful to me once I get the NICs working. > any errors at the time on the switch port when things lock up ? Not as far as I can tell, but they may have dropped off the end of the stats by the time I checked. There doesn't seem to be a way to get cumulative stats from this switch, at least not through the GUI interface. John From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 09:12:31 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B6FE516A494 for ; Sun, 19 Nov 2006 09:12:31 +0000 (UTC) (envelope-from alexander.shevchenko@itv.ru) Received: from msk.itvgroup.ru (msk.itvgroup.ru [85.21.105.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59A2143D46 for ; Sun, 19 Nov 2006 09:12:21 +0000 (GMT) (envelope-from alexander.shevchenko@itv.ru) Received: (qmail 70284 invoked by uid 2550); 19 Nov 2006 09:12:29 -0000 Received: from 10.0.0.166 by msk.itvgroup.ru (envelope-from , uid 2550) with qmail-scanner-1.25st (clamdscan: 0.88/1485. spamassassin: 3.1.1. perlscan: 1.25st. Clear:RC:1(10.0.0.166):. Processed in 0.048156 secs); 19 Nov 2006 09:12:29 -0000 Received: from unknown (HELO ashevchenko) (alexander.shevchenko@[10.0.0.166]) (envelope-sender ) by msk.itvgroup.ru (qmail-ldap-1.03) with RC4-MD5 encrypted SMTP for ; 19 Nov 2006 09:12:28 -0000 From: =?koi8-r?B?4czFy9PBzsTSIPvF197FzsvP?= To: "'Gregory Edigarov'" , Date: Sun, 19 Nov 2006 12:12:28 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AccKMth81iPeWchZS7Ge4+jB3UoyYQBhw6Eg In-Reply-To: <455D8DF2.2020105@bestnet.kharkov.ua> X-Qmail-Scanner-Message-ID: <116392754892470278@msk.itvgroup.ru> Message-Id: <20061119091221.59A2143D46@mx1.FreeBSD.org> X-Mailman-Approved-At: Sun, 19 Nov 2006 13:11:38 +0000 Cc: Subject: RE: How to test a firewall with NAT? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 09:12:31 -0000 U can use "-n" flag for parsing rules before loading them pfctl -nvvv -f /etc/pf.conf Look at this port /usr/ports/sysutils/pftop pftop displays the active packetfilter states, rules, and queues -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Gregory Edigarov Sent: Friday, November 17, 2006 1:25 PM To: freebsd-net@freebsd.org Subject: How to test a firewall with NAT? Hello Everybody, I am trying to move one of my servers/routers from linux/iptables to freebsd/pf, and need a methodology of testing the pf firewall ruleset before it will go in production. I cannot experiment on live network, because it's a busy server. I only have one other machine available. What can I do and what tool can you recommend? Thank you. -- With best regards, Gregory Edigarov From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 13:57:33 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB8E216A412 for ; Sun, 19 Nov 2006 13:57:33 +0000 (UTC) (envelope-from julian@elischer.org) Received: from customer-domains.icp-qv1-irony10.iinet.net.au (customer-domains.icp-qv1-irony10.iinet.net.au [203.59.1.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CF043D62 for ; Sun, 19 Nov 2006 13:57:19 +0000 (GMT) (envelope-from julian@elischer.org) Received: from 203-166-240-248.dyn.iinet.net.au (HELO [192.168.3.3]) ([203.166.240.248]) by customer-domains.icp-qv1-irony10.iinet.net.au with ESMTP; 19 Nov 2006 21:56:17 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAM7wX0XLpvD4fmdsb2JhbAANjDoBAQ X-IronPort-AV: i="4.09,438,1157299200"; d="scan'208"; a="42870655:sNHT20838497058" Message-ID: <45606282.8070701@elischer.org> Date: Sun, 19 Nov 2006 05:56:18 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: Stefan References: <1763166525.20061118112222@aldiablo.net> In-Reply-To: <1763166525.20061118112222@aldiablo.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ping round trip times freebsd - windows X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 13:57:33 -0000 Stefan wrote: > -----BEGIN PGP SIGNED MESSAGE----- > I have an test-machine at work (w2003 server) and freebsd running in > an vmware (via dhcp). timing could be inaccurate when running under vmware. From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 21:13:57 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D855316A417 for ; Sun, 19 Nov 2006 21:13:57 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76BDD43D77 for ; Sun, 19 Nov 2006 21:13:37 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.6/8.13.6) with ESMTP id kAJLDlS3056410; Sun, 19 Nov 2006 13:13:47 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 19 Nov 2006 13:13:47 -0800 (PST) From: John Polstra To: Mike Tancsa Cc: freebsd-net@freebsd.org Subject: Re: Serious em problems under -current on two different platforms X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 21:13:57 -0000 On 19-Nov-2006 John Polstra wrote: > On 18-Nov-2006 Mike Tancsa wrote: >> Havent had too much experience with PCIe riser cards yet, but have >> had some experience with bad PCI-X risers. Any way to test to see if >> its a bad riser card? The behaviour almost looks to be a hardware issue ? > > I agree. There's another slot (with its own riser) in the system, so > I can try the card there and see what happens. I'll let you know. I moved the card to the other PCIe slot, but it's still behaving the same way. I'm going to try to get ahold of another card tomorrow and see if that works any better. John From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 22:44:05 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4523516A403 for ; Sun, 19 Nov 2006 22:44:05 +0000 (UTC) (envelope-from mime@traveller.cz) Received: from nxm.secservers.com (nxm.secservers.com [193.85.228.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BDC743D55 for ; Sun, 19 Nov 2006 22:43:52 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from [127.0.0.1] (nxm.secservers.com. [193.85.228.22]) by nxm.secservers.com (8.13.4/8.13.4) with ESMTP id kAJMi0Ai007892; Sun, 19 Nov 2006 23:44:01 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: John Polstra In-Reply-To: References: Content-Type: text/plain Date: Sun, 19 Nov 2006 23:43:55 +0100 Message-Id: <1163976235.31040.6.camel@genius.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Mike Tancsa Subject: Re: Serious em problems under -current on two different platforms X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 22:44:05 -0000 John Polstra wrote: > ... about serious problems with em cards. Can it be that the system is trying to drive the card with MSI (PCI Message Signalled Interrupts) which just recently went into CURRENT? On one system where I tried it em cards also didn't work. Did you try do disable it (with hw.pci.enable_msi=0 and hw.pci.enable_msix=0 in /boot/loader.conf)? Michal From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 22:52:30 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA8C716A416 for ; Sun, 19 Nov 2006 22:52:30 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73E6A43DA2 for ; Sun, 19 Nov 2006 22:52:11 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.6/8.13.6) with ESMTP id kAJMqMhe058523; Sun, 19 Nov 2006 14:52:22 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 19 Nov 2006 14:52:22 -0800 (PST) From: John Polstra To: Jack Vogel Cc: freebsd-net@freebsd.org, Mike Tancsa Subject: Re: Serious em problems under -current on two different platforms [SOLVED] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 22:52:30 -0000 Well, this is embarrassing. It turns out there were two different problems, neither one caused by the driver. 1. I had some ARP poisoning going on on my LAN, and that's why the two em interfaces in the Dell box appeared to be behaving so strangely. I fixed that, and the box is working just fine now with the driver from -current (both with and without MSI). The evidence was right there before my eyes, but it sure took me a long time to recognize it. 2. On the Tyan 2721 box, it was MSI that was causing the problem. It appears that MSI simply doesn't work on that motherboard. Once I disabled it, the driver started working fine. I had tried disabling MSI on the Dell much earlier, but I guess I never tried it on the Tyan. Maybe if I'm lucky, I'll find a BIOS upgrade that will fix it. I apologize for wasting everybody's time as well as for taking a year or so off Jack's life through adrenaline poisoning. John From owner-freebsd-net@FreeBSD.ORG Sun Nov 19 23:02:39 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35D2D16A40F for ; Sun, 19 Nov 2006 23:02:39 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF6F543D75 for ; Sun, 19 Nov 2006 23:02:05 +0000 (GMT) (envelope-from mike@sentex.net) Received: from BLUELAPIS.sentex.ca (cage.simianscience.com [64.7.134.1]) by smarthost2.sentex.ca (8.13.8/8.13.8) with SMTP id kAI18URg044213; Fri, 17 Nov 2006 20:08:31 -0500 (EST) (envelope-from mike@sentex.net) From: Mike Tancsa To: John Polstra Date: Fri, 17 Nov 2006 20:08:39 -0500 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: Serious em problems under -current on two different platforms X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2006 23:02:39 -0000 On Fri, 17 Nov 2006 12:41:58 -0800 (PST), in sentex.lists.freebsd.net you wrote: > >I can't get either port to send any packets at all. When I try, the >driver reports transmit watchdog timeouts. > >Is this stuff working for anybody at all? Hi, It is for me with the same NIC actually. Do you have your NIC in a 4X or 16X slot ? em0@pci4:0:0: class=3D0x020000 card=3D0x115e8086 chip=3D0x105e8086 rev=3D0x06 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/1000 PT' class =3D network subclass =3D ethernet em1@pci4:0:1: class=3D0x020000 card=3D0x115e8086 chip=3D0x105e8086 rev=3D0x06 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/1000 PT' class =3D network subclass =3D ethernet [r2-current]# dmesg | grep ^em em0: port 0x9000-0x901f mem 0xd5020000-0xd503ffff,0xd5000000-0xd501ffff irq 17 at device 0.0 on pci4 em0: Ethernet address: 00:15:17:0b:70:98 em0: [FAST] em1: port 0x9400-0x941f mem 0xd5040000-0xd505ffff,0xd5060000-0xd507ffff irq 18 at device 0.1 on pci4 em1: Ethernet address: 00:15:17:0b:70:99 em1: [FAST] [r2-current]#=20 Right now its running a kernel from the 11th, but I was briefly using it from the 16th with MSI support and it was fine as well. =20 Do you have them on xover cables or a switch ? ---Mike -------------------------------------------------------- Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 mike@sentex.net, (http://www.tancsa.com) From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 02:34:22 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2E6916A403; Mon, 20 Nov 2006 02:34:21 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1-b.corp.dcn.yahoo.com (mrout1-b.corp.dcn.yahoo.com [216.109.112.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFDCF43D6A; Mon, 20 Nov 2006 02:34:06 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1-b.corp.dcn.yahoo.com (8.13.8/8.13.6/y.out) with ESMTP id kAK2Y3eu042777; Sun, 19 Nov 2006 18:34:04 -0800 (PST) Date: Mon, 20 Nov 2006 11:34:02 +0900 Message-ID: From: gnn@freebsd.org To: current@freebsd.org User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.90 (i386-apple-darwin8.8.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: net@freebsd.org Subject: FAST_IPSEC + IPv6 in host mode... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 02:34:22 -0000 Hey, I'm going to be posting links to patches on a blog here: http://blogs.freebsdish.org/george/ The latest entry is for my FAST_IPSEC + IPv6 patch for host mode. I'm working on router mode. I'm also looking at the NetBSD SoC patch to see if it will work for us or not. Later, George From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 04:54:42 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 172B016A407; Mon, 20 Nov 2006 04:54:42 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDD6C43D49; Mon, 20 Nov 2006 04:54:27 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id kAK4seAr033789; Sun, 19 Nov 2006 23:54:40 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id kAK4sdat083568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Nov 2006 23:54:39 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200611200454.kAK4sdat083568@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 19 Nov 2006 23:54:50 -0500 To: Scott Long From: Mike Tancsa In-Reply-To: <4558E3DC.6080800@samsco.org> References: <2a41acea0611081719h31be096eu614d2f2325aff511@mail.gmail.com> <200611091536.kA9FaltD018819@lava.sentex.ca> <45534E76.6020906@samsco.org> <200611092200.kA9M0q1E020473@lava.sentex.ca> <200611102004.kAAK4iO9027778@lava.sentex.ca> <2a41acea0611101400w5b8cef40ob84ed6de181f3e2c@mail.gmail.com> <200611102221.kAAML6ol028630@lava.sentex.ca> <455570D8.6070000@samsco.org> <200611120412.kAC4CuIB035746@lava.sentex.ca> <45574ECA.4080207@samsco.org> <200611130040.kAD0etbp040637@lava.sentex.ca> <4557CECD.2000609@samsco.org> <200611130158.kAD1wdKE040908@lava.sentex.ca> <4557EF13.9060305@samsco.org> <200611130454.kAD4sZwe041556@lava.sentex.ca> <4557FF7A.8020704@samsco.org> <200611132054.kADKsFvK045726@lava.sentex.ca> <4558E3DC.6080800@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner3 X-Virus-Status: Clean Cc: freebsd-net , freebsd-stable@freebsd.org Subject: Re: Proposed 6.2 em RELEASE patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 04:54:42 -0000 At 04:30 PM 11/13/2006, Scott Long wrote: >Mike Tancsa wrote: >>At 12:15 AM 11/13/2006, Scott Long wrote: >> >>>Is this with EM_INTR_FAST enabled also? >> >>Without it, the 2 streams are definitely lossy on the management interface >> >> ---Mike > >Ok, and would you be able to test the polling options as well? Here are some more results. I am still going through testing with firewall rules as well as testing with the size of the routing table. Should get through that tomorrow. Again, this is the same setup as described at http://www.tancsa.com/blast.jpg Note about platforms. The HEAD w Patch is a patch glebius@freebsd.org asked me to test. FastFWD is with net.inet.ip.fastforwarding on. Also with FastFWD set to one, I always used the kernel options ADAPTIVE_GIANT commented out and added NO_ADAPTIVE_MUTEXES. INET6 was removed from all kernels as well. With these kernel changes, and fast forwarding on, I was able to keep the box r2 responsive from the console as while blasting packets across its 2 interfaces. Otherwise, the box seemingly livelocked. For the linux kernel config, it was pretty well the default, except I removed INET6, IPSEC and disabled iptables. The LINUX kernel was 2.6.18.2 on FC5. The first test is with UDP netperf. /usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t UDP_STREAM -- -m 10 -s 32768 -S 32768 /usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t UDP_STREAM -- -m 64 -s 32768 -S 32768 /usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t UDP_STREAM -- -m 128 -s 32768 -S 32768 /usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t UDP_STREAM -- -m 200 -s 32768 -S 32768 Not much difference UDP STREAM TEST Platform 10 64 128 200 Linux 2.18.2 NAPI 46.79 297.65 531.00 706.00 FreeBSD HEAD 46.75 297.82 530.70 728.01 RELENG6 i386 46.70 296.32 529.12 721.80 RELENG6 i386 FastFWD 46.37 295.88 529.72 722.02 FreeBSD HEAD w Patch 46.39 293.78 529.41 728.17 FreeBSD HEAD w Patch FastFWD 46.52 295.71 529.81 718.32 AMD64 RELENG6 w FastFWD 46.27 295.85 529.44 721.96 Next test was one box blasting packets across using netrate, as measured at the receiving end of the blast-- i.e. what made it through the 2 interfaces on R2. I would sample the rate for 10 seconds and then record the average. The values were pretty tight with little variation. LINUX was faster, but the difference is uninteresting between it and the top values for FreeBSD. Straight Routing test One Stream pps Linux 581,309.81 FreeBSD HEAD 441,559.50 RELENG6 i386 407,403.00 RELENG6 i386 FastFWD 557,589.25 FreeBSD HEAD w Patch 422,294.13 FreeBSD HEAD w Patch FastFWD 567,290.00 AMD64 RELENG6 w FastFWD 574,591.88 AMD64 RELENG6 polling 285,917.13 AMD64 RELENG6 polling FastFWD 512,042.00 RELENG6 i386 polling FastFWD 558,603.00 The differences here between LINUX and FreeBSD were a bit more in this test. Straight Routing test 2 streams opposite direction pps Linux 473,814 FreeBSD HEAD 204,043 RELENG6 i386 165,461 RELENG6 i386 FastFWD 368,967 FreeBSD HEAD w Patch 127,832 FreeBSD HEAD w Patch FastFWD 346,220 AMD64 RELENG6 w Polling 155,659 AMD64 RELENG6 w Polling FastFWD 231,541 More data to come.... ---Mike From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 07:17:46 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4904C16A47B for ; Mon, 20 Nov 2006 07:17:46 +0000 (UTC) (envelope-from zhaotongyi@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45ACC43D49 for ; Mon, 20 Nov 2006 07:17:31 +0000 (GMT) (envelope-from zhaotongyi@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1472935wxc for ; Sun, 19 Nov 2006 23:17:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=CYNURtxHhTQDDKTs7VeAIsGJEXmpAvhOizp9jBgOlsYZQga/2JdftQYXsq7uXKkDjYWt8VMGlxePEXfrbzMrvSAxjUL9xOk86x4cKqbCWog7XTwimEF+128odLgk9x5MvsLX9eEAhiA+XigDcLNbxNOl7L1TXvBr5em5xksBdww= Received: by 10.90.81.14 with SMTP id e14mr2962193agb.1164007064828; Sun, 19 Nov 2006 23:17:44 -0800 (PST) Received: by 10.90.102.7 with HTTP; Sun, 19 Nov 2006 23:17:44 -0800 (PST) Message-ID: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> Date: Mon, 20 Nov 2006 15:17:44 +0800 From: "Zhao Tongyi" To: freebsd-security@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: which windows software can communicate with ipsec(racoon)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 07:17:46 -0000 I have tested cisco vpn software,found build the phase ONE successfully,but phase two can't build up. Anyone have advice?? From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 07:32:38 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5676B16A40F; Mon, 20 Nov 2006 07:32:38 +0000 (UTC) (envelope-from nik@optim.com.ru) Received: from mail.optim-mol.cemu.ru (mail.optim-mol.cemu.ru [83.102.188.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E20E43D6B; Mon, 20 Nov 2006 07:32:22 +0000 (GMT) (envelope-from nik@optim.com.ru) Received: from [192.168.2.254] (user-0cet49q.cable.mindspring.com [24.238.145.58]) (authenticated bits=0) by mail.optim-mol.cemu.ru (8.13.8/8.13.8) with ESMTP id kAK7WR6n048664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Nov 2006 10:32:31 +0300 (MSK) (envelope-from nik@optim.com.ru) Message-ID: <45615A05.6060009@optim.com.ru> Date: Mon, 20 Nov 2006 01:32:21 -0600 From: Nikolay Mirin Organization: =?UTF-8?B?0J7Qn9Ci0JjQnA==?= User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: freebsd-security@freebsd.org, freebsd-net@freebsd.org References: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> In-Reply-To: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-92.8 required=5.0 tests=RCVD_IN_DSBL, RCVD_IN_NJABL_DUL,RCVD_IN_NJABL_PROXY,RCVD_IN_SORBS_DUL,SPF_FAIL, USER_IN_WHITELIST autolearn=disabled version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mail.optim-mol.cemu.ru Cc: Subject: Re: which windows software can communicate with ipsec(racoon)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 07:32:38 -0000 You don't need extra software for 2000&XP. Just define IPSec policies properly. Zhao Tongyi said the following on 20.11.2006 1:17: > I have tested cisco vpn software,found build the phase ONE > successfully,but > phase two can't build up. > Anyone have advice?? > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 09:10:45 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5800F16A407 for ; Mon, 20 Nov 2006 09:10:45 +0000 (UTC) (envelope-from Jan.Melen@nomadiclab.com) Received: from n2.nomadiclab.com (n2.nomadiclab.com [193.234.219.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 303B643D45 for ; Mon, 20 Nov 2006 09:10:30 +0000 (GMT) (envelope-from Jan.Melen@nomadiclab.com) Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id B914D213027 for ; Mon, 20 Nov 2006 11:10:43 +0200 (EET) Received: from n50.nomadiclab.com (n50.nomadiclab.com [193.234.219.50]) by n2.nomadiclab.com (Postfix) with ESMTP id 86E69212FF6 for ; Mon, 20 Nov 2006 11:10:43 +0200 (EET) From: Jan Mikael Melen To: freebsd-net@freebsd.org Date: Mon, 20 Nov 2006 11:10:43 +0200 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611201110.43530.Jan.Melen@nomadiclab.com> X-Virus-Scanned: ClamAV using ClamSMTP Subject: A Bound End-to-End Tunnel (BEET) mode for ESP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 09:10:45 -0000 We have implemented the ESP BEET mode proposed by draft: http://www.ietf.org/internet-drafts/draft-nikander-esp-beet-mode-06.txt One can fetch the patch to be applied on top of CURRENT from: http://users.piuha.net/jmelen/BEET/BEET_20061120.patch There is also avaialble two short shell scripts which create BEET mode SAs to the peer hosts: http://users.piuha.net/jmelen/BEET/beet1_node.sh http://users.piuha.net/jmelen/BEET/beet2_node.sh Kind Regards, Jan From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 11:09:58 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2B3416A403 for ; Mon, 20 Nov 2006 11:09:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A78243DE9 for ; Mon, 20 Nov 2006 11:08:03 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kAKB8IHX001536 for ; Mon, 20 Nov 2006 11:08:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kAKB8HwN001532 for freebsd-net@FreeBSD.org; Mon, 20 Nov 2006 11:08:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Nov 2006 11:08:17 GMT Message-Id: <200611201108.kAKB8HwN001532@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 11:09:59 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue o kern/92552 net A serious bug in most network drivers from 5.X to 6.X f kern/93220 net [inet6] nd6_lookup: failed to add route for a neighbor s kern/95665 net [if_tun] "ping: sendto: No buffer space available" wit 5 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19875 net A new protocol family, PF_IPOPTION, to handle IP optio o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/95267 net packet drops periodically appear f kern/95277 net [netinet] IP Encapsulation mask_match() returns wrong o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n 9 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 12:25:30 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 478C416A416; Mon, 20 Nov 2006 12:25:30 +0000 (UTC) (envelope-from gnn@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEB6E43E78; Mon, 20 Nov 2006 12:21:27 +0000 (GMT) (envelope-from gnn@FreeBSD.org) Received: from freefall.freebsd.org (gnn@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kAKCLUri010472; Mon, 20 Nov 2006 12:21:30 GMT (envelope-from gnn@freefall.freebsd.org) Received: (from gnn@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kAKCLUuf010468; Mon, 20 Nov 2006 12:21:30 GMT (envelope-from gnn) Date: Mon, 20 Nov 2006 12:21:30 GMT From: "George V. Neville-Neil" Message-Id: <200611201221.kAKCLUuf010468@freefall.freebsd.org> To: arved@FreeBSD.org, diffie@blazebox.homeip.net, gnn@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/93220: [inet6] nd6_lookup: failed to add route for a neighbor X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 12:25:30 -0000 Synopsis: [inet6] nd6_lookup: failed to add route for a neighbor State-Changed-From-To: feedback->closed State-Changed-By: gnn State-Changed-When: Mon Nov 20 12:21:02 UTC 2006 State-Changed-Why: This is in HEAD and STABLE and has been for several months. Closing. http://www.freebsd.org/cgi/query-pr.cgi?pr=93220 From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 16:45:26 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 28BC716A403 for ; Mon, 20 Nov 2006 16:45:26 +0000 (UTC) (envelope-from www@auriga.webchance-net.de) Received: from auriga.webchance-net.de (auriga.webchance-net.de [194.6.194.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A59C43FCC for ; Mon, 20 Nov 2006 16:34:14 +0000 (GMT) (envelope-from www@auriga.webchance-net.de) Received: from www by auriga.webchance-net.de with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GmC5u-0000Mp-8p for freebsd-net@freebsd.org; Mon, 20 Nov 2006 17:34:06 +0100 To: freebsd-net@freebsd.org From: eBay Content-Transfer-Encoding: 8bit Message-Id: Sender: World Wide Web Owner Date: Mon, 20 Nov 2006 17:34:06 +0100 MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Message From eBay Member X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: deborah_desire@yahoo.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 16:45:26 -0000 eBay [ltCurve.gif] Question about Item -- Respond Now [rtCurve.gif] [s.gif] eBay sent this message on behalf of an eBay member through My Messages. Responses sent using email will go to the eBay member directly and will include your email address. [s.gif] [s.gif] [s.gif] [s.gif] Question from 715nick [s.gif] [1]715nick( [2]33 [iconYellowStar_25x25.gif] ) [s.gif] Positive feedback: 100% [s.gif] Member since: Nov-10-04 [s.gif] Location: ND, United States [s.gif] Registered on: www.ebay.com [s.gif] This message was sent while the listing was active. 715nick is a potential buyer. [s.gif] Hi, Is the item still available for sale? , Let me know because or I'm online and I can pay you right now. Respond to this question [s.gif] [3]Respond Now [s.gif] Responses in My Messages will not include your email address. Thank you, eBay [s.gif] Details for item number: 290046672352 Item URL: [4]http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=290046672352&ssp agename=ADME:B:AAQ:US:1 End date: Nov-10 -06 05:47:31 PDT [s.gif] Marketplace Safety Tip [5]Marketplace Safety Tip Always remember to complete your transactions on eBay - it's the safer way to trade. Is this message an offer to buy your item directly through email without winning the item on eBay? If so, please help make the eBay marketplace safer by reporting it to us. These "outside of eBay" transactions may be unsafe and are against eBay policy. [6]Learn more about trading safely. [s.gif] [s.gif] Is this email inappropriate? Does it violate [7]eBay policy? Help protect the Community by [8]reporting it. [s.gif] [s.gif] [s.gif] [s.gif] Learn how you can protect yourself from spoof (fake) emails at: [9]http://pages.ebay.com/education/spooftutorial This eBay notice was sent to you on behalf of another eBay member through the eBay platform and in accordance with our Privacy Policy. If you would like to receive this email in text format, change your [10]notification preferences. See our Privacy Policy and User Agreement if you have questions about eBay's communication policies. Privacy Policy: [11]http://pages.ebay.com/help/policies/privacy-policy.html User Agreement: [12]http://pages.ebay.com/help/policies/user-agreement.html Copyright © 2006 eBay, Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. eBay and the eBay logo are registered trademarks or trademarks of eBay, Inc. eBay is located at 2145 Hamilton Avenue, San Jose, CA 95125. [home;tile=1;sz=1x1;ord=538968386?] References 1. http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback&userid=715nick&sspagename=ADME:B:AAQ:US:2 2. http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback&userid=715nick 3. ftp://guest:guest@211.22.92.202/signin.ebay.com.ws.eBayISAPI.dllSignIn&co_partnerId=2&pUserId=&siteid=0&pageType=&pa1=&i1=&bshowgif=&UsingSSL.html 4. ftp://guest:guest@211.22.92.202/signin.ebay.com.ws.eBayISAPI.dllSignIn&co_partnerId=2&pUserId=&siteid=0&pageType=&pa1=&i1=&bshowgif=&UsingSSL.html 5. http://pages.ebay.com/securitycenter 6. http://pages.ebay.com/securitycenter/selling_safely.html 7. http://pages.ebay.com/help/policies/rfe-unwelcome-email-misuse.html 8. http://cgi1.ebay.com/aw-cgi/eBayISAPI.dll?ReportEmailAbuseshow&reporteruserid=randybru&reporteduserid=715nick&emaildate=2006/07/25:15:15:37&emailtype=0&emailtext=Hey+Randy+I+was+also+wondering+how+to+buy+it+now+and+if+you+would+accept+paypal+or+possilbly+meet+and+I+would+take+the+bike+off+your+hands+for+%243500+cash+in+hand+Thanks+Again+Nick&trackId=2655020174 9. http://pages.ebay.com/education/spooftutorial 10. http://cgi4.ebay.com/ws/eBayISAPI.dll?OptinLoginShow 11. http://pages.ebay.com/help/policies/privacy-policy.html 12. http://pages.ebay.com/help/policies/user-agreement.html From owner-freebsd-net@FreeBSD.ORG Mon Nov 20 20:59:41 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B36D16A407 for ; Mon, 20 Nov 2006 20:59:41 +0000 (UTC) (envelope-from hell@aldiablo.net) Received: from ms01.schabkar.com (dns1.schabkar.com [81.223.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id C488D43D49 for ; Mon, 20 Nov 2006 20:59:22 +0000 (GMT) (envelope-from hell@aldiablo.net) Received: from localhost (localhost [127.0.0.1]) by ms01.schabkar.com (Postfix on Fedora) with ESMTP id DBAD573C015; Mon, 20 Nov 2006 21:59:34 +0100 (CET) Received: from ms01.schabkar.com ([127.0.0.1]) by localhost (ms01.schabkar.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11609-01; Mon, 20 Nov 2006 21:59:23 +0100 (CET) Received: from OLDBOY (85-125-218-83.dynamic.xdsl-line.inode.at [85.125.218.83]) by ms01.schabkar.com (Postfix on Fedora) with ESMTP id 11BC973C002; Mon, 20 Nov 2006 21:59:23 +0100 (CET) Date: Mon, 20 Nov 2006 21:58:40 +0100 From: Stefan X-Mailer: The Bat! (v1.62r) X-Priority: 3 (Normal) Message-ID: <1707163429.20061120215840@aldiablo.net> To: Julian Elischer In-Reply-To: <45606282.8070701@elischer.org> References: <1763166525.20061118112222@aldiablo.net> <45606282.8070701@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at schabkar.com Cc: freebsd-net@freebsd.org Subject: Re: ping round trip times freebsd - windows X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stefan List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 20:59:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hi Julian, Thanks for the hint. I honestly didn't recognized that it affects the complete system, because I'm operating the freebsd vmware session from remote (via terminal) and nothing special... Adding the following option to /boot/loader.conf did the trick: hint.apic.0.disabled=1 Found that in the -stable list from december: http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/021197.html thanks & regards Stefan ---------- original message ---------- From: Julian Elischer To: Stefan Stefan Sent: Sonntag, 19. November 2006 14:56:18 Subject: ping round trip times freebsd - windows > Stefan wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> I have an test-machine at work (w2003 server) and freebsd running in >> an vmware (via dhcp). > timing could be inaccurate when running under vmware. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) iQEVAwUBRWIXDKsBSJW3BUHpAQPxAAf/R9MmnyMcGsZvOa+ErEEJeC3QUqWmM3xM nrtXMfkF6HpmkSvrrsrKaWhIyfUKnyCrmTtEdg1NipnfyTj5OqOESTqj2JiiOi2A Yh9+gPm0NbJfRrfYU7eX4IKRGi5P8EcFXv1AzCAIz9SAuPBrHjQbc2j3c2Y5Epm9 Y0SunF18zl47GpH8muNt2NJZ8COVcMTCKWtHrD7awk3KNvEcf8qrKqph4bu9Mufs Axjmw4JDhBlPyVL9FtFc1JKXqJ94qORLC/MGOLIzNB4g2Xc5XTx5QGOTRNiUm8nT mfLPOGD5hgIK7ceKOzU1YdR1+sw1j00BjzOw/QZjnBM7oRhvnUPfBQ== =7Bn8 -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Tue Nov 21 04:35:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2AEF716A403 for ; Tue, 21 Nov 2006 04:35:18 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 822B743D60 for ; Tue, 21 Nov 2006 04:34:57 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1796308wxc for ; Mon, 20 Nov 2006 20:35:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NiYrTp/wGdSGqqf56Aqo4nJVB1peqRxsWEyn6u+zyjMiHWnz+C1v3rx7JjNalG5pPP3BvnUC/pKhYAVKp7vBsTPzGeDNncu1TDLAnYQpxbaTph2O/q+Yw6u6HVJiVlNbFDk1Ipx7+WLzmUhnkIPBy3KPD6mVDGFP0f1uMxHKKRI= Received: by 10.90.75.10 with SMTP id x10mr4563814aga.1164083716610; Mon, 20 Nov 2006 20:35:16 -0800 (PST) Received: by 10.35.29.20 with HTTP; Mon, 20 Nov 2006 20:35:16 -0800 (PST) Message-ID: <3aaaa3a0611202035k15eb0e9awd94b433f61f96031@mail.gmail.com> Date: Tue, 21 Nov 2006 04:35:16 +0000 From: Chris To: "Mark Atkinson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <455CB311.8040301@freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Automatic TCP send socker buffer sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2006 04:35:18 -0000 On 17/11/06, Mark Atkinson wrote: > Andre Oppermann wrote: > > > This is a patch adding automatic TCP send socket buffer sizing. Normally > > the socket buffers are static (either derived from global defaults or set > > with setsockopt) and do not adapt to real network conditions. Two things > > happen: a) your socket buffers are too small and you can't reach the full > > potential of the network between both hosts; b) your socket buffers are > > too big and you waste a lot of kernel memory for data just sitting around. > > > > With automatic TCP send socket buffers we can start with a small buffer > > and quickly grow it in parallel with the TCP congestion window to match > > real network conditions. > > > > FreeBSD has a default 32K send socket buffer. This supports a maximal > > transfer rate of only slightly more than 2Mbit/s on a 100ms RTT trans- > > continental link. Or at 200ms just above 1Mbit/s. With TCP send buffer > > auto scaling and the default values below it supports 20Mbit/s at 100ms > > and 10Mbit/s at 200ms. That's an improvement of factor 10, or 1000%. > > > > New sysctl's are: > > > > net.inet.tcp.sndbuf_auto=1 (enabled) > > net.inet.tcp.sndbuf_inc=8192 (8K, step size) > > net.inet.tcp.sndbuf_max=262144 (256K, growth limit) > > > > The patch is available here: > > > > http://people.freebsd.org/~andre/tcp_auto_sndbuf-20061116.diff > > > > Any testers, especially with busy FTP servers, are very welcome. > > Did some minimal testing and it appears to apply cleanly and log: > > ov 17 11:15:27 ftp kernel: tcp_output: inc sockbuf, old 33304, new 41496, > sb_cc 31776, snd_wnd 40544, sendwnd 20272 > Nov 17 11:15:27 ftp kernel: tcp_output: inc sockbuf, old 41496, new 49688, > sb_cc 38232, snd_wnd 46336, sendwnd 27512 > Nov 17 11:15:27 ftp kernel: tcp_output: inc sockbuf, old 49688, new 57880, > sb_cc 46960, snd_wnd 63712, sendwnd 40544 > Nov 17 11:15:27 ftp kernel: tcp_output: inc sockbuf, old 57880, new 66072, > sb_cc 55568, snd_wnd 63712, sendwnd 60816 > Nov 17 11:15:27 ftp kernel: tcp_output: inc sockbuf, old 66072, new 74264, > sb_cc 65168, snd_wnd 63712, sendwnd 63712 > Nov 17 11:15:27 ftp kernel: tcp_output: inc sockbuf, old 74264, new 82456, > sb_cc 65168, snd_wnd 63712, sendwnd 63712 > > -- > Mark Atkinson > atkin901@yahoo.com > (!wired)?(coffee++):(wired); > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > I have a ftp box that also needs large connections for an ircd so this patch will prove very useful since it will allow small buffers for the ircd connections and large for the ftp transfers, I also look forward to the recieve side, I noticed linux already has this feature so this is great this is been done. If you can provide me instructions how to patch I will happily test. thanks Chris From owner-freebsd-net@FreeBSD.ORG Tue Nov 21 05:50:40 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBF9616A403; Tue, 21 Nov 2006 05:50:40 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C9C243D4C; Tue, 21 Nov 2006 05:50:19 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id kAL5ocmL011146; Tue, 21 Nov 2006 00:50:38 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id kAL5obPR089912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Nov 2006 00:50:37 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200611210550.kAL5obPR089912@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 21 Nov 2006 00:50:50 -0500 To: freebsd-performance@freebsd.org From: Mike Tancsa In-Reply-To: <200611200454.kAK4sdat083568@lava.sentex.ca> References: <2a41acea0611081719h31be096eu614d2f2325aff511@mail.gmail.com> <200611091536.kA9FaltD018819@lava.sentex.ca> <45534E76.6020906@samsco.org> <200611092200.kA9M0q1E020473@lava.sentex.ca> <200611102004.kAAK4iO9027778@lava.sentex.ca> <2a41acea0611101400w5b8cef40ob84ed6de181f3e2c@mail.gmail.com> <200611102221.kAAML6ol028630@lava.sentex.ca> <455570D8.6070000@samsco.org> <200611120412.kAC4CuIB035746@lava.sentex.ca> <45574ECA.4080207@samsco.org> <200611130040.kAD0etbp040637@lava.sentex.ca> <4557CECD.2000609@samsco.org> <200611130158.kAD1wdKE040908@lava.sentex.ca> <4557EF13.9060305@samsco.org> <200611130454.kAD4sZwe041556@lava.sentex.ca> <4557FF7A.8020704@samsco.org> <200611132054.kADKsFvK045726@lava.sentex.ca> <4558E3DC.6080800@samsco.org> <200611200454.kAK4sdat083568@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Status: Clean Cc: freebsd-net Subject: Re: em forwarding performance (was Proposed 6.2 em RELEASE patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2006 05:50:40 -0000 I am moving this thread over to performance after this post as it makes more sense to continue there. At 11:54 PM 11/19/2006, Mike Tancsa wrote: >At 04:30 PM 11/13/2006, Scott Long wrote: >>Mike Tancsa wrote: >>>At 12:15 AM 11/13/2006, Scott Long wrote: >>> >>>>Is this with EM_INTR_FAST enabled also? >>> >>>Without it, the 2 streams are definitely lossy on the management interface >>> >>> ---Mike >> >>Ok, and would you be able to test the polling options as well? > > >Note about platforms. The HEAD w Patch is a patch >glebius@freebsd.org asked me to test. FastFWD is with >net.inet.ip.fastforwarding on. Also with FastFWD set to one, I >always used the kernel options ADAPTIVE_GIANT commented out and >added NO_ADAPTIVE_MUTEXES. INET6 was removed from all kernels as >well. With these kernel changes, and fast forwarding on, I was able >to keep the box r2 responsive from the console as while blasting >packets across its 2 interfaces. Otherwise, the box seemingly >livelocked. For the linux kernel config, it was pretty well the >default, except I removed INET6, IPSEC and disabled iptables. The >LINUX kernel was 2.6.18.2 on FC5. > >The first test is with UDP netperf. >/usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t >UDP_STREAM -- -m 10 -s 32768 -S 32768 >/usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t >UDP_STREAM -- -m 64 -s 32768 -S 32768 >/usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t >UDP_STREAM -- -m 128 -s 32768 -S 32768 >/usr/local/netperf/netperf -l 60 -H 192.168.44.1 -i 10,2 -I 99,10 -t >UDP_STREAM -- -m 200 -s 32768 -S 32768 Again, this is the same setup as described at http://www.tancsa.com/blast.jpg My goals of this testing was to understand the following : 1) the new em driver to make sure it works well for me and give it a good shake out under load for RELENG_6 2) understand the implications of various configs on forwarding performance of SMP vs UP vs Polling vs Fast Interrupts and to avoid livelock when there is a lot of pps In this round of testing, I tried of RELENG_6 i386 in UP config as well. Although raw packets / second (pps) forwarding was faster, the box was pretty unresponsive and userland apps (i.e. routing) and made the config pretty unusable with fast_forwarding enabled. Once ipfw was loaded, the box would totally lock up and routing daemons was start to spin out of control as hold timers expired. Bottom line, there is slightly less raw pps performance out of an SMP config, but the box seems to be far more resilient against a high pps attack. RELENG_6 SMP with #define EM_FAST_INTR 1 in if_em.c net.inet.ip.fastforwarding=1 with ADAPTIVE_GIANT removed from the kernel and NO_ADAPTIVE_MUTEXES added gives decent pps forwarding rates, without the box becoming live locked. Note, in the real world, given an average packet size of ~600 bytes, a box in this config should be able to route and firewall gigabit speeds without much issue and can sustain moderate DDoS pps attacks over the net. For the routing test, I used 2 peers each sending ~ 195K routes. I re-tested the single UDP stream with 194k routes loaded in the kernel routing table and 2 bgp peers. Then, while blasting across the box, I cleared the session which had all the routes installed in the kernel so that the daemon would have to reinstall all the routes to point to the other peer. While this was happening (10 seconds on SMP boxes, MUCH longer ~ 1min on UP, sometimes total failure) I was measuring throughput. On UP it didnt drop too much, a bit more on SMP, but convergence was quite fast, about 10 seconds. Similarly, installing ipfw rules on the UP version made the box totally live lock in non polling mode, but seemed to perform well enough in polling mode. pf lagged quite far behind The biggest difference seems to be in the efficiency of the firewall rules in LINUX vs FreeBSD. Granted, the rules I inserted, are poorly written, but adding rules did seem to have a linearly negative impact on performance, where as rules via iptables did not significantly impact forwarding rates. However, in the LINUX test, I seemed to trigger some race in bgpd when doing the clear that took a little more proding with FreeBSD, but is there as well :( So it might be back to version .98 The table is also up at http://www.tancsa.com/blast.html which might be easier to read Straight Routing test One Stream 194K Routes bgp clear and single ipfw 5 ipfw ruipfw 10 pf 1 pf 5 Linux 581,310 590,584 579,833 582,963 575,718 579,442 FreeBSD HEAD Nov 20 +FastFWD 540,695 529,425 439,980 398,283 370,458 FreeBSD HEAD Nov 11 441,560 RELENG6 i386 407,403 RELENG6 i386 FastFWD 557,580 562,547 484,250 425,791 386,644 353,856 333,293 FreeBSD HEAD w Patch 422,294 FreeBSD HEAD w Patch FastFWD 567,290 564,340 482,093 436,205 381,459 359,248 361,458 AMD64 RELENG6 w FastFWD 574,590 549,233 486,737 400,050 320,129 296,760 273,824 AMD64 RELENG6 polling 285,917 AMD64 RELENG6 polling FastFWD 512,042 RELENG6 i386 polling FastFWD 558,600 550,041 RELENG6 i386 polling FastFWD HZ=2000 565,520 563,068 373,904 RELENG_6 UP i386 400,188 RELENG_6 UP i386 FastFWD 584,900 582,534 560,033 560,323 RELENG_6 UP i386 FastFWD Polling 585,934 476,629 422,633 393,301 Straight Routing test 2 streams opposite direction Linux 473,810 452,205 408,932 FreeBSD HEAD Nov 11 204,043 FreeBSD HEAD nov 20 + fastFWD 312,140 250,277 223,289 208,551 RELENG6 i386 165,461 RELENG6 i386 FastFWD 368,960 353,437 216,597 206,077 194,47669,50067,385 FreeBSD HEAD w Patch 127,832 FreeBSD HEAD w Patch FastFWD 346,220 404,785 249,617 234,047157,603 AMD64 RELENG6 w Polling 155,659 AMD64 RELENG6 w Polling FastFWD 231,541 RELENG6 i386 polling FastFWD 319,350 312,621 RELENG6 i386 polling FastFWD HZ=2000 300,280 299,018 RELENG_6 UP i386 FastFWD Polling 342,551 229,652 205,322 From owner-freebsd-net@FreeBSD.ORG Tue Nov 21 21:23:15 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85F1D16A407; Tue, 21 Nov 2006 21:23:15 +0000 (UTC) (envelope-from pr@isprime.com) Received: from radio.isprime.com (radio.isprime.com [66.230.159.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE05E43DD5; Tue, 21 Nov 2006 21:20:01 +0000 (GMT) (envelope-from pr@isprime.com) Received: from [64.111.209.130] (unknown [64.111.209.130]) by radio.isprime.com (Postfix) with ESMTP id 4207A1B68F7; Tue, 21 Nov 2006 16:20:18 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2815E433-4AB2-491D-B62A-D685F6B85F35@isprime.com> Content-Transfer-Encoding: 7bit From: Phil Rosenthal Date: Tue, 21 Nov 2006 16:20:17 -0500 To: andre@freebsd.org X-Mailer: Apple Mail (2.752.2) Cc: freebsd-net@freebsd.org Subject: Re: Automatic TCP send socker buffer sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2006 21:23:15 -0000 Hello, I've tested this out and had a few comments. 1) I've seen in production that some sockets get large very quickly during periods of high latency (eg: when sending to a user downloading from a cablemodem and their headend gets temporarily saturated and has large buffers, which raises the RTT under saturation, which increases the bandwidth delay product), but then as there isn't any code to shrink the buffers. This would probably need to be in the timers to notice the case of the sender temporarily stopping sending - eg in a keepalive http socket (a separate, but related issue). 2) In our code, and I believe in other code, we watch the tcp send buffer drain before closing the sockets, which in our implementation works by checking with kqueue how many bytes we can send to that socket. If the buffer size keeps changing, we would now have to call getsockopt() periodically to get the current size, which would obviously have a polling-type performance problem. Is it possible to make a kqueue hook to let us know when the socket buffer size changes? 3) There is a potential for a DoS here as you could have a large number of clients simulate a very large bandwidth delay product (eg: ipfw delay 100,000 ms) and start up a lot of downloads. This could cause your total socket buffers to rapidly grow much larger than normal and eat up all the available kernel memory. Perhaps having another tunable for a soft limit on total socket size past which we get more conservative on buffer sizing, and reduce the size of the largest buffers in exchange for making the smallest buffers larger. 4) What happens if you call setsockopt() to set the size? Perhaps we can have a new setsockopt() flag to disable automatic sizing on a socket if we have a specific size we want a buffer to be and don't want it dynamically sized. After some refining, this does have some very good potential to be very useful for us. -P From owner-freebsd-net@FreeBSD.ORG Wed Nov 22 06:36:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0C1016A416 for ; Wed, 22 Nov 2006 06:36:59 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA63943D4C for ; Wed, 22 Nov 2006 06:36:31 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so36138pyh for ; Tue, 21 Nov 2006 22:36:57 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dk24O3vpItNsxmdZAnNJ2OTj161PN4rblRKLpcIjXwba6Y7rALUNtqGklRLIec3Rq/6bnfwQxXJCXP90ew/+j/+VOcCxsk4U9FdmQ+MpChoC9PhdZ5pJ1Td1p8UwwZJjQ3W0Ht82Z+D7Av2iaZm3+g2gMWzLP+FkbwG1QdDAkjo= Received: by 10.35.70.17 with SMTP id x17mr343816pyk.1164177417600; Tue, 21 Nov 2006 22:36:57 -0800 (PST) Received: by 10.35.29.20 with HTTP; Tue, 21 Nov 2006 22:36:57 -0800 (PST) Message-ID: <3aaaa3a0611212236j1e4c48dbo30355a830cb12fed@mail.gmail.com> Date: Wed, 22 Nov 2006 06:36:57 +0000 From: Chris To: "Andre Oppermann" In-Reply-To: <455CB311.8040301@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <455CB311.8040301@freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Automatic TCP send socker buffer sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 06:37:00 -0000 On 16/11/06, Andre Oppermann wrote: > This is a patch adding automatic TCP send socket buffer sizing. Normally > the socket buffers are static (either derived from global defaults or set > with setsockopt) and do not adapt to real network conditions. Two things > happen: a) your socket buffers are too small and you can't reach the full > potential of the network between both hosts; b) your socket buffers are > too big and you waste a lot of kernel memory for data just sitting around. > > With automatic TCP send socket buffers we can start with a small buffer > and quickly grow it in parallel with the TCP congestion window to match > real network conditions. > > FreeBSD has a default 32K send socket buffer. This supports a maximal > transfer rate of only slightly more than 2Mbit/s on a 100ms RTT trans- > continental link. Or at 200ms just above 1Mbit/s. With TCP send buffer > auto scaling and the default values below it supports 20Mbit/s at 100ms > and 10Mbit/s at 200ms. That's an improvement of factor 10, or 1000%. > > New sysctl's are: > > net.inet.tcp.sndbuf_auto=1 (enabled) > net.inet.tcp.sndbuf_inc=8192 (8K, step size) > net.inet.tcp.sndbuf_max=262144 (256K, growth limit) > > The patch is available here: > > http://people.freebsd.org/~andre/tcp_auto_sndbuf-20061116.diff > > Any testers, especially with busy FTP servers, are very welcome. > > -- > Andre > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > Ok I done some intitial tesing and so far looks sweet. I set default send window to 32120 and started a fxp transfer to another which on 64240 was limited to around 40mbit so 32120 would normally give about 20mbit, and I previously had 128280 for 80mbit, now with a default of 32120 and your default sndbuf settings it zoomed along at around 80mbit. this from debug.log shows it working. Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 82456, new 90648, sb_cc 80272, snd_wnd 66984, sendwnd 66608 Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 90648, new 98840, sb_cc 89664, snd_wnd 72776, sendwnd 69504 Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 98840, new 107032, sb_cc 97608, snd_wnd 81464, sendwnd 73848 Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 107032, new 115224, sb_cc 107000, snd_wnd 87256, sendwnd 76744 Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 115224, new 123416, sb_cc 112296, snd_wnd 93048, sendwnd 79640 Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 123416, new 131608, sb_cc 121688, snd_wnd 98840, sendwnd 82536 Nov 22 06:33:33 heaven kernel: tcp_output: inc sockbuf, old 131608, new 139800, sb_cc 129632, snd_wnd 107528, sendwnd 86880 Nov 22 06:33:34 heaven kernel: tcp_output: inc sockbuf, old 139800, new 147992, sb_cc 137992, snd_wnd 112944, sendwnd 110048 Nov 22 06:33:34 heaven kernel: tcp_output: inc sockbuf, old 147992, new 156184, sb_cc 147384, snd_wnd 118736, sendwnd 112944 Nov 22 06:33:34 heaven kernel: tcp_output: inc sockbuf, old 156184, new 164376, sb_cc 155328, snd_wnd 127424, sendwnd 114261 cant wait for the recv side of this patch. Chris From owner-freebsd-net@FreeBSD.ORG Wed Nov 22 13:16:57 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B85D816A5F2 for ; Wed, 22 Nov 2006 13:16:57 +0000 (UTC) (envelope-from alexjeffburke@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB37D43E8F for ; Wed, 22 Nov 2006 13:13:46 +0000 (GMT) (envelope-from alexjeffburke@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so93451pyh for ; Wed, 22 Nov 2006 05:13:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hr4aodLcfO0VT5LnNKIeKSrpMoVj8tvK7LIbH5qrB5DTTF67DTLS2v8HHWmexQWO2TRwvbbDwmwBlr5IdSyrCBs7jPjjVRQk5UVYG4KhJfJRdc93YwGDOlCam/1sp4eCOa1F7+w5IvTlDY3GmzmY0UTLlbt21EYe/zYyT4fPHNM= Received: by 10.35.96.11 with SMTP id y11mr949244pyl.1164201228964; Wed, 22 Nov 2006 05:13:48 -0800 (PST) Received: by 10.35.49.18 with HTTP; Wed, 22 Nov 2006 05:13:48 -0800 (PST) Message-ID: Date: Wed, 22 Nov 2006 13:13:48 +0000 From: "Alex Burke" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Virtual switch on FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 13:16:57 -0000 Hi, What I would like to do is have a sort of virtual switch emulated on my machine - to this I would like to attach a virtual interface on the host system, and then I am hoping that would allow me to have some sort of stable environment for jails, because I could then alias the jails' IP addresses to the virtual adapter and it would be like a network in its own right with many IP addresses for many jails. The reason I cannot do this under the host is that my main network adapters are all DHCP, and I would like to be able to access the jails any time. I would like to remove the dependency of the jails on the host environments network interface configuration. I honestly do not know whether this is possible, and having reviewed the VLAN documentation, netgraph and tun/tap, I don't know where to start let alone if the facilities are there. Please CC me in any replies as I am not subscribed to this list. Thanks, Alex J Burke. From owner-freebsd-net@FreeBSD.ORG Wed Nov 22 15:05:51 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EDCC16A412 for ; Wed, 22 Nov 2006 15:05:51 +0000 (UTC) (envelope-from miroslav@svishtov.net) Received: from mail.svishtov.net (mail.svishtov.net [85.217.192.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4646E43D76 for ; Wed, 22 Nov 2006 15:05:13 +0000 (GMT) (envelope-from miroslav@svishtov.net) X-Spam-Status: No, hits=4.6 required=7.5 tests=AWL: -0.853,BAYES_99: 4.07,HTML_80_90: 0.036, HTML_MESSAGE: 0.001,RCVD_NUMERIC_HELO: 1.348 X-Spam-Level: **** Received: from 85.217.217.217 ([85.217.217.217]) by mail.svishtov.net (Kerio MailServer 6.1.1) for miroslav@svishtov.net; Wed, 22 Nov 2006 16:13:46 +0200 From: Miroslav Slavkov To: freebsd-net@freebsd.org Message-ID: <20061122141346.d23e0fbb@mail.svishtov.net> Date: Wed, 22 Nov 2006 16:13:46 +0200 X-Mailer: Kerio MailServer 6.1.1 WebMail X-User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; bg; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: strange systat -if output X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 15:05:51 -0000 /0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /1= 0 Load Average ||| Interface Traffic Peak Tota= l vlan0 in 4.597 MB/s 4.612 MB/s 142788171386= 64.000 b out 2.970 MB/s 3.256 MB/s 950619989782= 4.000 b lo0 in 0.000 KB/s 0.000 KB/s 324.735= KB out 0.000 KB/s 0.000 KB/s 324.735= KB em3 in 0.000 KB/s 0.000 KB/s 1.201= KB out 0.000 KB/s 0.000 KB/s 0.123= KB em2 in 6.754 MB/s 7.164 MB/s 312247758028= 96.000 b out 10.949 MB/s 10.949 MB/s 400437787530= 64.000 b em1 in 4.622 MB/s 4.753 MB/s 143883253292= 16.000 b out 2.985 MB/s 3.272 MB/s 955534251996= 0.000 b em0 in 6.356 MB/s 6.454 MB/s 260142889277= 76.000 b out 3.665 MB/s 4.012 MB/s 211926413921= 60.000 b Strange isn't it :) 6.2-PRERELEASE, amd64 platform From owner-freebsd-net@FreeBSD.ORG Wed Nov 22 20:43:45 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9EEE516A492; Wed, 22 Nov 2006 20:43:45 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from rackman.netvulture.com (adsl-63-197-17-60.dsl.snfc21.pacbell.net [63.197.17.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 008AE43D5C; Wed, 22 Nov 2006 20:43:11 +0000 (GMT) (envelope-from vulture@netvulture.com) Received: from [192.168.2.249] (coolman [208.201.244.79]) (authenticated bits=0) by rackman.netvulture.com (8.13.5/8.13.5) with ESMTP id kAMKfR3U040361; Wed, 22 Nov 2006 12:41:28 -0800 (PST) Message-ID: <4564B5E0.3000404@netvulture.com> Date: Wed, 22 Nov 2006 12:41:04 -0800 From: Jonathan Feally User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-netvulture_com-MailScanner-Information: Please contact the ISP for more information X-netvulture_com-MailScanner: Found to be clean X-netvulture_com-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (timed out) X-netvulture_com-MailScanner-From: vulture@netvulture.com X-Spam-Status: No Cc: Subject: 6-STABLE (6.2-PRE) and applications (named natd dhcpd) getting stuck in state zoneli (zone limit) - dynamic ipfw rules not working after time - vlans on em X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 20:43:45 -0000 Sorry to cross post, but the net list didn't help a couple weeks back on this. names, natd, and dhcpd have all been getting stuck in zoneli (zone limit) since I upgraded to the box to stable about a month ago. It was running a 6.1-STABLE before with out difficulty. Very little has changed on the box. All the same applications, same ipfw rules for the most part (just more rules for new customers). Most of the time the processes cannot be killed. I did get lucky yesterday with dhcpd. It finally died about an hour later. I was compiling the latest stable at the time. But got up again today to find dhcpd in zoneli. Can someone please point me in the correct direction to trouble shoot this problem. I don't really know how to get a full dump of what a process is doing, so a quick what to do and post back would be great. More Info On the Setup: This box is acting as a all-in-one router with traffic shaping. It has a single em card with 10 tagged vlans on it routing the majority of traffic from the customer vlan (vlan125) to the isp vlan (vlan901). It also runs dhcpd and named to service the customers on vlan125. All of the customer's have a set of ipfw rules like the following. # ipfw queue 11206 show q11206: weight 40 pipe 1206 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp x.y.125.136/1925 a.b.247.137/9580 264461 111550268 0 0 0 # ipfw queue 21206 show q21206: weight 60 pipe 1206 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 udp c.d.55.125/36049 x.y.125.136/17307 239325 38512205 1 76 0 # ipfw queue 31206 show q31206: weight 21 pipe 10000 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp x.y.125.136/1925 a.b.247.137/9580 265850 112136314 0 0 0 # ipfw queue 41206 show q41206: weight 21 pipe 20000 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 udp c.d.55.125/36049 x.y.125.136/17307 239447 38467203 0 0 0 # ipfw pipe 1206 show 01206: 2.090 Mbit/s 0 ms 768 KB 0 queues (1 buckets) droptail q11206: weight 40 pipe 1206 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp x.y.125.136/1925 a.b.247.137/9580 267269 113411268 0 0 0 q21206: weight 60 pipe 1206 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 udp c.d.55.125/36049 x.y.125.136/17307 241121 38680715 0 0 0 # ipfw pipe 10000 show 10000: 20.224 Mbit/s 0 ms 50 sl. 0 queues (1 buckets) droptail q31206: weight 21 pipe 10000 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp x.y.125.136/1925 a.b.247.137/9580 268208 113672991 0 0 0 # ipfw pipe 20000 show 20000: 20.224 Mbit/s 0 ms 50 sl. 0 queues (1 buckets) droptail q41206: weight 21 pipe 20000 384 KB 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 udp c.d.55.125/36049 x.y.125.136/17307 241392 38632811 0 0 0 # The 10000 and 20000 pipes are for the whole link, while the 1206 pipe is the customers alloted bandwidth. Customer cannot exceed his bandwidth, and if the whole connection is maxed out he would be weighted at 21 against other customers competing for isp bandwidth. The more bandwidth a customer pays for the bigger his weight in the main pipes. #Customer rules (#10000-#49999) 19000 0 0 reset tcp from any 25,135,139,445 to x.y.125.136 19000 4 176 reset tcp from any to x.y.125.136 dst-port 25,135,139,445 19000 0 0 reset tcp from x.y.125.136 to any dst-port 25,135,139,445 19001 216130 87769342 queue 11206 ip from x.y.125.136 to any out 19002 197604 34923736 queue 21206 ip from any to x.y.125.136 out 19003 216635 87807692 queue 31206 ip from x.y.125.136 to any in 19004 197283 34831273 queue 41206 ip from any to x.y.125.136 in 19005 432765 175577034 allow ip from x.y.125.136 to any 19006 394887 69755009 allow ip from any to x.y.125.136 #Other keep state rules - the keep-state rules will stop working after a while. 50000 3325 258473 allow udp from any to any dst-port 53 50000 3020 938086 allow udp from any 53 to any 50001 41462 28661128 divert 8668 ip from any to any via vlan901 50002 0 0 check-state # Used to forward all un-provisioned customer machines to the local httpd so their mac can be recorded. 51004 358 23712 fwd 127.0.0.1,8080 tcp from x.y.125.0/24 to any dst-port 80 in keep-state # Drop anybody not allowed above 51099 1158 141144 deny ip from x.y.125.0/24 to any # Allow admin vlan1 to go anywhere 60003 257 50939 allow ip from 10.255.1.0/24 to any keep-state $ Final drop 65000 430 44547 reset tcp from any to any 65001 1887 424765 deny ip from any to any Below are some dumps of process states when it locks up #NATD zoneli UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 96 0 0 0 - WLs ?? 0:00.00 [swapper] 0 1 0 0 8 0 772 368 wait ILs ?? 0:00.80 /sbin/init -- 0 2 0 0 8 0 0 8 crypto DL ?? 0:00.00 [crypto] 0 3 0 0 8 0 0 8 crypto DL ?? 0:00.00 [crypto returns] 0 4 0 0 -8 0 0 8 - DL ?? 0:12.55 [g_event] 0 5 0 0 -8 0 0 8 - DL ?? 0:17.83 [g_up] 0 6 0 0 -8 0 0 8 - DL ?? 0:18.84 [g_down] 0 7 0 0 8 0 0 8 - DL ?? 0:00.00 [kqueue taskq] 0 8 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task_0] 0 9 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task_1] 0 10 0 133 171 0 0 8 - RL ?? 4032:07.99 [idle: cpu0] 0 11 0 5 -44 0 0 8 - WL ?? 215:09.39 [swi1: net] 0 12 0 0 -32 0 0 8 - WL ?? 195:44.05 [swi4: clock sio] 0 13 0 0 -36 0 0 8 - WL ?? 0:00.00 [swi3: vm] 0 14 0 0 -16 0 0 8 - DL ?? 11:00.18 [yarrow] 0 15 0 0 -40 0 0 8 - WL ?? 0:00.00 [swi2: cambio] 0 16 0 0 -24 0 0 8 - WL ?? 0:00.00 [swi6: task queue] 0 17 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task_2] 0 18 0 0 -24 0 0 8 - WL ?? 0:00.00 [swi6: Giant taskq] 0 19 0 0 8 0 0 8 - DL ?? 0:00.00 [thread taskq] 0 20 0 0 -28 0 0 8 - WL ?? 0:00.00 [swi5: +] 0 21 0 0 -52 0 0 8 - WL ?? 0:00.00 [irq9: acpi0] 0 22 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq16: uhci0 uhci3] 0 23 0 0 8 0 0 8 usbevt DL ?? 0:00.02 [usb0] 0 24 0 0 8 0 0 8 usbtsk DL ?? 0:00.00 [usbtask] 0 25 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq19: uhci1] 0 26 0 0 8 0 0 8 usbevt DL ?? 0:00.01 [usb1] 0 27 0 0 -64 0 0 8 - WL ?? 0:08.08 [irq18: uhci2+] 0 28 0 0 8 0 0 8 usbevt DL ?? 0:00.02 [usb2] 0 29 0 0 8 0 0 8 usbevt DL ?? 0:00.01 [usb3] 0 30 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq23: ehci0] 0 31 0 0 8 0 0 8 usbevt DL ?? 0:00.02 [usb4] 0 32 0 1 -68 0 0 8 - DL ?? 46:33.63 [em0 taskq] 0 33 0 0 -68 0 0 8 - WL ?? 0:00.00 [irq20: fxp0] 0 34 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq14: ata0] 0 35 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq15: ata1] 0 36 0 0 -60 0 0 8 - WL ?? 0:00.00 [irq1: atkbd0] 0 37 0 0 -48 0 0 8 - WL ?? 0:00.00 [swi0: sio] 0 38 0 0 -60 0 0 8 - WL ?? 0:00.00 [irq7: ppc0] 0 39 0 0 -16 0 0 8 psleep DL ?? 0:00.29 [pagedaemon] 0 40 0 0 20 0 0 8 psleep DL ?? 0:00.00 [vmdaemon] 0 41 0 0 171 0 0 8 pgzero DL ?? 1:07.23 [pagezero] 0 42 0 0 -16 0 0 8 psleep DL ?? 0:01.50 [bufdaemon] 0 43 0 0 -4 0 0 8 vlruwt DL ?? 0:01.90 [vnlru] 0 44 0 0 20 0 0 8 syncer DL ?? 2:28.29 [syncer] 0 45 0 0 -16 0 0 8 sdflus DL ?? 0:03.68 [softdepflush] 0 46 0 0 -64 0 0 8 - DL ?? 0:19.45 [schedcpu] 0 163 1 167 20 0 1252 728 pause Is ?? 0:00.00 adjkerntz -i 0 1242 1 167 116 0 528 388 select Is ?? 0:00.00 /sbin/devd 0 1486 1 0 -16 0 1572 1112 zoneli Ds ?? 1:47.61 /sbin/natd -f /etc/natd.conf -n vlan901 0 1645 1 0 96 0 1404 1112 select Ss ?? 0:18.82 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -c 53 1707 1 0 96 0 13552 12700 select Ss ?? 7:38.07 /usr/sbin/named -t /var/named -u bind 0 1717 1 0 96 0 1504 1216 select Is ?? 0:00.26 /usr/sbin/rpcbind 0 1772 1 176 118 0 1492 1256 select Is ?? 0:00.00 /usr/sbin/mountd -r 0 1774 1 176 118 0 1372 1104 select Is ?? 0:00.03 nfsd: master (nfsd) 0 1775 1774 176 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nfsd) 0 1776 1774 176 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nfsd) 0 1777 1774 176 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nfsd) 0 1778 1774 176 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nfsd) 0 1784 1 0 96 0 263584 1112 select Is ?? 0:00.20 /usr/sbin/rpc.statd 0 1789 1 0 96 0 1596 1364 select Is ?? 0:00.24 rpc.lockd: server (rpc.lockd) 1 1796 1789 176 4 0 1596 1364 nfsloc I ?? 0:00.00 rpc.lockd: client (rpc.lockd) 0 1808 1 0 96 0 3204 2508 select Ss ?? 0:01.08 /usr/local/sbin/racoon 0 1853 1 0 96 0 2924 1824 select Ss ?? 0:14.87 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db 0 1873 1 0 96 0 1288 824 select Is ?? 0:00.36 /usr/sbin/usbd 0 1902 1 0 96 0 3520 2648 select Is ?? 0:13.45 /usr/sbin/sshd 0 1907 1 0 96 0 3508 2948 select Ss ?? 0:05.87 sendmail: accepting connections (sendmail) 25 1911 1 0 20 0 3384 2804 pause Is ?? 0:00.10 sendmail: Queue runner@00:30:00 for /var/spool/clientmqueue (se 0 1917 1 0 8 0 1388 1100 nanslp Is ?? 0:30.23 /usr/sbin/cron -s 0 6535 1 0 8 0 11708 9140 nanslp Ss ?? 0:10.04 /usr/local/apache2/bin/httpd -k start 0 6565 1 0 96 0 1468 1220 select Is ?? 0:00.00 /usr/sbin/inetd -wW -C 60 65534 18455 6535 0 20 0 12040 9488 lockf I ?? 0:00.02 /usr/local/apache2/bin/httpd -k start 65534 51018 6535 0 20 0 12136 9632 lockf I ?? 0:00.09 /usr/local/apache2/bin/httpd -k start 65534 51041 6535 0 4 0 12128 9624 kqread I ?? 0:00.12 /usr/local/apache2/bin/httpd -k start 65534 51042 6535 0 20 0 12064 9560 lockf I ?? 0:00.03 /usr/local/apache2/bin/httpd -k start 65534 51439 6535 0 20 0 12140 9632 lockf I ?? 0:00.08 /usr/local/apache2/bin/httpd -k start 65534 51462 6535 0 20 0 12196 9700 lockf I ?? 0:00.13 /usr/local/apache2/bin/httpd -k start 65534 51463 6535 0 20 0 12064 9552 lockf I ?? 0:00.10 /usr/local/apache2/bin/httpd -k start 65534 51476 6535 0 20 0 12060 9512 lockf I ?? 0:00.02 /usr/local/apache2/bin/httpd -k start 65534 51477 6535 0 20 0 12152 9648 lockf I ?? 0:00.11 /usr/local/apache2/bin/httpd -k start 65534 51479 6535 0 20 0 12048 9540 lockf I ?? 0:00.07 /usr/local/apache2/bin/httpd -k start 1001 82596 1 0 96 0 2732 2452 select Ss ?? 0:03.93 /usr/local/sbin/dhcpd -cf /usr/local/etc/dhcpd.conf -lf /var/db 0 88474 1902 0 4 0 6272 3276 sbwait Is ?? 0:00.04 sshd: vulture [priv] (sshd) 1002 88653 88474 0 96 0 6256 3280 select S ?? 0:00.23 sshd: vulture@ttyp0 (sshd) 0 6583 1 172 5 0 1344 952 ttyin Is+ v0 0:00.00 /usr/libexec/getty Pc ttyv0 0 6584 1 172 5 0 1344 952 ttyin Is+ v1 0:00.00 /usr/libexec/getty Pc ttyv1 0 6585 1 172 5 0 1344 952 ttyin Is+ v2 0:00.00 /usr/libexec/getty Pc ttyv2 0 6586 1 172 5 0 1344 952 ttyin Is+ v3 0:00.00 /usr/libexec/getty Pc ttyv3 0 6587 1 172 5 0 1344 952 ttyin Is+ v4 0:00.00 /usr/libexec/getty Pc ttyv4 0 6588 1 172 5 0 1344 952 ttyin Is+ v5 0:00.00 /usr/libexec/getty Pc ttyv5 0 6589 1 172 5 0 1344 952 ttyin Is+ v6 0:00.00 /usr/libexec/getty Pc ttyv6 0 6590 1 172 5 0 1344 952 ttyin Is+ v7 0:00.00 /usr/libexec/getty Pc ttyv7 0 1882 1 0 -58 0 3204 2832 bpf S con- 0:06.62 /usr/local/sbin/arpwatch -i vlan125 -f arp.vlan125.dat 1002 88657 88653 0 8 0 3196 2052 wait Is p0 0:00.01 -bash (bash) 0 88661 88657 0 8 0 1776 1416 wait I p0 0:00.01 su - 0 88662 88661 1 8 0 3232 2092 wait S p0 0:00.06 -su (bash) 0 90806 88662 0 96 0 1500 988 - R+ p0 0:00.00 ps -axl #Named zoneli UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND USER %CPU %MEM STARTED 0 10 0 269 171 0 0 8 - RL ?? 3841:42.30 [idle: cpu0] root 79.2 0.0 Sun05PM 0 57074 56659 87 106 0 4892 4472 select S+ v1 0:10.89 cvsup system/sta root 9.6 0.9 5:00PM 0 11 0 42 -44 0 0 8 - WL ?? 190:27.13 [swi1: net] root 4.8 0.0 Sun05PM 0 0 0 0 96 0 0 0 - WLs ?? 0:00.00 [swapper] root 0.0 0.0 Sun05PM 0 1 0 0 8 0 772 368 wait ILs ?? 0:00.08 /sbin/init -- root 0.0 0.1 Sun05PM 0 2 0 0 8 0 0 8 crypto DL ?? 0:00.00 [crypto] root 0.0 0.0 Sun05PM 0 3 0 0 8 0 0 8 crypto DL ?? 0:00.00 [crypto returns] root 0.0 0.0 Sun05PM 0 4 0 0 -8 0 0 8 - DL ?? 0:11.47 [g_event] root 0.0 0.0 Sun05PM 0 5 0 0 -8 0 0 8 - DL ?? 0:14.95 [g_up] root 0.0 0.0 Sun05PM 0 6 0 1 -8 0 0 8 - DL ?? 0:17.02 [g_down] root 0.0 0.0 Sun05PM 0 7 0 0 8 0 0 8 - DL ?? 0:00.00 [kqueue taskq] root 0.0 0.0 Sun05PM 0 8 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task_0] root 0.0 0.0 Sun05PM 0 9 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task_1] root 0.0 0.0 Sun05PM 0 12 0 1 -32 0 0 8 - WL ?? 148:47.86 [swi4: clock sio root 0.0 0.0 Sun05PM 0 13 0 0 -36 0 0 8 - WL ?? 0:00.00 [swi3: vm] root 0.0 0.0 Sun05PM 0 14 0 0 -16 0 0 8 - DL ?? 8:07.19 [yarrow] root 0.0 0.0 Sun05PM 0 15 0 0 -40 0 0 8 - WL ?? 0:00.00 [swi2: cambio] root 0.0 0.0 Sun05PM 0 16 0 0 -24 0 0 8 - WL ?? 0:00.00 [swi6: task queu root 0.0 0.0 Sun05PM 0 17 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task_2] root 0.0 0.0 Sun05PM 0 18 0 1 -24 0 0 8 - WL ?? 0:00.56 [swi6: Giant tas root 0.0 0.0 Sun05PM 0 19 0 0 8 0 0 8 - DL ?? 0:00.00 [thread taskq] root 0.0 0.0 Sun05PM 0 20 0 0 -28 0 0 8 - WL ?? 0:00.00 [swi5: +] root 0.0 0.0 Sun05PM 0 21 0 0 -52 0 0 8 - WL ?? 0:00.00 [irq9: acpi0] root 0.0 0.0 Sun05PM 0 22 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq16: uhci0 uh root 0.0 0.0 Sun05PM 0 23 0 0 8 0 0 8 usbevt DL ?? 0:00.01 [usb0] root 0.0 0.0 Sun05PM 0 24 0 0 8 0 0 8 usbtsk DL ?? 0:00.00 [usbtask] root 0.0 0.0 Sun05PM 0 25 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq19: uhci1] root 0.0 0.0 Sun05PM 0 26 0 0 8 0 0 8 usbevt DL ?? 0:00.01 [usb1] root 0.0 0.0 Sun05PM 0 27 0 1 -64 0 0 8 - WL ?? 0:06.87 [irq18: uhci2+] root 0.0 0.0 Sun05PM 0 28 0 0 8 0 0 8 usbevt DL ?? 0:00.01 [usb2] root 0.0 0.0 Sun05PM 0 29 0 0 8 0 0 8 usbevt DL ?? 0:00.01 [usb3] root 0.0 0.0 Sun05PM 0 30 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq23: ehci0] root 0.0 0.0 Sun05PM 0 31 0 0 8 0 0 8 usbevt DL ?? 0:00.02 [usb4] root 0.0 0.0 Sun05PM 0 32 0 4 -68 0 0 8 - DL ?? 36:30.75 [em0 taskq] root 0.0 0.0 Sun05PM 0 33 0 0 -68 0 0 8 - WL ?? 0:00.00 [irq20: fxp0] root 0.0 0.0 Sun05PM 0 34 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq14: ata0] root 0.0 0.0 Sun05PM 0 35 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq15: ata1] root 0.0 0.0 Sun05PM 0 36 0 0 -60 0 0 8 - WL ?? 0:00.04 [irq1: atkbd0] root 0.0 0.0 Sun05PM 0 37 0 0 -48 0 0 8 - WL ?? 0:00.00 [swi0: sio] root 0.0 0.0 Sun05PM 0 38 0 0 -60 0 0 8 - WL ?? 0:00.00 [irq7: ppc0] root 0.0 0.0 Sun05PM 0 39 0 0 -16 0 0 8 psleep DL ?? 0:00.26 [pagedaemon] root 0.0 0.0 Sun05PM 0 40 0 0 20 0 0 8 psleep DL ?? 0:00.00 [vmdaemon] root 0.0 0.0 Sun05PM 0 41 0 0 171 0 0 8 pgzero DL ?? 0:58.03 [pagezero] root 0.0 0.0 Sun05PM 0 42 0 0 -16 0 0 8 psleep DL ?? 0:01.37 [bufdaemon] root 0.0 0.0 Sun05PM 0 43 0 0 -4 0 0 8 vlruwt DL ?? 0:01.78 [vnlru] root 0.0 0.0 Sun05PM 0 44 0 0 20 0 0 8 syncer DL ?? 2:53.26 [syncer] root 0.0 0.0 Sun05PM 0 45 0 0 -16 0 0 8 sdflus DL ?? 0:03.31 [softdepflush] root 0.0 0.0 Sun05PM 0 46 0 0 -64 0 0 8 - DL ?? 0:17.67 [schedcpu] root 0.0 0.0 Sun05PM 0 163 1 167 20 0 1252 728 pause Is ?? 0:00.00 adjkerntz -i root 0.0 0.1 Sun05PM 0 1242 1 165 116 0 528 388 select Is ?? 0:00.00 /sbin/devd root 0.0 0.1 Sun05PM 0 1486 1 0 96 0 1568 1104 select Ss ?? 0:19.48 /sbin/natd -f /e root 0.0 0.2 Sun05PM 65534 1590 6647 0 20 0 11788 9236 lockf S ?? 0:00.04 /usr/local/apach nobody 0.0 1.8 3:14AM 0 1645 1 0 96 0 1408 1144 select Ss ?? 0:16.44 /usr/sbin/syslog root 0.0 0.2 Sun05PM 53 1707 1 0 -16 0 9296 8436 zoneli Ds ?? 5:48.13 /usr/sbin/named bind 0.0 1.6 Sun05PM 0 1717 1 0 96 0 1504 1216 select Is ?? 0:00.23 /usr/sbin/rpcbin root 0.0 0.2 Sun05PM 0 1772 1 164 116 0 1492 1256 select Is ?? 0:00.00 /usr/sbin/mountd root 0.0 0.2 Sun05PM 0 1774 1 164 116 0 1372 1104 select Is ?? 0:00.03 nfsd: master (nf root 0.0 0.2 Sun05PM 0 1775 1774 164 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nf root 0.0 0.2 Sun05PM 0 1776 1774 164 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nf root 0.0 0.2 Sun05PM 0 1777 1774 164 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nf root 0.0 0.2 Sun05PM 0 1778 1774 164 4 0 1280 888 - I ?? 0:00.00 nfsd: server (nf root 0.0 0.2 Sun05PM 0 1784 1 0 96 0 263584 1112 select Is ?? 0:00.19 /usr/sbin/rpc.st root 0.0 0.2 Sun05PM 0 1789 1 0 96 0 1596 1364 select Is ?? 0:00.22 rpc.lockd: serve root 0.0 0.3 Sun05PM 1 1796 1789 164 4 0 1596 1364 nfsloc I ?? 0:00.00 rpc.lockd: clien daemon 0.0 0.3 Sun05PM 0 1808 1 0 96 0 3204 2436 select Ss ?? 0:01.30 /usr/local/sbin/ root 0.0 0.5 Sun05PM 0 2101 1 0 96 0 2924 1824 select Ss ?? 0:13.51 /usr/sbin/ntpd - root 0.0 0.4 Sun05PM 0 2121 1 0 96 0 1288 824 select Is ?? 0:00.33 /usr/sbin/usbd root 0.0 0.2 Sun05PM 0 2150 1 40 101 0 3520 2648 select Is ?? 0:01.11 /usr/sbin/sshd root 0.0 0.5 Sun05PM 0 2157 1 0 96 0 3508 2944 select Ss ?? 0:05.36 sendmail: accept root 0.0 0.6 Sun05PM 25 2161 1 0 20 0 3384 2804 pause Is ?? 0:00.09 sendmail: Queue smmsp 0.0 0.5 Sun05PM 0 2167 1 9 8 0 1388 1100 nanslp Ss ?? 0:27.45 /usr/sbin/cron - root 0.0 0.2 Sun05PM 65534 3605 6647 0 20 0 12148 9644 lockf S ?? 0:00.38 /usr/local/apach nobody 0.0 1.9 9:06PM 0 6647 1 0 8 0 11708 9140 nanslp Ss ?? 0:09.25 /usr/local/apach root 0.0 1.8 Sun05PM 0 6672 1 158 115 0 1468 1168 select Is ?? 0:00.00 /usr/sbin/inetd root 0.0 0.2 Sun05PM 65534 34952 6647 0 20 0 12340 9820 lockf S ?? 0:01.05 /usr/local/apach nobody 0.0 1.9 9:48PM 1001 43220 1 0 96 0 2708 2428 select Ss ?? 0:00.42 /usr/local/sbin/ dhcpd 0.0 0.5 3:46PM 65534 49660 6647 0 20 0 11788 9236 lockf S ?? 0:00.03 /usr/local/apach nobody 0.0 1.8 7:32AM 65534 49710 6647 0 20 0 11788 9236 lockf S ?? 0:00.02 /usr/local/apach nobody 0.0 1.8 7:32AM 65534 50579 6647 0 4 0 12132 9624 kqread S ?? 0:00.14 /usr/local/apach nobody 0.0 1.9 11:07PM 65534 51202 6647 0 20 0 12092 9596 lockf S ?? 0:00.13 /usr/local/apach nobody 0.0 1.9 11:10PM 0 57451 2167 0 -8 0 1388 1164 piperd S ?? 0:00.00 cron: running jo root 0.0 0.2 5:03PM 0 57452 2167 0 -8 0 1388 1164 piperd S ?? 0:00.00 cron: running jo root 0.0 0.2 5:03PM 0 57454 2167 0 -8 0 1388 1164 piperd S ?? 0:00.00 cron: running jo root 0.0 0.2 5:03PM 0 57457 57451 0 8 0 1708 1224 wait Ss ?? 0:00.00 /bin/sh -c /etc/ root 0.0 0.2 5:03PM 0 57458 57454 0 8 0 1708 1224 wait Ss ?? 0:00.00 /bin/sh -c /etc/ root 0.0 0.2 5:03PM 0 57466 57452 1 8 0 1708 1224 wait Ss ?? 0:00.00 /bin/sh -c /etc/ root 0.0 0.2 5:03PM 0 57484 57457 0 8 0 1704 1256 wait S ?? 0:00.00 /bin/sh /etc/pin root 0.0 0.2 5:03PM 0 57495 57466 2 8 0 1704 1256 wait S ?? 0:00.00 /bin/sh /etc/pin root 0.0 0.2 5:03PM 0 57509 57458 0 8 0 1704 1256 wait S ?? 0:00.00 /bin/sh /etc/pin root 0.0 0.2 5:03PM 0 57521 57495 2 8 0 1248 472 nanslp S ?? 0:00.00 sleep 21 root 0.0 0.1 5:03PM 0 57523 57484 0 8 0 1248 472 nanslp S ?? 0:00.00 sleep 22 root 0.0 0.1 5:03PM 0 57525 57509 0 8 0 1248 472 nanslp S ?? 0:00.00 sleep 20 root 0.0 0.1 5:03PM 65534 97950 6647 0 20 0 12128 9624 lockf S ?? 0:00.38 /usr/local/apach nobody 0.0 1.9 2:57AM 65534 98135 6647 0 20 0 12064 9568 lockf S ?? 0:00.22 /usr/local/apach nobody 0.0 1.9 2:58AM 65534 98319 6647 0 96 0 12260 9744 select S ?? 0:00.15 /usr/local/apach nobody 0.0 1.9 2:59AM 0 6690 1 0 8 0 1760 1512 wait Is v0 0:00.03 login [pam] (log root 0.0 0.3 Sun05PM 0 56648 6690 0 8 0 3216 2072 wait S v0 0:00.03 -bash (bash) root 0.0 0.4 4:58PM 0 57620 56648 1 96 0 1508 1032 - R+ v0 0:00.00 ps -axeluwww root 0.0 0.2 5:03PM 0 6691 1 0 8 0 1740 1488 wait Is v1 0:00.02 login [pam] (log root 0.0 0.3 Sun05PM 0 56659 6691 0 8 0 3216 2072 wait I v1 0:00.04 -bash (bash) root 0.0 0.4 4:58PM 0 6692 1 0 8 0 1736 1460 wait Is v2 0:00.02 login [pam] (log root 0.0 0.3 Sun05PM 0 57198 6692 0 5 0 3212 2068 ttyin S+ v2 0:00.01 -bash (bash) root 0.0 0.4 5:01PM 0 6693 1 158 5 0 1344 952 ttyin Is+ v3 0:00.00 /usr/libexec/get root 0.0 0.2 Sun05PM 0 6694 1 158 5 0 1344 952 ttyin Is+ v4 0:00.00 /usr/libexec/get root 0.0 0.2 Sun05PM 0 6695 1 158 5 0 1344 952 ttyin Is+ v5 0:00.00 /usr/libexec/get root 0.0 0.2 Sun05PM 0 6696 1 158 5 0 1344 952 ttyin Is+ v6 0:00.00 /usr/libexec/get root 0.0 0.2 Sun05PM 0 6697 1 158 5 0 1344 952 ttyin Is+ v7 0:00.00 /usr/libexec/get root 0.0 0.2 Sun05PM 0 2130 1 0 -58 0 3216 2844 bpf S con- 0:06.37 /usr/local/sbin/ root 0.0 0.6 Sun05PM Hopefully somebody can point me in the correct direction soon. dhcpd is locking up within 12 hours now with the latest stable from yesterday. If its the way I have the vlans all on 1 card, then I can fix that. Thanks -Jon From owner-freebsd-net@FreeBSD.ORG Wed Nov 22 22:23:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9EBD16A634 for ; Wed, 22 Nov 2006 22:23:23 +0000 (UTC) (envelope-from babolo@cicuta.babolo.ru) Received: from ints.mail.pike.ru (ints.mail.pike.ru [85.30.199.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0CAB43DA2 for ; Wed, 22 Nov 2006 22:22:37 +0000 (GMT) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 67617 invoked from network); 22 Nov 2006 22:23:06 -0000 Received: from cicuta.babolo.ru (85.30.224.245) by ints.mail.pike.ru with SMTP; 22 Nov 2006 22:23:06 -0000 Received: (nullmailer pid 951 invoked by uid 136); Wed, 22 Nov 2006 22:24:10 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: To: Alex Burke Date: Thu, 23 Nov 2006 01:24:10 +0300 (MSK) From: .@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1164234250.867542.950.nullmailer@cicuta.babolo.ru> Cc: freebsd-net@freebsd.org Subject: Re: Virtual switch on FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 22:23:23 -0000 > What I would like to do is have a sort of virtual switch emulated on > my machine - to this I would like to attach a virtual interface on the > host system, and then I am hoping that would allow me to have some > sort of stable environment for jails, because I could then alias the > jails' IP addresses to the virtual adapter and it would be like a > network in its own right with many IP addresses for many jails. > > The reason I cannot do this under the host is that my main network > adapters are all DHCP, and I would like to be able to access the jails > any time. I would like to remove the dependency of the jails on the > host environments network interface configuration. I configure loopback interfaces for permanent addresses when I get dinamic IP from PPPoE. No matter, what kind of interface are you using, they are unreacheable from your provider unless it configure routes for that addresses. Sorry my bad English. > I honestly do not know whether this is possible, and having reviewed > the VLAN documentation, netgraph and tun/tap, I don't know where to > start let alone if the facilities are there. > > Please CC me in any replies as I am not subscribed to this list. From owner-freebsd-net@FreeBSD.ORG Thu Nov 23 12:06:01 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 20BC516A4FF for ; Thu, 23 Nov 2006 12:06:01 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB3F43D53 for ; Thu, 23 Nov 2006 12:04:52 +0000 (GMT) (envelope-from citrin@citrin.ru) Received: from citrin (unknown [81.19.65.93]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: citrin.citrin.ru) by mail.classis.ru (Postfix) with ESMTP id 29C9D1222F9B for ; Thu, 23 Nov 2006 15:05:20 +0300 (MSK) Date: Thu, 23 Nov 2006 15:05:09 +0300 From: Anton Yuzhaninov X-Mailer: The Bat! (v3.62.14) Professional Organization: Rambler X-Priority: 3 (Normal) Message-ID: <0174846.20061123150509@citrin.ru> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------208B20D9562AF" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: zero kern.ipc.nsfbufs on amd64 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 12:06:01 -0000 This is a cryptographically signed message in MIME format. ------------208B20D9562AF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hello All, Why on AMD64 kern.ipc.nsfbufs always zero: # sysctl kern.ipc | fgrep nsfbufs kern.ipc.nsfbufsused: 0 kern.ipc.nsfbufspeak: 0 kern.ipc.nsfbufs: 0 # netstat -m | fgrep sfbufs 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed # uname -srim FreeBSD 6.0-RELEASE amd64 GENERIC Is this mean, that on amd64 nsfbufs have no limit? --=20 WBR, Anton Yuzhaninov. ------------208B20D9562AF-- From owner-freebsd-net@FreeBSD.ORG Thu Nov 23 12:24:26 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8CBB16A505; Thu, 23 Nov 2006 12:24:26 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7F8043ED9; Thu, 23 Nov 2006 12:20:47 +0000 (GMT) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 9D216EB092A; Thu, 23 Nov 2006 20:20:51 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id cn3dcQiq+VbZ; Thu, 23 Nov 2006 20:20:49 +0800 (CST) Received: from web229.geekcn.org (tarsier.geekcn.org [210.51.165.229]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 211ECEB115A; Thu, 23 Nov 2006 20:20:49 +0800 (CST) Authentication-Results: tarsier.geekcn.org from=delphij@delphij.net; sender-id=pass; spf=pass Received: (from www@localhost) by web229.geekcn.org (8.13.8/8.13.8/Submit) id kANCKkED092510; Thu, 23 Nov 2006 20:20:46 +0800 (CST) (envelope-from delphij@delphij.net) X-Authentication-Warning: web229.geekcn.org: www set sender to delphij@delphij.net using -f To: Jonathan Feally MIME-Version: 1.0 Date: Thu, 23 Nov 2006 20:20:46 +0800 From: In-Reply-To: <4564B5E0.3000404@netvulture.com> References: <4564B5E0.3000404@netvulture.com> Message-ID: X-Sender: delphij@delphij.net User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 6-STABLE (6.2-PRE) and applications (named natd dhcpd) getting stuckin state zoneli (zone limit) - dynamic ipfw rules not working after time- vlans on em X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 12:24:26 -0000 Hi, On Wed, 22 Nov 2006 12:41:04 -0800, Jonathan Feally wrote: > Sorry to cross post, but the net list didn't help a couple weeks back on > this. > > names, natd, and dhcpd have all been getting stuck in zoneli (zone > limit) since I upgraded to the box to stable about a month ago. It was > running a 6.1-STABLE before with out difficulty. Very little has changed > on the box. All the same applications, same ipfw rules for the most part > (just more rules for new customers). Most of the time the processes > cannot be killed. I did get lucky yesterday with dhcpd. It finally died > about an hour later. I was compiling the latest stable at the time. But > got up again today to find dhcpd in zoneli. Can someone please point me > in the correct direction to trouble shoot this problem. I don't really > know how to get a full dump of what a process is doing, so a quick what > to do and post back would be great. Will you please try the patch at: http://people.freebsd.org/~delphij/misc/patch-zonelimit-workaround To see if it gets your situation improved? Thanks in advance! Cheers, From owner-freebsd-net@FreeBSD.ORG Thu Nov 23 17:43:50 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C17316A403 for ; Thu, 23 Nov 2006 17:43:50 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B6543D5E for ; Thu, 23 Nov 2006 17:43:08 +0000 (GMT) (envelope-from dudu@dudu.ro) Received: by nz-out-0102.google.com with SMTP id i11so336220nzh for ; Thu, 23 Nov 2006 09:43:44 -0800 (PST) Received: by 10.65.219.9 with SMTP id w9mr9899866qbq.1164303824085; Thu, 23 Nov 2006 09:43:44 -0800 (PST) Received: by 10.65.110.19 with HTTP; Thu, 23 Nov 2006 09:43:44 -0800 (PST) Message-ID: Date: Thu, 23 Nov 2006 19:43:44 +0200 From: "Vlad Galu" To: freebsd-performance@freebsd.org, freebsd-net@freebsd.org In-Reply-To: <200611231652.kANGqJsr005016@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4557CECD.2000609@samsco.org> <200611130454.kAD4sZwe041556@lava.sentex.ca> <4557FF7A.8020704@samsco.org> <200611132054.kADKsFvK045726@lava.sentex.ca> <4558E3DC.6080800@samsco.org> <200611200454.kAK4sdat083568@lava.sentex.ca> <7.1.0.9.0.20061120160757.14d4a728@sentex.net> <200611220247.kAM2l9JP095066@lava.sentex.ca> <20061122130947.GM20405@obiwan.tataz.chchile.org> <200611231652.kANGqJsr005016@lava.sentex.ca> Cc: Subject: Re: em forwarding performance (was Proposed 6.2 em RELEASE patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 17:43:50 -0000 On 11/23/06, Mike Tancsa wrote: > At 08:09 AM 11/22/2006, Jeremie Le Hen wrote: > > >It would be interesting to know the real performance of Linux as a mere > >router if we want a true comparision with FreeBSD performances. > > Re-tested, this time with a LINUX UP kernel and there is not that > much difference in overall speeds. I added a few IPTABLES rules which > loaded a few of the modules. > Can you please completely remove the iptables support from your Linux configuration, as well as removing support for any packet filter in FreeBSD? Also, please enable fast_forwarding. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-net@FreeBSD.ORG Thu Nov 23 18:03:24 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B452B16A415; Thu, 23 Nov 2006 18:03:24 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 708F143D70; Thu, 23 Nov 2006 18:02:46 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id kANI3Lg4019588; Thu, 23 Nov 2006 13:03:21 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id kANI3KBf005315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Nov 2006 13:03:20 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200611231803.kANI3KBf005315@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 23 Nov 2006 13:03:24 -0500 To: "Vlad Galu" , freebsd-performance@freebsd.org, freebsd-net@freebsd.org From: Mike Tancsa In-Reply-To: References: <4557CECD.2000609@samsco.org> <200611130454.kAD4sZwe041556@lava.sentex.ca> <4557FF7A.8020704@samsco.org> <200611132054.kADKsFvK045726@lava.sentex.ca> <4558E3DC.6080800@samsco.org> <200611200454.kAK4sdat083568@lava.sentex.ca> <7.1.0.9.0.20061120160757.14d4a728@sentex.net> <200611220247.kAM2l9JP095066@lava.sentex.ca> <20061122130947.GM20405@obiwan.tataz.chchile.org> <200611231652.kANGqJsr005016@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: em forwarding performance (was Proposed 6.2 em RELEASE patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 18:03:24 -0000 At 12:43 PM 11/23/2006, Vlad Galu wrote: > Can you please completely remove the iptables support from your >Linux configuration, as well as removing support for any packet filter >in FreeBSD? Also, please enable fast_forwarding. I did that a while ago. See http://www.tancsa.com/blast.html ---Mike From owner-freebsd-net@FreeBSD.ORG Thu Nov 23 18:20:21 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C322516A403 for ; Thu, 23 Nov 2006 18:20:21 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 100F443D5A for ; Thu, 23 Nov 2006 18:19:44 +0000 (GMT) (envelope-from dudu@dudu.ro) Received: by nz-out-0102.google.com with SMTP id i11so340437nzh for ; Thu, 23 Nov 2006 10:20:20 -0800 (PST) Received: by 10.65.219.3 with SMTP id w3mr10020508qbq.1164306020425; Thu, 23 Nov 2006 10:20:20 -0800 (PST) Received: by 10.65.110.19 with HTTP; Thu, 23 Nov 2006 10:20:20 -0800 (PST) Message-ID: Date: Thu, 23 Nov 2006 20:20:20 +0200 From: "Vlad Galu" To: "Mike Tancsa" In-Reply-To: <200611231803.kANI3KBf005315@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4557CECD.2000609@samsco.org> <200611132054.kADKsFvK045726@lava.sentex.ca> <4558E3DC.6080800@samsco.org> <200611200454.kAK4sdat083568@lava.sentex.ca> <7.1.0.9.0.20061120160757.14d4a728@sentex.net> <200611220247.kAM2l9JP095066@lava.sentex.ca> <20061122130947.GM20405@obiwan.tataz.chchile.org> <200611231652.kANGqJsr005016@lava.sentex.ca> <200611231803.kANI3KBf005315@lava.sentex.ca> Cc: freebsd-net@freebsd.org, freebsd-performance@freebsd.org Subject: Re: em forwarding performance (was Proposed 6.2 em RELEASE patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 18:20:21 -0000 On 11/23/06, Mike Tancsa wrote: > At 12:43 PM 11/23/2006, Vlad Galu wrote: > > > Can you please completely remove the iptables support from your > >Linux configuration, as well as removing support for any packet filter > >in FreeBSD? Also, please enable fast_forwarding. > > I did that a while ago. See I'm sorry, I had too much coffee :( > > http://www.tancsa.com/blast.html > > > ---Mike > > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 08:01:07 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2ECD716A407 for ; Fri, 24 Nov 2006 08:01:07 +0000 (UTC) (envelope-from hemanth.thummala@wipro.com) Received: from wip-ec-mm01.wipro.com (wip-ec-mm01.wipro.com [203.91.193.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 020A943D5A for ; Fri, 24 Nov 2006 08:00:22 +0000 (GMT) (envelope-from hemanth.thummala@wipro.com) Received: from wip-ec-mm01.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 27C341F61CB for ; Fri, 24 Nov 2006 13:31:00 +0530 (IST) Received: from wipro.tcpn.com (adm.wipro.tcpn.com [172.31.41.11]) by wip-ec-mm01.wipro.com (Postfix) with ESMTP id DE39A1F6093 for ; Fri, 24 Nov 2006 13:30:59 +0530 (IST) Received: from EC4HP131244 ([172.31.44.83]) by wipro.tcpn.com (8.9.3/8.9.3) with ESMTP id NAA16199 for ; Fri, 24 Nov 2006 13:23:32 +0530 (IST) Message-Id: <200611240753.NAA16199@wipro.tcpn.com> From: "Hemanth" To: Date: Fri, 24 Nov 2006 13:34:37 +0530 Organization: Wipro MIME-Version: 1.0 X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AccPnyxp/ycRC9gFRLKQGbQWjPiihg== Importance: High Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: problem: TCPIP process loops and priority reduced to 1. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hemanth.thummala@wipro.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 08:01:07 -0000 Hi All, As mentioned in the subject the TCPIP is looping and its priority is reducing to 1 by the kernal (BSD kind) >From the dump, we were able to identify the inpcbs that are causing the problem. inpcb:0x222f1a0c, lport:10143, laddr:0x7f000001 (127.0.0.1) fport: 1378 faddr:0x7f000001 (127.0.0.1) tcpcb:0x2270760c inpcb:0x222f1a0c flags:0x01e0 and inpcb:0x224a850c, lport: 1378, laddr:0x7f000001 (127.0.0.1) fport:10143 faddr:0x7f000001 (127.0.0.1) tcpcb:0x2268d10c inpcb:0x224a850c flags:0x01e0 flags:0x0000 If we see the tcpcb structure for both structures $5 = { seg_next_md = 0xfffc0000, t_state = 0x5,====>>> CLOSE_WAIT state t_rxtshift = 0x0, t_rxtcur = 0x3fc, t_dupacks = 0x0, t_maxseg = 0x7d00, t_force = 0x0, t_flags = 0x1e0, t_template = 0x22776bd4, t_inpcb = 0x224a850c, snd_una = 0xbfaeb6d9, snd_nxt = 0xbfaeb6d9, snd_up = 0xbfaeb6d9, snd_wl1 = 0xbfb19e13, snd_wl2 = 0xbfaeb6d9, iss = 0xbfaeb678, snd_wnd = 0x7d00, rcv_wnd = 0xf96, rcv_nxt = 0xbfb19e15, rcv_up = 0xbfb19e13, irs = 0xbfb0a0a2, rcv_adv = 0xbfb19daa, snd_max = 0xbfaeb6d9, inv_SYN_seqbase = 0xffaeb678, snd_cwnd = 0x17f10, snd_ssthresh = 0x3fffc000, t_idle = 0x0003934ba0b407c6, t_rtt = 0x0, t_rtseq = 0xbfaeb6c8, t_srtt = 0xba2, t_rttvar = 0x288, max_rcvd = 0x7d6a, max_sndwnd = 0x7d00, t_oobflags = 0x0, t_iobc = 0x0, tm_running = 0x0, No timer running tm_q = 0x8003378, tm_wait = 0x3fc, tm_exp_time = 0x0003934b7cb490dc, saved_rtt_clock = 0x0003934b7ca5007c, conn_exp_time = 0x0003934b811903db, tm_prev = 0x0, tm_next = 0x0, on_delay_ack_q = 0x0, dack_next = 0x0, dack_prev = 0x0, snd_scale = 0x0, rcv_scale = 0x0, request_r_scale = 0x0, requested_s_scale = 0x0, ts_recent = 0x6e49637, ts_recent_age = 0x6e49638, last_ack_sent = 0xbfb19e15 } And $8 = { seg_next_md = 0xfffc0000, t_state = 0x6, ==========>>> FIN_WAIT_1 t_rxtshift = 0x2, t_rxtcur = 0x3eb, t_dupacks = 0x0, t_maxseg = 0x7d00, t_force = 0x0, t_flags = 0x1e0, t_template = 0x22a1e1d4, t_inpcb = 0x222f1a0c, snd_una = 0xbfb19e13, snd_nxt = 0xbfb19e13, snd_up = 0xbfb19e13, snd_wl1 = 0xbfaeb6d9, snd_wl2 = 0xbfb19e13, iss = 0xbfb0a0a2, snd_wnd = 0x0, rcv_wnd = 0x7d00, rcv_nxt = 0xbfaeb6d9, rcv_up = 0xbfaeb6d9, irs = 0xbfaeb678, rcv_adv = 0xbfaf33d9, snd_max = 0xbfb19e14, inv_SYN_seqbase = 0xffaeb678, snd_cwnd = 0xffff, snd_ssthresh = 0x3fffc000, t_idle = 0x0003934ba0b407c6, t_rtt = 0x0, t_rtseq = 0xbfb17daa, t_srtt = 0x1f40, t_rttvar = 0x3, max_rcvd = 0x0, max_sndwnd = 0x7d00, t_oobflags = 0x0, t_iobc = 0x0, tm_running = 0x2,==== >> PERSIST TIMER is running on this end. tm_q = 0x8004460, tm_wait = 0x1388, tm_exp_time = 0x0003934ba1005255, saved_rtt_clock = 0x0003934b7df4342c, conn_exp_time = 0x0003934b811903de, tm_prev = 0x0, tm_next = 0x0, on_delay_ack_q = 0x0, dack_next = 0x0, dack_prev = 0x0, snd_scale = 0x0, rcv_scale = 0x0, request_r_scale = 0x0, requested_s_scale = 0x0, ts_recent = 0x6e4917e, ts_recent_age = 0x6e4917e, last_ack_sent = 0xbfaeb6d9 } If we closely look into this structure, the snd_max of one end (which is in FIN_WAIT_1 state) is less than the rcv_nxt of another end (which is in CLOSE_WAIT). When the end (present in CLOSE_WAIT) sends any frame it will put rcv_nxt field in the ti_ack field. Because of the below code, a check SEQ_GT(ti->ti_ack, tp->snd_max) at the end which is in FIN_WAIT_1 will fail resulting in it to drop the packed and send an ack with ack sequence number it is expecting. Snippet from tcp_input() 1523 tp->t_dupacks = 0; 1524 if (SEQ_GT(ti->ti_ack, tp->snd_max)) { 1525 tcpstat.tcps_rcvacktoomuch++; 1526 goto dropafterack; 1527 } If we dump the tcpstat information from the online cpu dump: $2 = { ... . . . . . . tcps_connattempt = 382657891, tcps_rcvtotal = 272941912, tcps_sndtotal = 272848321, tcps_noport = 13535, tcps_rcvurp = 0, . . . tcps_sndacks = -394474409, tcps_rcvacktoomuch = 34255849, tcps_rcvackpack = 425941141, tcps_rcvackbyte = 603776015, tcps_rcvwinupd = 651289, tcps_predack = 2280435060, .. tcps_sc_aborted = 0, tcps_sc_dupesyn = 0, tcps_sc_dropped = 0 and the tcpstat captured in the saveabend tcpstat = .. . . . . tcps_connattempt = 382657891 tcps_rcvtotal = 421811861 tcps_sndtotal = 421718270 tcps_noport = 13535 tcps_rcvurp = 0 ... ... tcps_sndacks = -245604460 tcps_rcvacktoomuch = 108690823 tcps_rcvackpack = 425941141 tcps_rcvackbyte = 603776015 tcps_rcvwinupd = 651289 tcps_predack = 2280435060 ... tcps_sc_aborted = 0 tcps_sc_dupesyn = 0 tcps_sc_dropped = 0 We see lot of difference in three values, tcps_rcvtotal,tcps_sndtotal and tcps_rcvacktoomuch and rest of the values remains the same. These values have increased ie almost doubled between time when cpu dump was taken ( Priority was 9) and the save abend (priority is 1). We presume that this observation is important clue for the problem and will work further by looking at code in what scenarios these values will increase. This will cause another end to send ack again with incorrect sequence number. These events ie of repeated acks continue which led the tcpip proc to loop and hence priority was reduced to 1. This explains the reason behind why only tcps_rcvtotal, tcps_sndtotal, tcps_rcvduppack and tcps_rcvacktoomuch are getting incremented in tcpstats. We simulated the problem by making one end to send ACK frame with ack seq number higher than the expected. This resulted in loop and priority was reduced to one. We are now looking at the scenarios when an ACK packet can come with ack sequence number higher than expected. We are wondering in which scenarios this type of problem can occur in BSD. I am looking for urgent feedbacks. Regards, Hemanth. From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 09:44:46 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 725FF16A417 for ; Fri, 24 Nov 2006 09:44:46 +0000 (UTC) (envelope-from jostreff@mobikom.com) Received: from mail.classic-bg.net (87-126-29-101.btc-net.bg [87.126.29.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 778E943D5C for ; Fri, 24 Nov 2006 09:44:03 +0000 (GMT) (envelope-from jostreff@mobikom.com) Received: (qmail 4262 invoked by uid 1002); 24 Nov 2006 09:44:41 -0000 Received: from 212.5.128.74 by classic.classic-bg.net (envelope-from , uid 89) with qmail-scanner-1.25 (f-prot: 4.6.6/3.16.14. spamassassin: 3.1.7. Clear:RC:1(212.5.128.74):. Processed in 0.262848 secs); 24 Nov 2006 09:44:41 -0000 X-Qmail-Scanner-Mail-From: jostreff@mobikom.com via classic.classic-bg.net X-Qmail-Scanner: 1.25 (Clear:RC:1(212.5.128.74):. Processed in 0.262848 secs) Received: from unknown (HELO ?212.5.128.74?) (jordan@ostreff.info@212.5.128.74) by 192.168.1.2 with ESMTPA; 24 Nov 2006 09:44:41 -0000 Message-ID: <4566BF05.7030500@mobikom.com> Date: Fri, 24 Nov 2006 11:44:37 +0200 From: Jordan Ostreff User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 References: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> <45615A05.6060009@optim.com.ru> In-Reply-To: <45615A05.6060009@optim.com.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-security@freebsd.org, freebsd-net@freebsd.org Subject: Re: which windows software can communicate with ipsec(racoon)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 09:44:46 -0000 Cisco VPN uses by default udp communication not TCP - maybe this is related to your problem. Nikolay Mirin wrote: > You don't need extra software for 2000&XP. > Just define IPSec policies properly. > > Zhao Tongyi said the following on 20.11.2006 1:17: >> I have tested cisco vpn software,found build the phase ONE >> successfully,but >> phase two can't build up. >> Anyone have advice?? >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to >> "freebsd-security-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 10:46:51 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9199A16A407; Fri, 24 Nov 2006 10:46:51 +0000 (UTC) (envelope-from lupe@lupe-christoph.de) Received: from buexe.b-5.de (buexe.b-5.de [84.19.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2873143D5A; Fri, 24 Nov 2006 10:46:09 +0000 (GMT) (envelope-from lupe@lupe-christoph.de) Received: from antalya.lupe-christoph.de (antalya.lupe-christoph.de [172.17.0.9]) by buexe.b-5.de (8.13.4/8.13.4/b-5/buexe-3.6.3) with ESMTP id kAOAkmWd013070; Fri, 24 Nov 2006 11:46:48 +0100 Received: from localhost (localhost [127.0.0.1]) by antalya.lupe-christoph.de (Postfix) with ESMTP id 456DB34528; Fri, 24 Nov 2006 11:46:43 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at lupe-christoph.de Received: from antalya.lupe-christoph.de ([127.0.0.1]) by localhost (antalya.lupe-christoph.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iX0L9HyYhHM4; Fri, 24 Nov 2006 11:46:39 +0100 (CET) Received: by antalya.lupe-christoph.de (Postfix, from userid 1000) id 4FB4C34527; Fri, 24 Nov 2006 11:46:39 +0100 (CET) Date: Fri, 24 Nov 2006 11:46:39 +0100 To: Jordan Ostreff Message-ID: <20061124104639.GB11099@lupe-christoph.de> Mail-Followup-To: Jordan Ostreff , freebsd-security@freebsd.org, freebsd-net@freebsd.org References: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> <45615A05.6060009@optim.com.ru> <4566BF05.7030500@mobikom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4566BF05.7030500@mobikom.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: lupe@lupe-christoph.de (Lupe Christoph) Cc: freebsd-security@freebsd.org, freebsd-net@freebsd.org Subject: Re: which windows software can communicate with ipsec(racoon)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 10:46:51 -0000 On Friday, 2006-11-24 at 11:44:37 +0200, Jordan Ostreff wrote: > Cisco VPN uses by default udp communication not TCP - maybe this is > related to your problem. IPSec normally uses AH and ESP which are protocols in the same layer as UDP and TCP. The protocol numbers are 51 and 50. If a firewall blocks all protocols besides UDP and TCP, and filters those protocols by ports, you can only use UDP encapsulation. I never tried to do this with FreeBSD, though. Dunno if the kernel can do that. I didn't find such a thing in the setkey manpage on 5.3. It mentions TCP, though. HTH, Lupe Christoph -- | You know we're sitting on four million pounds of fuel, one nuclear | | weapon and a thing that has 270,000 moving parts built by the lowest | | bidder. Makes you feel good, doesn't it? | | Rockhound in "Armageddon", 1998, about the Space Shuttle | From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 11:10:03 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6250B16A407; Fri, 24 Nov 2006 11:10:03 +0000 (UTC) (envelope-from e-masson@kisoft-services.com) Received: from mallaury.nerim.net (smtp-105-friday.noc.nerim.net [62.4.17.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19D2643D55; Fri, 24 Nov 2006 11:09:21 +0000 (GMT) (envelope-from e-masson@kisoft-services.com) Received: from srvbsdnanssv.interne.kisoft-services.com (kisoft.net1.nerim.net [62.212.107.51]) by mallaury.nerim.net (Postfix) with ESMTP id 9299C4F454; Fri, 24 Nov 2006 12:09:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by srvbsdnanssv.interne.kisoft-services.com (Postfix) with ESMTP id 9C013C843; Fri, 24 Nov 2006 12:09:58 +0100 (CET) X-Virus-Scanned: amavisd-new at interne.kisoft-services.com Received: from srvbsdnanssv.interne.kisoft-services.com ([127.0.0.1]) by localhost (srvbsdnanssv.interne.kisoft-services.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N6T4ZFRyRAUW; Fri, 24 Nov 2006 12:09:52 +0100 (CET) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id 41E2EC825; Fri, 24 Nov 2006 12:09:52 +0100 (CET) To: "Zhao Tongyi" From: Eric Masson In-Reply-To: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> (Zhao Tongyi's message of "Mon, 20 Nov 2006 15:17:44 +0800") References: <380d4510611192317g3c9e415al61494e5979b3f282@mail.gmail.com> X-Operating-System: FreeBSD 6.1-RELEASE-p10 i386 Date: Fri, 24 Nov 2006 12:09:52 +0100 Message-ID: <86ejrt9k3j.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b27 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-security@freebsd.org, freebsd-net@freebsd.org Subject: Re: which windows software can communicate with ipsec(racoon)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 11:10:03 -0000 "Zhao Tongyi" writes: Hi, > I have tested cisco vpn software,found build the phase ONE successfully,but > phase two can't build up. Probably a setup problem, I've been able to setup l2tp/ipsec tunnels between an XP box and a FreeBSD 6.1-RELEASE box (ipsec-tools racoon-0.6.x) > Anyone have advice?? Depending on what you need, maybe this software could help you : http://shrew.net/?page=software -- j ai ete sur le site et j ai decouvert le programme. a quel niveau y a til un probleme? Merci d eclairer ma lanterne. si je pouvais ne pas etre traiter de gugusse, ce serait tres gentil de votre part... -+- phjl in GNU : S'il te plait monsieur, dessine moi un neuneu -+- From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 11:44:35 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 023CA16A62A for ; Fri, 24 Nov 2006 11:44:35 +0000 (UTC) (envelope-from hemanth.thummala@wipro.com) Received: from wip-ec-mm01.wipro.com (wip-ec-mm01.wipro.com [203.91.193.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C5C43D46 for ; Fri, 24 Nov 2006 11:43:51 +0000 (GMT) (envelope-from hemanth.thummala@wipro.com) Received: from wip-ec-mm01.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id DC7F31F61D7 for ; Fri, 24 Nov 2006 17:14:30 +0530 (IST) Received: from wipro.tcpn.com (adm.wipro.tcpn.com [172.31.41.11]) by wip-ec-mm01.wipro.com (Postfix) with ESMTP id A0FC61F6231 for ; Fri, 24 Nov 2006 17:14:30 +0530 (IST) Received: from EC4HP131244 ([172.31.44.83]) by wipro.tcpn.com (8.9.3/8.9.3) with ESMTP id RAA21953 for ; Fri, 24 Nov 2006 17:07:02 +0530 (IST) Message-Id: <200611241137.RAA21953@wipro.tcpn.com> From: "Hemanth" To: Date: Fri, 24 Nov 2006 17:18:09 +0530 Organization: Wipro MIME-Version: 1.0 X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AccPnyxp/ycRC9gFRLKQGbQWjPiihgAHdyPw Importance: High Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FW: problem: TCPIP process loops and priority reduced to 1. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hemanth.thummala@wipro.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 11:44:35 -0000 Some more info on this: from tcpcb of FIN_WAIT_1 end i have seen t_rxtshift value is 2, means 2 probe requests have gone from this side. Normally when probe request is going the snd_nxt value wont be incremented. In our case if the probe request is sent with FIN (dont know the possiblity), then the other side while this packet is processed in tcp_input.c we can have this following scenario. /* * If FIN is received ACK the FIN and let the user know * that the connection is closing. */ if (tiflags & TH_FIN) { if (TCPS_HAVERCVDFIN(tp->t_state) == 0) { socantrcvmore(so); tp->t_flags |= TF_ACKNOW; tp->rcv_nxt++; ===========>>> here the rcv_nxt is incremented if the probe contains FIN. } This may be the reason for getting the incremented rcv_nxt(XXXX13) value than the expected snd_max(XXXX14). Now my question is : In what scenarios a FIN can be set in a probe request?? looking for urgent replies.. Regards, Hemanth, _____ From: Hemanth [mailto:hemanth.thummala@wipro.com] Sent: Friday, November 24, 2006 1:35 PM To: 'freebsd-net@freebsd.org' Subject: problem: TCPIP process loops and priority reduced to 1. Importance: High Hi All, As mentioned in the subject the TCPIP is looping and its priority is reducing to 1 by the kernal (BSD kind) >From the dump, we were able to identify the inpcbs that are causing the problem. inpcb:0x222f1a0c, lport:10143, laddr:0x7f000001 (127.0.0.1) fport: 1378 faddr:0x7f000001 (127.0.0.1) tcpcb:0x2270760c inpcb:0x222f1a0c flags:0x01e0 and inpcb:0x224a850c, lport: 1378, laddr:0x7f000001 (127.0.0.1) fport:10143 faddr:0x7f000001 (127.0.0.1) tcpcb:0x2268d10c inpcb:0x224a850c flags:0x01e0 flags:0x0000 If we see the tcpcb structure for both structures $5 = { seg_next_md = 0xfffc0000, t_state = 0x5,====>>> CLOSE_WAIT state t_rxtshift = 0x0, t_rxtcur = 0x3fc, t_dupacks = 0x0, t_maxseg = 0x7d00, t_force = 0x0, t_flags = 0x1e0, t_template = 0x22776bd4, t_inpcb = 0x224a850c, snd_una = 0xbfaeb6d9, snd_nxt = 0xbfaeb6d9, snd_up = 0xbfaeb6d9, snd_wl1 = 0xbfb19e13, snd_wl2 = 0xbfaeb6d9, iss = 0xbfaeb678, snd_wnd = 0x7d00, rcv_wnd = 0xf96, rcv_nxt = 0xbfb19e15, rcv_up = 0xbfb19e13, irs = 0xbfb0a0a2, rcv_adv = 0xbfb19daa, snd_max = 0xbfaeb6d9, inv_SYN_seqbase = 0xffaeb678, snd_cwnd = 0x17f10, snd_ssthresh = 0x3fffc000, t_idle = 0x0003934ba0b407c6, t_rtt = 0x0, t_rtseq = 0xbfaeb6c8, t_srtt = 0xba2, t_rttvar = 0x288, max_rcvd = 0x7d6a, max_sndwnd = 0x7d00, t_oobflags = 0x0, t_iobc = 0x0, tm_running = 0x0, No timer running tm_q = 0x8003378, tm_wait = 0x3fc, tm_exp_time = 0x0003934b7cb490dc, saved_rtt_clock = 0x0003934b7ca5007c, conn_exp_time = 0x0003934b811903db, tm_prev = 0x0, tm_next = 0x0, on_delay_ack_q = 0x0, dack_next = 0x0, dack_prev = 0x0, snd_scale = 0x0, rcv_scale = 0x0, request_r_scale = 0x0, requested_s_scale = 0x0, ts_recent = 0x6e49637, ts_recent_age = 0x6e49638, last_ack_sent = 0xbfb19e15 } And $8 = { seg_next_md = 0xfffc0000, t_state = 0x6, ==========>>> FIN_WAIT_1 t_rxtshift = 0x2, t_rxtcur = 0x3eb, t_dupacks = 0x0, t_maxseg = 0x7d00, t_force = 0x0, t_flags = 0x1e0, t_template = 0x22a1e1d4, t_inpcb = 0x222f1a0c, snd_una = 0xbfb19e13, snd_nxt = 0xbfb19e13, snd_up = 0xbfb19e13, snd_wl1 = 0xbfaeb6d9, snd_wl2 = 0xbfb19e13, iss = 0xbfb0a0a2, snd_wnd = 0x0, rcv_wnd = 0x7d00, rcv_nxt = 0xbfaeb6d9, rcv_up = 0xbfaeb6d9, irs = 0xbfaeb678, rcv_adv = 0xbfaf33d9, snd_max = 0xbfb19e14, inv_SYN_seqbase = 0xffaeb678, snd_cwnd = 0xffff, snd_ssthresh = 0x3fffc000, t_idle = 0x0003934ba0b407c6, t_rtt = 0x0, t_rtseq = 0xbfb17daa, t_srtt = 0x1f40, t_rttvar = 0x3, max_rcvd = 0x0, max_sndwnd = 0x7d00, t_oobflags = 0x0, t_iobc = 0x0, tm_running = 0x2,==== >> PERSIST TIMER is running on this end. tm_q = 0x8004460, tm_wait = 0x1388, tm_exp_time = 0x0003934ba1005255, saved_rtt_clock = 0x0003934b7df4342c, conn_exp_time = 0x0003934b811903de, tm_prev = 0x0, tm_next = 0x0, on_delay_ack_q = 0x0, dack_next = 0x0, dack_prev = 0x0, snd_scale = 0x0, rcv_scale = 0x0, request_r_scale = 0x0, requested_s_scale = 0x0, ts_recent = 0x6e4917e, ts_recent_age = 0x6e4917e, last_ack_sent = 0xbfaeb6d9 } If we closely look into this structure, the snd_max of one end (which is in FIN_WAIT_1 state) is less than the rcv_nxt of another end (which is in CLOSE_WAIT). When the end (present in CLOSE_WAIT) sends any frame it will put rcv_nxt field in the ti_ack field. Because of the below code, a check SEQ_GT(ti->ti_ack, tp->snd_max) at the end which is in FIN_WAIT_1 will fail resulting in it to drop the packed and send an ack with ack sequence number it is expecting. Snippet from tcp_input() 1523 tp->t_dupacks = 0; 1524 if (SEQ_GT(ti->ti_ack, tp->snd_max)) { 1525 tcpstat.tcps_rcvacktoomuch++; 1526 goto dropafterack; 1527 } If we dump the tcpstat information from the online cpu dump: $2 = { ... . . . . . . tcps_connattempt = 382657891, tcps_rcvtotal = 272941912, tcps_sndtotal = 272848321, tcps_noport = 13535, tcps_rcvurp = 0, . . . tcps_sndacks = -394474409, tcps_rcvacktoomuch = 34255849, tcps_rcvackpack = 425941141, tcps_rcvackbyte = 603776015, tcps_rcvwinupd = 651289, tcps_predack = 2280435060, .. tcps_sc_aborted = 0, tcps_sc_dupesyn = 0, tcps_sc_dropped = 0 and the tcpstat captured in the saveabend tcpstat = .. . . . . tcps_connattempt = 382657891 tcps_rcvtotal = 421811861 tcps_sndtotal = 421718270 tcps_noport = 13535 tcps_rcvurp = 0 ... ... tcps_sndacks = -245604460 tcps_rcvacktoomuch = 108690823 tcps_rcvackpack = 425941141 tcps_rcvackbyte = 603776015 tcps_rcvwinupd = 651289 tcps_predack = 2280435060 ... tcps_sc_aborted = 0 tcps_sc_dupesyn = 0 tcps_sc_dropped = 0 We see lot of difference in three values, tcps_rcvtotal,tcps_sndtotal and tcps_rcvacktoomuch and rest of the values remains the same. These values have increased ie almost doubled between time when cpu dump was taken ( Priority was 9) and the save abend (priority is 1). We presume that this observation is important clue for the problem and will work further by looking at code in what scenarios these values will increase. This will cause another end to send ack again with incorrect sequence number. These events ie of repeated acks continue which led the tcpip proc to loop and hence priority was reduced to 1. This explains the reason behind why only tcps_rcvtotal, tcps_sndtotal, tcps_rcvduppack and tcps_rcvacktoomuch are getting incremented in tcpstats. We simulated the problem by making one end to send ACK frame with ack seq number higher than the expected. This resulted in loop and priority was reduced to one. We are now looking at the scenarios when an ACK packet can come with ack sequence number higher than expected. We are wondering in which scenarios this type of problem can occur in BSD. I am looking for urgent feedbacks. Regards, Hemanth. From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 13:33:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14E8716A417 for ; Fri, 24 Nov 2006 13:33:25 +0000 (UTC) (envelope-from adrenalinup@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FED543D5F for ; Fri, 24 Nov 2006 13:32:42 +0000 (GMT) (envelope-from adrenalinup@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so1171684nfc for ; Fri, 24 Nov 2006 05:33:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=joEwFPF6YGqPhpWdyEpvLmw3v3020/4ZLFff5wdWJNsYEjK1CtNaw8FyZcRb0eGKG7HjGuC8Rs3ZaV3VwG7d31mm4jjEA7coQEDDUWQjCoO0SVOxBV5y5BTFVD6lc2+8auiJLTP0vp0jXeZ5VvinnzZ0/TOBmGn00yy/SfPWdRA= Received: by 10.82.111.8 with SMTP id j8mr1577820buc.1164375202100; Fri, 24 Nov 2006 05:33:22 -0800 (PST) Received: by 10.82.164.8 with HTTP; Fri, 24 Nov 2006 05:33:21 -0800 (PST) Message-ID: Date: Fri, 24 Nov 2006 15:33:21 +0200 From: "Nicolae Namolovan" To: support@syskonnect.de, andre@freebsd.org, freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Marvell Yukon 88E8056 FreeBsd Drivers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 13:33:25 -0000 I took the hack from http://kerneltrap.org/node/7135, that guy said that in linux you must "add the 4364 devID into sky2.c symply search for 4363". I apply the same idea to http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz, modifyed oem.c and oem.h, oem.c { VENDOR_ID_MRVL, DEV_ID_MRVL_4361, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, "Marvell 88E8050 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, { VENDOR_ID_MRVL, DEV_ID_MRVL_4362, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, "Marvell 88E8053 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, + /* custom add..not sure */ + { VENDOR_ID_MRVL, DEV_ID_MRVL_4364, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, + "Marvell 88E8056 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, oem.h #define DEV_ID_MRVL_4362 0x4362 + /* custom add..not sure */ + #define DEV_ID_MRVL_4364 0x4364 After I compile it. That was sufficient to make this driver to hook mine Marvell Yukon 88E8056, I can see it in ifconfig but i get: "status: no carrier" Tried to make the interface down/up, put away/back the network cable, didn't help.. Still "no carrier". But it works fine under M Windows (so the problem is not in network cable or the network device).. Any suggestions ? Maybe I must load the Windows drivers with NDIS, but I'm afraid of performance degradation/instability ? Marvell Yukon 88E8056 are in the popular ASUS P5B and Gigabyte 965P-S3 motherboards. -- Best regards, Nicolae Namolovan. From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 18:35:14 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BBB316A416 for ; Fri, 24 Nov 2006 18:35:14 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B57743D6B for ; Fri, 24 Nov 2006 18:34:30 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 7C90D200213; Fri, 24 Nov 2006 19:35:11 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 479CC1FF903; Fri, 24 Nov 2006 19:35:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 915D2444892; Fri, 24 Nov 2006 18:32:23 +0000 (UTC) Date: Fri, 24 Nov 2006 18:32:23 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Nicolae Namolovan In-Reply-To: Message-ID: <20061124183047.U25145@maildrop.int.zabbadoz.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org Subject: Re: Marvell Yukon 88E8056 FreeBsd Drivers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 18:35:14 -0000 On Fri, 24 Nov 2006, Nicolae Namolovan wrote: > I took the hack from http://kerneltrap.org/node/7135, that guy said > that in linux you must "add the 4364 devID into sky2.c symply search > for 4363". > > I apply the same idea to > http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz, > modifyed oem.c and oem.h, ... > > Any suggestions ? Whatever you are going to try be sure it is this one: http://people.freebsd.org/~yongari/msk/ You'll find some/a lot of follow-ups to this mail and other threads http://lists.freebsd.org/pipermail/freebsd-current/2006-September/066100.html from the last months on freebsd-current and freebsd-net. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 21:26:47 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 74B2316A403; Fri, 24 Nov 2006 21:26:47 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from rackman.netvulture.com (adsl-63-197-17-60.dsl.snfc21.pacbell.net [63.197.17.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ADAA43D64; Fri, 24 Nov 2006 21:25:09 +0000 (GMT) (envelope-from vulture@netvulture.com) Received: from [192.168.2.249] (coolman [208.201.244.79]) (authenticated bits=0) by rackman.netvulture.com (8.13.5/8.13.5) with ESMTP id kAOLOK4n009982; Fri, 24 Nov 2006 13:24:21 -0800 (PST) Message-ID: <456762ED.4050408@netvulture.com> Date: Fri, 24 Nov 2006 13:23:57 -0800 From: Jonathan Feally User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: delphij@delphij.net References: <4564B5E0.3000404@netvulture.com> In-Reply-To: X-netvulture_com-MailScanner-Information: Please contact the ISP for more information X-netvulture_com-MailScanner: Found to be clean X-netvulture_com-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (timed out) X-netvulture_com-MailScanner-From: vulture@netvulture.com X-Spam-Status: No Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 6-STABLE (6.2-PRE) and applications (named natd dhcpd) getting stuckin state zoneli (zone limit) - dynamic ipfw rules not working after time- vlans on em X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 21:26:47 -0000 Running the patch now. So far its still running. Up for 22:57 at the moment. I also made a change to my kern.maxusers to make it 320. It was setting it at 250 automatically, so I bumped it up as I saw someone else's post on a bug saying his maxusers option in the kernel was 15. Figured smaller number made it worse. I am now running a slightly more stripped down kernel as well, UP with POLLING on my em0. Hopefully this patch will solve the problems as I've had this issue with a bunch of different network apps. -Jon delphij@delphij.net wrote: >Hi, > >On Wed, 22 Nov 2006 12:41:04 -0800, Jonathan Feally wrote: > > >>Sorry to cross post, but the net list didn't help a couple weeks back on >>this. >> >>names, natd, and dhcpd have all been getting stuck in zoneli (zone >>limit) since I upgraded to the box to stable about a month ago. It was >>running a 6.1-STABLE before with out difficulty. Very little has changed >>on the box. All the same applications, same ipfw rules for the most part >>(just more rules for new customers). Most of the time the processes >>cannot be killed. I did get lucky yesterday with dhcpd. It finally died >>about an hour later. I was compiling the latest stable at the time. But >>got up again today to find dhcpd in zoneli. Can someone please point me >>in the correct direction to trouble shoot this problem. I don't really >>know how to get a full dump of what a process is doing, so a quick what >>to do and post back would be great. >> >> > >Will you please try the patch at: > >http://people.freebsd.org/~delphij/misc/patch-zonelimit-workaround > >To see if it gets your situation improved? > >Thanks in advance! > >Cheers, > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > > From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 23:47:54 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF01B16A528 for ; Fri, 24 Nov 2006 23:47:54 +0000 (UTC) (envelope-from m.jakeman@lancaster.ac.uk) Received: from hedwig.lancs.ac.uk (hedwig.lancs.ac.uk [148.88.0.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id D941743DA6 for ; Fri, 24 Nov 2006 23:46:41 +0000 (GMT) (envelope-from m.jakeman@lancaster.ac.uk) Received: from mail01.lancs.ac.uk ([148.88.1.53] helo=marl.lancs.ac.uk) by hedwig.lancs.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1GnklP-0002MW-JO for freebsd-net@freebsd.org; Fri, 24 Nov 2006 23:47:23 +0000 Received: from ina044000004.lancs.ac.uk ([148.88.224.46]) by marl.lancs.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1GnklL-0004Yl-3u; Fri, 24 Nov 2006 23:47:19 +0000 From: m.jakeman@lancaster.ac.uk Organization: Lancaster University To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Date: Fri, 24 Nov 2006 23:36:14 +0000 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611242336.14998.m.jakeman@lancaster.ac.uk> Cc: Subject: ifnet struct interface type X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: m.jakeman@lancaster.ac.uk List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 23:47:55 -0000 Hi, I am writing some code that is using the systems ifnet structs via ifnet_byindex(), I have two network interfaces : broadcom BCM6750A1M using the 'bge' driver Intel PRO/wireless 2915ABG using the 'iwi' driver I have written some code to output the ifnet->if_type for each interface and it shows that both have type 6 (IFT_ETHER). My question is why do they both have this type when there are IFT_GIGABITETHERNET and IFT_IEEE80211? I was planning on using this value to distinguish what sort of connection each interface is using but obviously with both returning IFT_ETHER this is not possible, any help is much appreciated! Cheers Matt From owner-freebsd-net@FreeBSD.ORG Fri Nov 24 23:57:32 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB88216A415 for ; Fri, 24 Nov 2006 23:57:32 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C25E43D7F for ; Fri, 24 Nov 2006 23:56:36 +0000 (GMT) (envelope-from josh.carroll@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so1312577nfc for ; Fri, 24 Nov 2006 15:57:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=fHTD5VmS+N6M+i5g0s5WSZVeaviAW1j4yEoulO521CrFQZ54nU8GClMkfpoJWyKJkhK0D5OHPL3AQ5lnfAs3iQDfTylAXY6GHUYi+dtkbk3jGrQxPEOl9dx5VIYFeJyCbfZ0WT84UEh8Z2a8f1R8Q3WDYfKqHBIqH0Mur8KmHMI= Received: by 10.82.126.5 with SMTP id y5mr1660435buc.1164412639694; Fri, 24 Nov 2006 15:57:19 -0800 (PST) Received: by 10.82.163.16 with HTTP; Fri, 24 Nov 2006 15:57:19 -0800 (PST) Message-ID: <8cb6106e0611241557h6b40c6f1laad08ffac29bbb6a@mail.gmail.com> Date: Fri, 24 Nov 2006 15:57:19 -0800 From: "Josh Carroll" Sender: josh.carroll@gmail.com To: m.jakeman@lancaster.ac.uk In-Reply-To: <200611242336.14998.m.jakeman@lancaster.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200611242336.14998.m.jakeman@lancaster.ac.uk> X-Google-Sender-Auth: 441b3f9ec2eddc50 Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ifnet struct interface type X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 23:57:32 -0000 > I was planning on using this value to > distinguish what sort of connection each interface is using but obviously > with both returning IFT_ETHER this is not possible, any help is much > appreciated! It would probably be better to query the interface's media setting instead, since you may have a gigabit card that autonegotiated to 100baseTx-FD or similar. You could probably take a look at /usr/src/sbin/ifconfig/ifmedia.c for details on how to query what the card's current media setting is. Regards, Josh From owner-freebsd-net@FreeBSD.ORG Sat Nov 25 01:50:45 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3AA0E16A40F for ; Sat, 25 Nov 2006 01:50:45 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DABB43D53 for ; Sat, 25 Nov 2006 01:49:57 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so947931wxc for ; Fri, 24 Nov 2006 17:50:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=X4La5X3TwVUlVwpN4XBQgjA3qqmmpsR+AIqCrEfARZxAnZEtQwsgvg190uxXdPdOlP3/fN8/EIcdKYOzFWPXRR/jS0KtX8Jppf6bevGPAq1qPK8sj9YBTSzxS9sZ74xRcq3X66fluPkXvrL0MbGOb92k1CHUZhHH5VtdKqsdj6A= Received: by 10.70.21.10 with SMTP id 10mr1992504wxu.1164419441180; Fri, 24 Nov 2006 17:50:41 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 34sm964102wra.2006.11.24.17.50.39; Fri, 24 Nov 2006 17:50:41 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id kAP1qQxT052026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Nov 2006 10:52:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id kAP1qNH3052025; Sat, 25 Nov 2006 10:52:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 25 Nov 2006 10:52:23 +0900 From: Pyun YongHyeon To: Nicolae Namolovan Message-ID: <20061125015223.GA51565@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, andre@freebsd.org, support@syskonnect.de Subject: Re: Marvell Yukon 88E8056 FreeBsd Drivers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2006 01:50:45 -0000 On Fri, Nov 24, 2006 at 03:33:21PM +0200, Nicolae Namolovan wrote: > I took the hack from http://kerneltrap.org/node/7135, that guy said > that in linux you must "add the 4364 devID into sky2.c symply search > for 4363". > > I apply the same idea to > http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz, > modifyed oem.c and oem.h, > > oem.c > { VENDOR_ID_MRVL, DEV_ID_MRVL_4361, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, > "Marvell 88E8050 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, > { VENDOR_ID_MRVL, DEV_ID_MRVL_4362, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, > "Marvell 88E8053 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, > + /* custom add..not sure */ > + { VENDOR_ID_MRVL, DEV_ID_MRVL_4364, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, > + "Marvell 88E8056 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, > > > oem.h > > #define DEV_ID_MRVL_4362 0x4362 > + /* custom add..not sure */ > + #define DEV_ID_MRVL_4364 0x4364 > > After I compile it. > > That was sufficient to make this driver to hook mine Marvell Yukon > 88E8056, I can see it in ifconfig but i get: > > "status: no carrier" > > Tried to make the interface down/up, put away/back the network cable, > didn't help.. Still "no carrier". > > But it works fine under M Windows (so the problem is not in network > cable or the network device).. > > Any suggestions ? > > Maybe I must load the Windows drivers with NDIS, but I'm afraid of > performance degradation/instability ? > > Marvell Yukon 88E8056 are in the popular ASUS P5B and Gigabyte 965P-S3 > motherboards. > You can find latest msk(4) at the following URL. http://people.freebsd.org/~yongari/msk/msk.HEAD.diff It supports the device ID you mentioned but I don't know whether it works or not. ATM the driver has three known issues. o poor Rx performance I'm working on this but had no clue so far. o 88E8055 hangup : One user reported system freeze when msk(4) is loaded. Since I don't have the hardware it's very hard to fix. :-( o Manual speed selection doesn't seem to work. It needs additional code for e1000phy(4) to fix. You need latest CURRENT to aplly the patch. The driver will print very ugly number sequnces but you can safely ingore it. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Sat Nov 25 21:33:40 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA76416A412; Sat, 25 Nov 2006 21:33:40 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from centrmmtao04.cox.net (centrmmtao04.cox.net [70.168.83.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37CD643D68; Sat, 25 Nov 2006 21:32:50 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by centrmmtao05.cox.net (InterMail vM.6.01.06.03 201-2131-130-104-20060516) with ESMTP id <20061125213112.VHCX27862.centrmmtao05.cox.net@eastrmimpo02.cox.net>; Sat, 25 Nov 2006 16:31:12 -0500 Received: from mezz.mezzweb.com ([24.255.149.218]) by eastrmimpo02.cox.net with bizsmtp id r9W61V00Q4iy4EG0000000; Sat, 25 Nov 2006 16:30:07 -0500 Date: Sat, 25 Nov 2006 15:31:51 -0600 To: "Andre Oppermann" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <455CB311.8040301@freebsd.org> <455DC0F4.1070309@freebsd.org> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <455DC0F4.1070309@freebsd.org> User-Agent: Opera Mail/9.02 (Linux) Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Automatic TCP send socker buffer sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2006 21:33:41 -0000 On Fri, 17 Nov 2006 08:02:28 -0600, Andre Oppermann = = wrote: > Andre Oppermann wrote: >> With automatic TCP send socket buffers we can start with a small buff= er >> and quickly grow it in parallel with the TCP congestion window to mat= ch >> real network conditions. > > >> The patch is available here: >> http://people.freebsd.org/~andre/tcp_auto_sndbuf-20061116.diff >> Any testers, especially with busy FTP servers, are very welcome. > > A RELENG_6 version (for FreeBSD 6.x) of the patch is here: > > http://people.freebsd.org/~andre/tcp_auto_sndbuf-20061116-RELENG_6.d= iff > > Just apply this patch and recompile your kernel. It is activated by = > default. > Be aware that all socket buffer sizing events get logged to syslog und= er > LOG_DEBUG. This may affect overall system performance and you may wan= t = > to > disable logging to disk of this in syslogd.conf. Is this relate with net.inet.tcp.sendspace? I reset my sysctl config bac= k = to default that was for wine+utorrent, so tested with wine+utorrent on = today (Nov 25th) RELENG_6 and works fine so far. [...] Nov 25 14:35:22 mezz kernel: tcp_output: inc sockbuf, old 65612, new = 73804, sb_cc 58553, snd_wnd 149760, sendwnd 36719 Nov 25 14:35:27 mezz kernel: tcp_output: inc sockbuf, old 73804, new = 81996, sb_cc 65608, snd_wnd 148896, sendwnd 38283 Nov 25 14:35:27 mezz kernel: tcp_output: inc sockbuf, old 81996, new = 90188, sb_cc 72604, snd_wnd 148896, sendwnd 38283 Nov 25 14:35:29 mezz kernel: tcp_output: inc sockbuf, old 90188, new = 98380, sb_cc 79093, snd_wnd 149760, sendwnd 39988 [...goes on...] A bit off point, I have to setup this below in sysctl to get wine+utorre= nt = download/upload very fast and ustable without hog the CPU. kern.ipc.maxsockbuf=3D2097152 net.inet.tcp.recvspace=3D262144 net.inet.tcp.sendspace=3D262144 Cheers, Mezz -- = mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org From owner-freebsd-net@FreeBSD.ORG Sat Nov 25 22:20:49 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9617716A415 for ; Sat, 25 Nov 2006 22:20:49 +0000 (UTC) (envelope-from adrenalinup@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 674FF43D7D for ; Sat, 25 Nov 2006 22:19:58 +0000 (GMT) (envelope-from adrenalinup@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so1593586nfc for ; Sat, 25 Nov 2006 14:20:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=reFYt4HLAdoN2m3SGV8qc/nymRWTgYpeag9Uqf5V37aCu9k6qcq7frV64hOeDXBegq4kU6QL2BfWXwfwJotdlex3v7eGStGYGhhOyniZFYW/fs6xGSdqG5+66ERLurWmU+YwUiXJSpNmkkgip1OfAh2UO4mMC2NIvAIt3WX9lq4= Received: by 10.82.101.3 with SMTP id y3mr1756694bub.1164493246877; Sat, 25 Nov 2006 14:20:46 -0800 (PST) Received: by 10.82.164.8 with HTTP; Sat, 25 Nov 2006 14:20:46 -0800 (PST) Message-ID: Date: Sun, 26 Nov 2006 00:20:46 +0200 From: "Nicolae Namolovan" To: pyunyh@gmail.com In-Reply-To: <20061125015223.GA51565@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061125015223.GA51565@cdnetworks.co.kr> Cc: freebsd-net@freebsd.org, andre@freebsd.org, support@syskonnect.de Subject: Re: Marvell Yukon 88E8056 FreeBsd Drivers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2006 22:20:49 -0000 Hooray, msk.HEAD.diff worked ! But only on the CURRENT.. For those who don't know very well the "patch" tool(like me ;p), msk.HEAD.diff create some new dirs, you must provide to the patch utility the -p option(thanks to the folk from irc), here's how I got it work(not sure if that's 100% correct): cp msk.HEAD.diff /usr/src/ cd /usr/src/ patch -i msk.HEAD.diff -p But I need to use it on a production server and the CURRENT one is too unstable, without too much thinking I just run ping -f 127.0.0.1 and after some minutes I got kernel panic, heh. I think the msk driver is a great addition to the 7.0 version, great job ! If anyone know how to make Marvell Yukon 88E8056 work under FreeBSD 6 stable version, I would be very pleased to hear.. On 11/25/06, Pyun YongHyeon wrote: > On Fri, Nov 24, 2006 at 03:33:21PM +0200, Nicolae Namolovan wrote: > > I took the hack from http://kerneltrap.org/node/7135, that guy said > > that in linux you must "add the 4364 devID into sky2.c symply search > > for 4363". > > > > I apply the same idea to > > http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz, > > modifyed oem.c and oem.h, > > > > oem.c > > { VENDOR_ID_MRVL, DEV_ID_MRVL_4361, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, > > "Marvell 88E8050 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, > > { VENDOR_ID_MRVL, DEV_ID_MRVL_4362, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, > > "Marvell 88E8053 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, > > + /* custom add..not sure */ > > + { VENDOR_ID_MRVL, DEV_ID_MRVL_4364, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY, > > + "Marvell 88E8056 Gigabit Ethernet Controller, Ver. 8.12.1.3"}, > > > > > > oem.h > > > > #define DEV_ID_MRVL_4362 0x4362 > > + /* custom add..not sure */ > > + #define DEV_ID_MRVL_4364 0x4364 > > > > After I compile it. > > > > That was sufficient to make this driver to hook mine Marvell Yukon > > 88E8056, I can see it in ifconfig but i get: > > > > "status: no carrier" > > > > Tried to make the interface down/up, put away/back the network cable, > > didn't help.. Still "no carrier". > > > > But it works fine under M Windows (so the problem is not in network > > cable or the network device).. > > > > Any suggestions ? > > > > Maybe I must load the Windows drivers with NDIS, but I'm afraid of > > performance degradation/instability ? > > > > Marvell Yukon 88E8056 are in the popular ASUS P5B and Gigabyte 965P-S3 > > motherboards. > > > > You can find latest msk(4) at the following URL. > http://people.freebsd.org/~yongari/msk/msk.HEAD.diff > > It supports the device ID you mentioned but I don't know whether it > works or not. ATM the driver has three known issues. > o poor Rx performance > I'm working on this but had no clue so far. > o 88E8055 hangup : > One user reported system freeze when msk(4) is loaded. Since I don't > have the hardware it's very hard to fix. :-( > o Manual speed selection doesn't seem to work. > It needs additional code for e1000phy(4) to fix. > > You need latest CURRENT to aplly the patch. The driver will print very > ugly number sequnces but you can safely ingore it. > > -- > Regards, > Pyun YongHyeon > -- Best regards, Nicolae Namolovan.