From owner-freebsd-net@FreeBSD.ORG Sun Jan 1 03:07: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3048516A41F for ; Sun, 1 Jan 2006 03:07:41 +0000 (GMT) (envelope-from reverselogic@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 059BA43D78 for ; Sun, 1 Jan 2006 03:07:34 +0000 (GMT) (envelope-from reverselogic@gmail.com) Received: by nproxy.gmail.com with SMTP id o60so299427nfa for ; Sat, 31 Dec 2005 19:07:32 -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=uR5iYbd2oXR4PrOPBKXV1cqKzz1U9jJaRW3vbFLo2mY0Bih3NiltBAu5oBV9+kAXarzhX8tYkEV8PQcECfUFlQN9dLKBVFnYvA6l1XBkcetygXs1sFrno3q3D3rRAmO9BYAK7GR1VYNhcRpXx/mam4JPa9legoLcDp9ORIvupPg= Received: by 10.48.163.10 with SMTP id l10mr460161nfe; Sat, 31 Dec 2005 19:07:31 -0800 (PST) Received: by 10.48.217.10 with HTTP; Sat, 31 Dec 2005 19:07:31 -0800 (PST) Message-ID: Date: Sun, 1 Jan 2006 03:07:31 +0000 From: Paul To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: RE: FreeBSD 6.0 Release 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, 01 Jan 2006 03:07:41 -0000 On 12/31/05, Bill Vermillion wrote: > I know you'll find this hard to believe, but on Sat, Dec 31, 2005 > at 02:52 , Paul actually admitted to saying: > > > I've just installed FreeBSD 6.0 Release yesterday, I've spend the last > > two days trying to resolve a networking problem, the problem is this: > > when I try and connect to a domain or an IP for that matter, it takes > > several minutes for it to connect + receive the content. It doesn't > > seem to effect all addresses though, I've had no problems connecting > > to ftp://ftp.freebsd.org to download software etc., nor have I had any > > problems connecting to domains inside my LAN. > > > As far as I can tell, it isn't a dns problem because I can ping > > without any problems. > > That is out-going DNS. > > You said 'connecting problems' but only mentioned 'ftp'. > > Many ftp sites require a proper reverse DNS. But since you don't > have that with ftp.freebsd.org, but you do with other ftp addresses > it most likely is a DNS problem? > > Over the years I've noticed that many ISPs which give dynamic > addresses do NOT have reverse DNS mapped. That is wrong but there > is nothing you can do about it. > > From your few details [unless you can't connect to other sites > with http] I really do think it is a DNS problem. > > Bill > > Bill > -- > Bill Vermillion - bv @ wjv . com > Hi, The details I gave were a little vague, sorry about that. The problem I'm experiencing is effecting all protocols (ftp, http, irc, ssh, etc.) ftp.freebsd.org is an example of a domain which isn't effected, another of these is irc.chatjunkies.org (They're currently the only two I've found, which appear to be unaffected by the problem). I don't think that the problem is related to my ISP, because I've had 5/6 other operating systems (mainly Linux variants) before FreeBSD, and never before have I had the same problem. Now, the problems gets even stranger... This morning I decided to install 'links', it connected to a website without any problems at all. Previously I'd been doing my testing in firefox. Of course firefox still doesn't work, neither do (ftp, ssh, etc.) I've tried recompiling each of the applications, but they still don't work. Thanks, and happy New Year. - Paul. From owner-freebsd-net@FreeBSD.ORG Sun Jan 1 11:50: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C7016A41F for ; Sun, 1 Jan 2006 11:50:50 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2030043D4C for ; Sun, 1 Jan 2006 11:50:48 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep02.bredband.com with ESMTP id <20060101115047.RHXX17186.mxfep02.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se>; Sun, 1 Jan 2006 12:50:47 +0100 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id B4F70678DC; Sun, 1 Jan 2006 12:50:46 +0100 (CET) Message-ID: <43B7C218.6070300@gneto.com> Date: Sun, 01 Jan 2006 12:50:48 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051221) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Ambrisko References: <200510141915.j9EJFJ8T059154@ambrisko.com> In-Reply-To: <200510141915.j9EJFJ8T059154@ambrisko.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: bge BCM5721/BCM5750 fixes to work with IPMI 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, 01 Jan 2006 11:50:50 -0000 Doug Ambrisko wrote: > Here are some first pass patches to make the bge driver not break IPMI. > This was tested on a Dell PE850: > bge0: mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci4 > miibus1: on bge0 > brgphy0: on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > > It shouldn't break other bge cards and it might work with other Broadcom > IPMI capable chips (they seem to have different usages). Please let me know > how this goes. > > I gleaned this info. from the Linux drivers. YMMV. I tried applying the patches on todays current (amd64) but there have been a lot of changes in this driver lately so I had to apply one hunk by hand. With a BCM5704 chip (Supermicro H8SSL-i) the box hangs solid after setting hostname. With a BCM5721 chip (Supermicro P8SCi) i get "RX CPU Self diagnosis failed" and no ethernet interfaces at all. Do you have an updated/working patch set? Regards, Martin From owner-freebsd-net@FreeBSD.ORG Sun Jan 1 12:22:12 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18A6A16A41F; Sun, 1 Jan 2006 12:22:12 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 867B643D5D; Sun, 1 Jan 2006 12:22:11 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id BFB684CD43; Sun, 1 Jan 2006 12:22:29 +0000 (GMT) Received: from [192.168.0.2] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 9C90F4C8E8; Sun, 1 Jan 2006 12:22:28 +0000 (GMT) Message-ID: <43B7C974.7070803@roq.com> Date: Sun, 01 Jan 2006 23:22:12 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <43B45EEF.6060800@x-trader.de> <43B47CB5.3C0F1632@freebsd.org> In-Reply-To: <43B47CB5.3C0F1632@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-net@freebsd.org Subject: Re: Routing SMP benefit 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, 01 Jan 2006 12:22:12 -0000 Andre Oppermann wrote: >Markus Oestreicher wrote: > > >>Currently running a few routers on 5-STABLE I have read the >>recent changes in the network stack with interest. >> >> > >You should run 6.0R. It contains many improvements over 5-STABLE. > > > >>A few questions come to my mind: >> >>- Can a machine that mainly routes packets between two em(4) >>interfaces benefit from a second CPU and SMP kernel? Can both >>CPUs process packets from the same interface in parallel? >> >> > >My testing has shown that a machine can benefit from it but not >much in the forwarding performance. The main benefit is the >prevention of lifelock if you have very high packet loads. The >second CPU on SMP keeps on doing all userland tasks and running >routing protocols. Otherwise your BGP sessions or OSPF hellos >would stop and remove you from the routing cloud. > > > >>- From reading the lists it appears that net.isr.direct >>and net.ip.fastforwarding are doing similar things. Should >>they be used together or rather not? >> >> > >net.inet.ip.fastforwarding has precedence over net.isr.direct and >enabling both at the same doesn't gain you anything. Fastforwarding >is about 30% faster than all other methods available, including >polling. On my test machine with two em(4) and an AMD Opteron 852 >(2.6GHz) I can route 580'000 pps with zero packet loss on -CURRENT. >An upcoming optimization that will go into -CURRENT in the next >few days pushes that to 714'000 pps. Futher optimizations are >underway to make a stock kernel do close to or above 1'000'000 pps >on the same hardware. > > I have tested on 6R with fastforwarding and net.isr.direct and found that by them selves they don't compare in network performance boosts compared to enabling polling, but you have made me feel like retesting, this is on 6R or stable though. When do you think some of these new network improvements in -current will go into 6-stable? Regards, Mike From owner-freebsd-net@FreeBSD.ORG Sun Jan 1 12:34:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CFEA16A41F for ; Sun, 1 Jan 2006 12:34:04 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4DA143D5C for ; Sun, 1 Jan 2006 12:34:03 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id A9F694CF4C; Sun, 1 Jan 2006 12:34:21 +0000 (GMT) Received: from [192.168.0.2] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id C5F6B4CF46; Sun, 1 Jan 2006 12:34:20 +0000 (GMT) Message-ID: <43B7CC3C.4080606@roq.com> Date: Sun, 01 Jan 2006 23:34:04 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Zongsheng Zhang References: <43B11DF3.8070501@ist.osaka-u.ac.jp> In-Reply-To: <43B11DF3.8070501@ist.osaka-u.ac.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-net@freebsd.org Subject: Re: tcp performance 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, 01 Jan 2006 12:34:04 -0000 Zongsheng Zhang wrote: >Hi, *, > >For testing throughput of a TCP connection, the following topology is used: > Host-A ---GB Ethernet--- Dummynet ---GB Ethernet--- Host-B > >Host-A/B use FreeBSD v6.0. Sysctl parameters of Host-A/B are: >kern.ipc.nmbclusters=32768 >net.inet.tcp.inflight.enable=0 >net.inet.tcp.sendspace=2097152 # 2M >net.inet.tcp.recvspace=2097152 # 2M > >When RTT in Dummynet is set to 0ms, the throughput (A--B) is about >900Mbps. The buffer size is enough to fill a link bandwidth=800Mbps, and >RTT=20ms. However, if RTT is set to 20ms, the throughput is only about >500Mbps. > >Are there other parameters which are necessary to adjust? Does anyone >have suggestion for high throughput? > >Thanks in advance. > > > What are you following on your hosts? Release/stable or current? I only use just release or stable. For your middle router try net.inet.ip.fastforwarding or net.isr.direct but not at the same time, then try on top enabling polling. Personally I found enabling polling worked best combined with net.inet.ip.fastforwarding. Andre Oppermann claimed in a post just recently he gets best performance using just net.inet.ip.fastforwarding without polling but that might be for just -current, I am not sure. You could also try using current, but if I had to guess you already are? Regards, Mike From owner-freebsd-net@FreeBSD.ORG Sun Jan 1 20:24: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8990416A41F for ; Sun, 1 Jan 2006 20:24:46 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) Received: from mail.npubs.com (npubs.com [209.66.100.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3550543D48 for ; Sun, 1 Jan 2006 20:24:45 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) From: Nate Nielsen User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Candler References: <20051228143817.GA6898@uk.tiscali.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20060101204253.3976870DDA9@mail.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Sun, 1 Jan 2006 20:42:53 +0000 (GMT) Cc: freebsd-net@freebsd.org Subject: Re: IPSEC documentation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nielsen@memberwebs.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 20:24:46 -0000 Brian Candler wrote: > The IPSEC documentation at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html is > pretty weird. It suggests that you encapsulate your packets in IP-IP (gif) > encapsulation and THEN encapsulate that again using IPSEC tunnel mode. > This is a really strange approach which is almost guaranteed not to > interoperate with other IPSEC gateways. (It might be useful if you were > using etherip encapsulation and attempting to bridge two remote networks, > but that's not what it's doing either. In any case, if you're encapsulating > with a different protocol then you only need IPSEC transport mode, not > tunnel mode) That's what I've found the easiest: Encapsulation with gif tunnels and then IPSec transport mode encryption. Due to the way IPSec Tunnel mode is implemented routing protocols don't work well over it (ie: most routing protocols need an interface and next hop). > ISTM that this chapter should be rewritten to use IPSEC tunnel mode solely. > Do people here generally agree? If so I'll try to find the time to modify > it. I'd suggest adding, not replacing. Cheers, Nate From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 00:38: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38BE616A41F for ; Mon, 2 Jan 2006 00:38:45 +0000 (GMT) (envelope-from dennisolvany@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8A4D43D48 for ; Mon, 2 Jan 2006 00:38:43 +0000 (GMT) (envelope-from dennisolvany@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so1959254wra for ; Sun, 01 Jan 2006 16:38:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=GOMp0RNW2Fdk4QGv1g32uANmahz94NkoWVFVDOU8g4fLenZkRbpCuTU98pszVRjsOUi0uHMqsPiYJxEnigdPOIZhZIRfmVv3Gbs+BG+p3CQ2UQlO4PQYADvEV0TGcd93eDSJH29W7OSa807V7d/i9oR/qEdcnk9FyW92hkAfwSU= Received: by 10.54.119.11 with SMTP id r11mr532290wrc; Sun, 01 Jan 2006 16:38:43 -0800 (PST) Received: from ?195.16.87.34? ( [195.16.87.34]) by mx.gmail.com with ESMTP id 13sm24584783wrl.2006.01.01.16.38.41; Sun, 01 Jan 2006 16:38:42 -0800 (PST) Message-ID: <43B875FD.6000102@gmail.com> Date: Sun, 01 Jan 2006 18:38:21 -0600 From: Dennis Olvany User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051129) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org X-Enigmail-Version: 0.93.0.0 OpenPGP: id=D71A85AB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: route selection and ipfw forwarding 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, 02 Jan 2006 00:38:45 -0000 Let's say that I wanted to balance upstream traffic across four WAN links to the same ISP and default gateway using IPFW probabilities. Can the FreeBSD routing table contain multiple routes to the same destination? How would a route be selected and could such a selection be influenced by IPFW? From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 02:09:27 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F2F116A41F for ; Mon, 2 Jan 2006 02:09:27 +0000 (GMT) (envelope-from orac000@internet-mail.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2482A43D48 for ; Mon, 2 Jan 2006 02:09:27 +0000 (GMT) (envelope-from orac000@internet-mail.org) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 379FCD2F099 for ; Sun, 1 Jan 2006 21:09:25 -0500 (EST) Received: from web3.messagingengine.com ([10.202.2.212]) by frontend1.internal (MEProxy); Sun, 01 Jan 2006 21:09:25 -0500 Received: by web3.messagingengine.com (Postfix, from userid 99) id 77A1115316; Sun, 1 Jan 2006 21:09:26 -0500 (EST) Message-Id: <1136167766.17477.250884723@webmail.messagingengine.com> X-Sasl-Enc: chHlo/SuDKzmDtdat/C7XsDn/4zTtTT2EckPls+wTDK+ 1136167766 From: "Aluminium Oxide" To: freebsd-net@freebsd.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Mon, 02 Jan 2006 12:39:26 +1030 Subject: /usr/src/lib/libc/net/res_debug.c: compile problem fixed 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, 02 Jan 2006 02:09:27 -0000 I've fixed a problem with res_debug.c, which, during a make buildworld on a 6.0 RELEASE i386 system cvsupped yesterday, was stopping with these errors : ============================================================ ..... In file included from /usr/src/lib/libc/net/res_debug.c:733: /usr/src/lib/libc/net/res_debug.c: in function '__loc_aton' : /usr/src/lib/libc/net/res_debug.c:733: warning: passing arg 1 of 'latlon2ul' from incompatible pointer type /usr/src/lib/libc/net/res_debug.c:735: warning: passing arg 1 of 'latlon2ul' from incompatible pointer type /usr/src/lib/libc/net/res_debug.c:786: warning: passing arg 1 of 'latlon2ul' from incompatible pointer type /usr/src/lib/libc/net/res_debug.c:797: warning: passing arg 1 of 'latlon2ul' from incompatible pointer type /usr/src/lib/libc/net/res_debug.c:808: warning: passing arg 1 of 'latlon2ul' from incompatible pointer type *** Error code 1 Stop in /usr/src/lib/libc/ ...... Stop in /usr/src. ============================================================ I have fixed this and would like to either create a patch for the code in question, or if you prefer simply replacing the code (26Kb) with the attached code. Either way, I am not the most experienced C programmer and would like my changes checked. Below is the output of `diff res_debug.org.c res_debug.c` I've also attached this. ===================================================== 574,575c574,575 < precsize_aton(strptr) < char **strptr; --- > precsize_aton(char **strptr) > /* char **strptr; */ 616,618c616,618 < latlon2ul(latlonstrptr,which) < char **latlonstrptr; < int *which; --- > latlon2ul(char *latlonstrptr,int *which) > /* char **latlonstrptr; */ > /* int *which; */ 624c624 < cp = *latlonstrptr; --- > cp = latlonstrptr; 707c707 < *latlonstrptr = cp; --- > latlonstrptr = cp; 719c719,720 < const char *cp, *maxcp; --- > char *cp; > char *maxcp; 730,731c731,732 < cp = ascii; < maxcp = cp + strlen(ascii); --- > *cp = *ascii; > *maxcp = *cp + strlen(ascii); 733c734 < lltemp1 = latlon2ul(&cp, which1); --- > lltemp1 = latlon2ul(cp, which1); 735c736 < lltemp2 = latlon2ul(&cp, which2); --- > lltemp2 = latlon2ul(cp, which2); 737c738 < switch (which1 + which2) { --- > switch (*which1 + *which2) { 739c740 < if ((which1 == 1) && (which2 == 2)) { /* normal case */ --- > if ((*which1 == 1) && (*which2 == 2)) { /* normal case */ 742c743,744 < } else if ((which1 == 2) && (which2 == 1)) { /* reversed */ --- > } else if ((*which1 == 2) && (*which2 == 1)) { /* reversed > */ ===================================================== -- Aluminium Oxide orac000@internet-mail.org -- http://www.fastmail.fm - A fast, anti-spam email service. From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 02:19:06 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7120A16A41F for ; Mon, 2 Jan 2006 02:19:06 +0000 (GMT) (envelope-from orac000@internet-mail.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D9943D49 for ; Mon, 2 Jan 2006 02:19:05 +0000 (GMT) (envelope-from orac000@internet-mail.org) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 1EDF6D2F02B for ; Sun, 1 Jan 2006 21:19:04 -0500 (EST) Received: from web3.messagingengine.com ([10.202.2.212]) by frontend1.internal (MEProxy); Sun, 01 Jan 2006 21:19:04 -0500 Received: by web3.messagingengine.com (Postfix, from userid 99) id 5C52E16D20; Sun, 1 Jan 2006 21:19:05 -0500 (EST) Message-Id: <1136168345.18174.250886155@webmail.messagingengine.com> X-Sasl-Enc: Utz7+4cjc2CdfG76eULjAO23Sv7EjBFKXzidbWZNeBgt 1136168345 From: "Aluminium Oxide" To: freebsd-net@freebsd.org Content-Transfer-Encoding: 7bit Content-Type: multipart/mixed; boundary="_----------=_1136168345181740"; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Mon, 02 Jan 2006 12:49:05 +1030 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fwd: /usr/src/lib/libc/net/res_debug.c: compile problem fixed 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, 02 Jan 2006 02:19:06 -0000 This is a multi-part message in MIME format. --_----------=_1136168345181740 Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Mon, 2 Jan 2006 02:19:05 UT Oops. Let's try that again, with the attachments this time... On Mon, 02 Jan 2006 12:39:26 +1030, "Aluminium Oxide" said: > I've fixed a problem with res_debug.c, which, during a make buildworld > on a 6.0 RELEASE i386 system cvsupped yesterday, was stopping with > these errors : > > ============================================================ > ..... > In file included from /usr/src/lib/libc/net/res_debug.c:733: > > /usr/src/lib/libc/net/res_debug.c: in function '__loc_aton' : > /usr/src/lib/libc/net/res_debug.c:733: warning: passing arg 1 of > 'latlon2ul' from incompatible pointer type > /usr/src/lib/libc/net/res_debug.c:735: warning: passing arg 1 of > 'latlon2ul' from incompatible pointer type > /usr/src/lib/libc/net/res_debug.c:786: warning: passing arg 1 of > 'latlon2ul' from incompatible pointer type > /usr/src/lib/libc/net/res_debug.c:797: warning: passing arg 1 of > 'latlon2ul' from incompatible pointer type > /usr/src/lib/libc/net/res_debug.c:808: warning: passing arg 1 of > 'latlon2ul' from incompatible pointer type > > *** Error code 1 > Stop in /usr/src/lib/libc/ > ...... > Stop in /usr/src. > ============================================================ > > I have fixed this and would like to either create a patch for the code > in question, or if you prefer simply replacing the code (26Kb) with the > attached code. Either way, I am not the most experienced C programmer > and would like my changes checked. > > Below is the output of `diff res_debug.org.c res_debug.c` > > I've also attached this. > ===================================================== > 574,575c574,575 > < precsize_aton(strptr) > < char **strptr; > --- > > precsize_aton(char **strptr) > > /* char **strptr; */ > 616,618c616,618 > < latlon2ul(latlonstrptr,which) > < char **latlonstrptr; > < int *which; > --- > > latlon2ul(char *latlonstrptr,int *which) > > /* char **latlonstrptr; */ > > /* int *which; */ > 624c624 > < cp = *latlonstrptr; > --- > > cp = latlonstrptr; > 707c707 > < *latlonstrptr = cp; > --- > > latlonstrptr = cp; > 719c719,720 > < const char *cp, *maxcp; > --- > > char *cp; > > char *maxcp; > 730,731c731,732 > < cp = ascii; > < maxcp = cp + strlen(ascii); > --- > > *cp = *ascii; > > *maxcp = *cp + strlen(ascii); > 733c734 > < lltemp1 = latlon2ul(&cp, which1); > --- > > lltemp1 = latlon2ul(cp, which1); > 735c736 > < lltemp2 = latlon2ul(&cp, which2); > --- > > lltemp2 = latlon2ul(cp, which2); > 737c738 > < switch (which1 + which2) { > --- > > switch (*which1 + *which2) { > 739c740 > < if ((which1 == 1) && (which2 == 2)) { /* normal case */ > --- > > if ((*which1 == 1) && (*which2 == 2)) { /* normal case */ > 742c743,744 > < } else if ((which1 == 2) && (which2 == 1)) { /* reversed > */ > --- > > } else if ((*which1 == 2) && (*which2 == 1)) { /* reversed > > */ > > ===================================================== ===================== Sub UNIX lumen Damien Miller orac000@internet-mail.org ===================== -- Aluminium Oxide orac000@internet-mail.org -- http://www.fastmail.fm - A fast, anti-spam email service. --_----------=_1136168345181740 Content-Disposition: attachment; filename="res_debug.c.org" Content-Transfer-Encoding: base64 Content-Type: application/octet-stream; name="res_debug.c.org" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Mon, 2 Jan 2006 02:19:05 UT --_----------=_1136168345181740 Content-Disposition: attachment; filename="res_debug.c.diff" Content-Transfer-Encoding: base64 Content-Type: text/x-patch; name="res_debug.c.diff" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Mon, 2 Jan 2006 02:19:05 UT NTc0LDU3NWM1NzQsNTc1CjwgcHJlY3NpemVfYXRvbihzdHJwdHIpCjwgCWNo YXIgKipzdHJwdHI7Ci0tLQo+IHByZWNzaXplX2F0b24oY2hhciAqKnN0cnB0 cikKPiAvKgljaGFyICoqc3RycHRyOyAqLwo2MTYsNjE4YzYxNiw2MTgKPCBs YXRsb24ydWwobGF0bG9uc3RycHRyLHdoaWNoKQo8IAljaGFyICoqbGF0bG9u c3RycHRyOyAKPCAJaW50ICp3aGljaDsgCi0tLQo+IGxhdGxvbjJ1bChjaGFy ICpsYXRsb25zdHJwdHIsaW50ICp3aGljaCkKPiAvKgljaGFyICoqbGF0bG9u c3RycHRyOyAqLwo+IC8qCWludCAqd2hpY2g7ICovCjYyNGM2MjQKPCAJY3Ag PSAqbGF0bG9uc3RycHRyOwotLS0KPiAJY3AgPSBsYXRsb25zdHJwdHI7Cjcw N2M3MDcKPCAJKmxhdGxvbnN0cnB0ciA9IGNwOwotLS0KPiAJbGF0bG9uc3Ry cHRyID0gY3A7CjcxOWM3MTksNzIwCjwgCWNvbnN0IGNoYXIgKmNwLCAqbWF4 Y3A7Ci0tLQo+IAljaGFyICpjcDsKPiAJY2hhciAqbWF4Y3A7CjczMCw3MzFj NzMxLDczMgo8IAljcCA9IGFzY2lpOwo8IAltYXhjcCA9IGNwICsgc3RybGVu KGFzY2lpKTsKLS0tCj4gCSpjcCA9ICphc2NpaTsKPiAJKm1heGNwID0gKmNw ICsgc3RybGVuKGFzY2lpKTsKNzMzYzczNAo8IAlsbHRlbXAxID0gbGF0bG9u MnVsKCZjcCwgd2hpY2gxKTsKLS0tCj4gCWxsdGVtcDEgPSBsYXRsb24ydWwo Y3AsIHdoaWNoMSk7CjczNWM3MzYKPCAJbGx0ZW1wMiA9IGxhdGxvbjJ1bCgm Y3AsIHdoaWNoMik7Ci0tLQo+IAlsbHRlbXAyID0gbGF0bG9uMnVsKGNwLCB3 aGljaDIpOwo3MzdjNzM4CjwgCXN3aXRjaCAod2hpY2gxICsgd2hpY2gyKSB7 Ci0tLQo+IAlzd2l0Y2ggKCp3aGljaDEgKyAqd2hpY2gyKSB7CjczOWM3NDAK PCAJCWlmICgod2hpY2gxID09IDEpICYmICh3aGljaDIgPT0gMikpIHsgLyog bm9ybWFsIGNhc2UgKi8KLS0tCj4gCQlpZiAoKCp3aGljaDEgPT0gMSkgJiYg KCp3aGljaDIgPT0gMikpIHsgLyogbm9ybWFsIGNhc2UgKi8KNzQyYzc0Myw3 NDQKPCAJCX0gZWxzZSBpZiAoKHdoaWNoMSA9PSAyKSAmJiAod2hpY2gyID09 IDEpKSB7IC8qIHJldmVyc2VkICovCi0tLQo+IAkJfSBlbHNlIGlmICgoKndo aWNoMSA9PSAyKSAmJiAoKndoaWNoMiA9PSAxKSkgeyAvKiByZXZlcnNlZCAK PiAqLwo= --_----------=_1136168345181740-- From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 03:38:00 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75FEF16A41F for ; Mon, 2 Jan 2006 03:38:00 +0000 (GMT) (envelope-from orac000@internet-mail.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2182843D49 for ; Mon, 2 Jan 2006 03:37:59 +0000 (GMT) (envelope-from orac000@internet-mail.org) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 23511D2E35A for ; Sun, 1 Jan 2006 22:37:58 -0500 (EST) Received: from web3.messagingengine.com ([10.202.2.212]) by frontend1.internal (MEProxy); Sun, 01 Jan 2006 22:37:58 -0500 Received: by web3.messagingengine.com (Postfix, from userid 99) id 70C4C16D3F; Sun, 1 Jan 2006 22:37:59 -0500 (EST) Message-Id: <1136173079.24299.250888676@webmail.messagingengine.com> X-Sasl-Enc: CXgdK0sCyH1n0UF5OC/0Qu62D2ino2QSOzKQyhywkjH1 1136173079 From: "Aluminium Oxide" To: freebsd-net@freebsd.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Mon, 02 Jan 2006 14:07:59 +1030 Subject: To where should I address a fix for /usr/src/lib/libc/rpc code? 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, 02 Jan 2006 03:38:00 -0000 Hi, I've been fixing code in a recently (yesterday) cvsupped i386 Release 6.0 system and would like to know where I should direct my atttention (and code) to. Thanks, Damien Miller ===================== Sub UNIX lumen orac000@internet-mail.org ===================== -- Aluminium Oxide orac000@internet-mail.org -- http://www.fastmail.fm - I mean, what is it about a decent email service? From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 10:46:06 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCFE816A41F for ; Mon, 2 Jan 2006 10:46:06 +0000 (GMT) (envelope-from linux@giboia.org) Received: from adriana.dilk.com.br (adriana.dilk.com.br [200.250.23.1]) by mx1.FreeBSD.org (Postfix) with SMTP id 1E11143D5A for ; Mon, 2 Jan 2006 10:46:04 +0000 (GMT) (envelope-from linux@giboia.org) Received: (qmail 54491 invoked by uid 98); 2 Jan 2006 10:45:29 -0000 Received: from 10.0.0.94 by lda.dilk.com.br (envelope-from , uid 82) with qmail-scanner-1.25-st-qms (uvscan: v4.4.00/v4545. perlscan: 1.25-st-qms. Clear:RC:1(10.0.0.94):. Processed in 0.028981 secs); 02 Jan 2006 10:45:29 -0000 Received: from unknown (HELO localhost) (10.0.0.94) by adriana.dilk.com.br with SMTP; 2 Jan 2006 10:45:29 -0000 Date: Mon, 2 Jan 2006 08:46:00 -0200 From: Gilberto Villani Brito To: freebsd-net@freebsd.org Message-ID: <20060102084600.12d3d12d@localhost> In-Reply-To: <20051230171045.234b4cc7.piston@otel.net> References: <20051230171045.234b4cc7.piston@otel.net> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; i586-mandrake-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: cpu?bsnmp 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, 02 Jan 2006 10:46:07 -0000 Use cacti. Gilberto On Fri, 30 Dec 2005 17:10:45 +0200 "S.I" wrote: > hi, > I want to monitor my CPU with bsnmpd but I don't want to use external (prog, script). > Any Ideas for that. > > _______________________________________________ > 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" > From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 11:02:48 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5732416A420 for ; Mon, 2 Jan 2006 11:02:48 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E751543D49 for ; Mon, 2 Jan 2006 11:02:44 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k02B2hxa037596 for ; Mon, 2 Jan 2006 11:02:43 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k02B2gaf037590 for freebsd-net@freebsd.org; Mon, 2 Jan 2006 11:02:42 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 2 Jan 2006 11:02:42 GMT Message-Id: <200601021102.k02B2gaf037590@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter 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, 02 Jan 2006 11:02:48 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations wit o [2005/11/03] kern/88450 net SYN+ACK reports strange size of window 2 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 17:51: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93F1F16A420 for ; Mon, 2 Jan 2006 17:51:42 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 214A543D58 for ; Mon, 2 Jan 2006 17:51:41 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 2267C8444C for ; Mon, 2 Jan 2006 18:51:39 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03721-04 for ; Mon, 2 Jan 2006 18:51:33 +0100 (CET) Received: from [127.0.0.1] (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id DBC2E84420 for ; Mon, 2 Jan 2006 18:51:32 +0100 (CET) Message-ID: <43B96824.20608@fsn.hu> Date: Mon, 02 Jan 2006 18:51:32 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5 (X11/20051227) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Subject: Is RFC1323 support flawed? (only with pf enabled) 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, 02 Jan 2006 17:51:42 -0000 Hello, On nearly all of my recent 6-STABLE servers, I got complaints from the users that transferring "larger" amount of data fails. For example on FTP and HTTP downloading about 500k-1M works, but after that the connection breaks. Similarly, when looking for large (a few thousand) mail folders via IMAP, the client yells that there is a problem. I got reports from Linux and Windows users. The solution is to turn RFC1323 support off on any side. What could be broken? FreeBSD? The intermediate network? Linux, Windows? Between two FreeBSD boxes, everything is OK. I use pf on all machines, if that counts... ... yes, that counts. Without pf it works OK, but when I load a simple pass only ruleset, it breaks. The strange thing is that FreeBSD-FreeBSD works with pf loaded, but FreeBSD with Windows or Linux doesn't. Any ideas? -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Adopt a directory on our free software phone: +3630 306 6758 server! http://www.fsn.hu/?f=brick From owner-freebsd-net@FreeBSD.ORG Mon Jan 2 18:24: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6861C16A41F for ; Mon, 2 Jan 2006 18:24:41 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id DDFCB43D49 for ; Mon, 2 Jan 2006 18:24:40 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 23928 invoked from network); 2 Jan 2006 18:24:39 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 2 Jan 2006 18:24:39 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 2 Jan 2006 12:24:38 -0600 (CST) From: Mike Silbersack To: Attila Nagy In-Reply-To: <43B96824.20608@fsn.hu> Message-ID: <20060102122339.V1498@odysseus.silby.com> References: <43B96824.20608@fsn.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Is RFC1323 support flawed? (only with pf enabled) 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, 02 Jan 2006 18:24:41 -0000 On Mon, 2 Jan 2006, Attila Nagy wrote: > I use pf on all machines, if that counts... > ... yes, that counts. Without pf it works OK, but when I load a simple pass > only ruleset, it breaks. Someone else reported this problem a few weeks ago, he said that it occurs when hz is set > 1000. Do you have a weird hz setting on your machines? Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 00:35: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AD5D16A41F; Tue, 3 Jan 2006 00:35:42 +0000 (GMT) (envelope-from lbromirski@mr0vka.eu.org) Received: from r2d2.bromirski.net (r2d2.bromirski.net [217.153.57.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87E5C43D49; Tue, 3 Jan 2006 00:35:41 +0000 (GMT) (envelope-from lbromirski@mr0vka.eu.org) Received: from [192.168.0.10] (shield.wesola.pl [62.111.150.246]) by r2d2.bromirski.net (Postfix) with ESMTP id 69EA31089D9; Tue, 3 Jan 2006 01:42:22 +0100 (CET) Message-ID: <43B9C7CC.7090703@mr0vka.eu.org> Date: Tue, 03 Jan 2006 01:39:40 +0100 From: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= User-Agent: Thunderbird 1.5 (Windows/20051206) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-pf@freebsd.org Subject: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 00:35:42 -0000 Hi, Following some short discussion on freebsd-pf I've written (mostly copied, but let's skip that for a moment) short patch for ip_input.c, that does uRPF check for incoming packets. In some simple words, it's exactly the function ipfw2 is calling when You specify a rule with `versrcreach', but it's there in core network processing path and it's controlled via sysctl, so You don't need any packet filter in system to get the job done. If sysctl net.inet.ip.urpf is set to 0 check is disabled, and if it's set to 1, checking of source address/interface against routing table is in effect. Checks will skip packets coming on from loopback or CARP interfaces. When the packet is going to be dropped, there's syslog message generated with source IP address and input interface it came on, and system counters are increased. Patch applies cleanly on ip_input.c version 1.301.2.3 dated 2005/10/09 (latest RELENG_5 checkout). It will also work with latest RELENG_4 checkout (ip_input.c version 1.130.2.55 dated 2005/01/02). Please note however, this code is for IPv4 only. http://lukasz.bromirski.net/projekty/freebsd/ip_input.urpf.diff SHA1 (ip_input.urpf.diff) = c76319f619a43f1d031e729d361324d3a4d86daf Please also note, there's already similar sysctl in ip_input.c - it's named ip_checkinterface and does subset of urpf checks, so while I don't think this patch is going to make into source tree, maybe it's time for someone wiser than me to review the code and 'update' ip_input.c code? -- this space was intentionally left blank | Łukasz Bromirski you can insert your favourite quote here | lukasz:bromirski,net From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 00:53: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C2BD16A41F; Tue, 3 Jan 2006 00:53:07 +0000 (GMT) (envelope-from lbromirski@mr0vka.eu.org) Received: from r2d2.bromirski.net (r2d2.bromirski.net [217.153.57.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 768B443D5F; Tue, 3 Jan 2006 00:53:06 +0000 (GMT) (envelope-from lbromirski@mr0vka.eu.org) Received: from [192.168.0.10] (shield.wesola.pl [62.111.150.246]) by r2d2.bromirski.net (Postfix) with ESMTP id 3FCAF1089C3; Tue, 3 Jan 2006 01:59:48 +0100 (CET) Message-ID: <43B9CBA4.4070303@mr0vka.eu.org> Date: Tue, 03 Jan 2006 01:56:04 +0100 From: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= User-Agent: Thunderbird 1.5 (Windows/20051206) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <43B9C7CC.7090703@mr0vka.eu.org> In-Reply-To: <43B9C7CC.7090703@mr0vka.eu.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-pf@freebsd.org Subject: Re: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 00:53:07 -0000 Łukasz Bromirski wrote: > Patch applies cleanly on ip_input.c version 1.301.2.3 dated 2005/10/09 > (latest RELENG_5 checkout). It will also work with latest RELENG_4 > checkout (ip_input.c version 1.130.2.55 dated 2005/01/02). Sorry for small mistake - patch applies cleanly to: ip_input.c v1.301.2.3 z 2005/10/09 (RELENG_6) ip_input.c v1.283.2.14 2005/07/20 (RELENG_5) ip_input.c v1.130.2.55 z 2005/01/02 (RELENG_4) -- this space was intentionally left blank | Łukasz Bromirski you can insert your favourite quote here | lukasz:bromirski,net From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 04:06:22 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5480E16A41F for ; Tue, 3 Jan 2006 04:06:22 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E97D043D5C for ; Tue, 3 Jan 2006 04:06:21 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id k03468RF005849; Mon, 2 Jan 2006 20:06:13 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200601030406.k03468RF005849@gw.catspoiler.org> Date: Mon, 2 Jan 2006 20:06:08 -0800 (PST) From: Don Lewis To: ambrisko@ambrisko.com In-Reply-To: <200512011757.jB1HvwP3009101@ambrisko.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-net@FreeBSD.org, priarifire@yahoo.com Subject: Re: Configure wireless connection using Cisco aironet 350 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, 03 Jan 2006 04:06:22 -0000 On 1 Dec, Doug Ambrisko wrote: > Imrani writes: > [ Charset ISO-8859-1 unsupported, converting... ] > | Hi, > | > | I am trying to configure Cisco Aironet 350 wireless PCI card but I > | get an error which I am unable to find much details for that. Following > | is description of ifconfing: > | > | > ifconfig an0 > | an0: flags=8843 mtu 1500 > | inet6 fe80::209:7cff:fe22:6eab%an0 prefixlen 64 scopeid 0x2 > | ether 00:09:7c:22:6e:ab > | media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > | status: associated > | ssid 1:myhome channel 9 > | stationname FreeBSD > | ano: record length mismatch -- expected 194, got 196 for Rid ff10 > | authmode OPEN privacy ON deftxkey 2 txpowmax 0 rtsthreshold 0 > | fragthreshold 0 roaming DEVICE > | > | > | As you can see the wireless card is detected and status is "associated' > | but my wireless connection doesn't work. I cannot even ping the router. > | > | Can you please help me configure wireless connection with my router. > | > | Also, here are more details: > | > | WEP on, encryption is 128 bits, BSD 6.0, PCI card is Cisco Aironet 350, > | AMD athalon. > > > Is this mini-PCI. If so down-rev the firmware. I got it working better > with newer version of mini-PCI but ran into problem in which checking > on status while sending data could wedge the card. Doing a kldunload/kldload > fixes it but my reset attempts methods didn't :-( I also have the > HW MIC support added but not the SW bits. I been derailed on too many > other FreeBSD problems to make much progress. I have lots of things > that need polish before they can be commited but don't have the time to > do that :-( The biggest thing is an OpenIPMI compatable IPMI driver > so ipmitool etc. can talk via the motherboard interface. Same problem here with firmware V5b00.08. What's a good revision to try? From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 06:30: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6D2316A42F for ; Tue, 3 Jan 2006 06:30:26 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36DB143D49 for ; Tue, 3 Jan 2006 06:30:25 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 2173B8444F; Tue, 3 Jan 2006 07:30:24 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01400-04; Tue, 3 Jan 2006 07:30:18 +0100 (CET) Received: from [172.16.164.1] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 4E11A8441E; Tue, 3 Jan 2006 07:30:18 +0100 (CET) Message-ID: <43BA19EA.6010407@fsn.hu> Date: Tue, 03 Jan 2006 07:30:02 +0100 From: Attila Nagy User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <43B96824.20608@fsn.hu> <20060102122339.V1498@odysseus.silby.com> In-Reply-To: <20060102122339.V1498@odysseus.silby.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-net@freebsd.org Subject: Re: Is RFC1323 support flawed? (only with pf enabled) 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, 03 Jan 2006 06:30:27 -0000 Hello, >> I use pf on all machines, if that counts... >> ... yes, that counts. Without pf it works OK, but when I load a simple >> pass only ruleset, it breaks. > Someone else reported this problem a few weeks ago, he said that it > occurs when hz is set > 1000. Do you have a weird hz setting on your > machines? No: sysctl kern.clockrate kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 } It is a stripped down GENERIC kernel, with some debugging options left in (KDB, MP_WATCHDOG, etc). -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 ISOs: http://www.fsn.hu/?f=download From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 08:46:00 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5553B16A41F for ; Tue, 3 Jan 2006 08:46:00 +0000 (GMT) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (insomnia.benzedrine.cx [62.65.145.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 137BE43D60 for ; Tue, 3 Jan 2006 08:45:57 +0000 (GMT) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (dhartmei@localhost [127.0.0.1]) by insomnia.benzedrine.cx (8.13.4/8.12.11) with ESMTP id k038jrAZ015434 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 3 Jan 2006 09:45:54 +0100 (MET) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.13.4/8.12.10/Submit) id k038jqZB028105; Tue, 3 Jan 2006 09:45:53 +0100 (MET) Date: Tue, 3 Jan 2006 09:45:51 +0100 From: Daniel Hartmeier To: Attila Nagy Message-ID: <20060103084551.GF17829@insomnia.benzedrine.cx> References: <43B96824.20608@fsn.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43B96824.20608@fsn.hu> User-Agent: Mutt/1.5.10i Cc: freebsd-net@freebsd.org Subject: Re: Is RFC1323 support flawed? (only with pf enabled) 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, 03 Jan 2006 08:46:00 -0000 On Mon, Jan 02, 2006 at 06:51:32PM +0100, Attila Nagy wrote: > Any ideas? RFC1323 support includes TCP window scaling (wscale), which affects pf stateful filtering. There have been bugs with that in the past, but the code in 6.x should contain all fixes for them. Maybe you found a new one. When you say "a simple pass only ruleset", do you mean a ruleset consisting of a single "pass all" rule (i.e. not creating state), or one that includes "pass keep state" (and possibly "scrub") rules? If the latter, there's one possible user mistake that could result in the effects you're seeing. If you filter statefully, but create state not on the initial SYN packet of each TCP connection, but a subsequent one, pf doesn't note the relevant wscale factors (seen only during the first two packets of the handshake), which can have precisely this effect, stalling connections after a while (when one peer starts to actually use large windows, making use of its negotiated wscale factor). It's also possible that this would occur more often with specific OS peers, as the OS (and TCP settings, like receive buffer size) influence the wscale factors being used. To rule this out, make sure you either don't create state at all, or create state on the first SYN when you do (look for any "pass" rules which don't also include "keep state"). pfctl -vss prints the wscale factors being honoured by pf for each state. If that's not it, can you enable pf debug logging (pfctl -xm), note pfctl -si output, then reproduce a failing connection, then run pfctl -si again, compare the output (looking for any counters increasing the obvious ones), and checking /var/log/messages for any lines from pf? Daniel From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 09:08: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D3EE16A41F for ; Tue, 3 Jan 2006 09:08:31 +0000 (GMT) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (insomnia.benzedrine.cx [62.65.145.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63C0643D49 for ; Tue, 3 Jan 2006 09:08:30 +0000 (GMT) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (dhartmei@localhost [127.0.0.1]) by insomnia.benzedrine.cx (8.13.4/8.12.11) with ESMTP id k0398S1P009411 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 3 Jan 2006 10:08:29 +0100 (MET) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.13.4/8.12.10/Submit) id k0398SZX032616; Tue, 3 Jan 2006 10:08:28 +0100 (MET) Date: Tue, 3 Jan 2006 10:08:28 +0100 From: Daniel Hartmeier To: Attila Nagy Message-ID: <20060103090828.GG17829@insomnia.benzedrine.cx> References: <43B96824.20608@fsn.hu> <20060103084551.GF17829@insomnia.benzedrine.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060103084551.GF17829@insomnia.benzedrine.cx> User-Agent: Mutt/1.5.10i Cc: freebsd-net@freebsd.org Subject: Re: Is RFC1323 support flawed? (only with pf enabled) 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, 03 Jan 2006 09:08:31 -0000 On Tue, Jan 03, 2006 at 09:45:51AM +0100, Daniel Hartmeier wrote: > To rule this out, make sure you either don't create state at all, or > create state on the first SYN when you do (look for any "pass" rules > which don't also include "keep state"). pfctl -vss prints the wscale > factors being honoured by pf for each state. Also note that there is an implicit (invisible) "pass" rule (without "keep state") at the bottom of every ruleset, matching when no rule matches at all. For instance, the following ruleset would show the problem: pass in all keep state Say, the machine has two interfaces and is IP forwarding a connection going through both (incoming on one, outgoing through the other). pf filters each packet on both interfaces (in on the first and out on the second, in on the second and out on the first). In this case, the initial SYN would come in on the first interface, match your explicit rule, and create state on the first interface. This state does NOT cover the packets flowing (in reverse direction) on the other interface, pf evaluates the ruleset again when the initial SYN leaves the second interface. Now the explicit rule does not match (the direction is out, not in), but the packet passes due to the implicit "pass" rule at the end (not creating state). Then the SYN+ACK comes back in through the second interface, doesn't match a state, causes ruleset evaluation, matches your explicit rule, and creates state. Now this state is created based on the SYN+ACK, and hasn't seen the initial SYN, hence pf doesn't properly track wscale factors in this state, and will/might stall the connection eventually. Make sure the implicit "pass" rule is never used, by adding an explicit rule matching everything (the default policy, either blocking everything or passing everything with "keep state") at the top of your ruleset. Daniel From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 10:09: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2D4416A41F for ; Tue, 3 Jan 2006 10:09:49 +0000 (GMT) (envelope-from zhang@ist.osaka-u.ac.jp) Received: from terra.ane.cmc.osaka-u.ac.jp (terra.ane.cmc.osaka-u.ac.jp [133.1.74.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B39243D78 for ; Tue, 3 Jan 2006 10:09:46 +0000 (GMT) (envelope-from zhang@ist.osaka-u.ac.jp) Received: from [192.168.1.75] (muse.ane.cmc.osaka-u.ac.jp [133.1.74.180]) (authenticated bits=0) by terra.ane.cmc.osaka-u.ac.jp (8.12.10/8.12.10) with ESMTP id k03A9hsN014992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Jan 2006 19:09:44 +0900 Message-ID: <43BA4D6F.6060706@ist.osaka-u.ac.jp> Date: Tue, 03 Jan 2006 19:09:51 +0900 From: Zongsheng Zhang User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <43B11DF3.8070501@ist.osaka-u.ac.jp> <43B7CC3C.4080606@roq.com> In-Reply-To: <43B7CC3C.4080606@roq.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: tcp performance 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, 03 Jan 2006 10:09:50 -0000 I have confirmed that there is no problem with settings of Dummynet. When Host-A/B uses Linux, the throughput of RTT=20ms (using Iperf) is same as that of RTT=0ms. Host-A/B use FreeBSD v6.0 release. Does anyone have experience/suggestion for achieving high throughput with FreeBSD? Michael Vince wrote: > Zongsheng Zhang wrote: > >> Hi, *, >> >> For testing throughput of a TCP connection, the following topology is >> used: >> Host-A ---GB Ethernet--- Dummynet ---GB Ethernet--- Host-B >> >> Host-A/B use FreeBSD v6.0. Sysctl parameters of Host-A/B are: >> kern.ipc.nmbclusters=32768 >> net.inet.tcp.inflight.enable=0 >> net.inet.tcp.sendspace=2097152 # 2M >> net.inet.tcp.recvspace=2097152 # 2M >> >> When RTT in Dummynet is set to 0ms, the throughput (A--B) is about >> 900Mbps. The buffer size is enough to fill a link bandwidth=800Mbps, and >> RTT=20ms. However, if RTT is set to 20ms, the throughput is only about >> 500Mbps. >> >> Are there other parameters which are necessary to adjust? Does anyone >> have suggestion for high throughput? >> >> Thanks in advance. >> >> >> > What are you following on your hosts? Release/stable or current? I only > use just release or stable. > > For your middle router try net.inet.ip.fastforwarding or net.isr.direct > but not at the same time, then try on top enabling polling. > Personally I found enabling polling worked best combined with > net.inet.ip.fastforwarding. > > Andre Oppermann claimed in a post just recently he gets best performance > using just net.inet.ip.fastforwarding without polling but that might be > for just -current, I am not sure. > > You could also try using current, but if I had to guess you already are? > > Regards, > Mike > > -- Zongsheng Zhang zhang@ist.osaka-u.ac.jp From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 10:38: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82C5116A420 for ; Tue, 3 Jan 2006 10:38:58 +0000 (GMT) (envelope-from budiyt@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20D2643D45 for ; Tue, 3 Jan 2006 10:38:58 +0000 (GMT) (envelope-from budiyt@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so2492288nzo for ; Tue, 03 Jan 2006 02:38:56 -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=sE1dUX++Kh4DF8LEKnzrzldFbyctzHLKFDAkPjtuYyq+daNVAevRNs33iCTDqioSm4aL7M5VhNE82aqmmv4+0Y1Ah1VhPKsfc78Mh9xpGhGKp7vlY3Cg1DctDYh346WiQiSLkRzfk2mI332gI7tmSyWQqStSkLpryNlr7JU5zfI= Received: by 10.36.84.18 with SMTP id h18mr3313147nzb; Tue, 03 Jan 2006 02:38:56 -0800 (PST) Received: by 10.36.90.5 with HTTP; Tue, 3 Jan 2006 02:38:56 -0800 (PST) Message-ID: <4d4dc3640601030238r2faf55bua234869c396b76f6@mail.gmail.com> Date: Tue, 3 Jan 2006 17:38:56 +0700 From: budsz To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Need help WFQ 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, 03 Jan 2006 10:38:58 -0000 Hi, I hope you give me some advice or explaination about Dummynet. I've googling/experiment for three a month to get the right answer how to use WF2Q+ with Dummynet. I've a small internet cafe and after 4 years using FreeBSD+Dummynet with hardlink limiting policy. Here for WF2Q+ implementation in my internet cafe: In /etc/rc.firewall look like: # IP Address variable ip_cl_01=3D"192.168.0.1/32" ip_cl_10=3D"192.168.0.10/32" ip_cl_11=3D"192.168.0.11/32" ip_cl_12=3D"192.168.0.12/32" ip_cl_13=3D"192.168.0.13/32" ip_cl_14=3D"192.168.0.14/32" ip_cl_50=3D"192.168.0.50/32" # Bandwidth variable bw_share=3D"152Kbit/s" ${fwcmd} add 104 queue 1 ip from ${ip_cl_01} to any via ${eth_1} ${fwcmd} add 105 queue 1 ip from any to ${ip_cl_01} via ${eth_1} ${fwcmd} add 106 queue 2 ip from ${ip_cl_10} to any via ${eth_1} ${fwcmd} add 107 queue 2 ip from any to ${ip_cl_10} via ${eth_1} ${fwcmd} add 108 queue 3 ip from ${ip_cl_11} to any via ${eth_1} ${fwcmd} add 109 queue 3 ip from any to ${ip_cl_11} via ${eth_1} ${fwcmd} add 110 queue 4 ip from ${ip_cl_12} to any via ${eth_1} ${fwcmd} add 111 queue 4 ip from any to ${ip_cl_12} via ${eth_1} ${fwcmd} add 112 queue 5 ip from ${ip_cl_13} to any via ${eth_1} ${fwcmd} add 113 queue 5 ip from any to ${ip_cl_13} via ${eth_1} ${fwcmd} add 114 queue 6 ip from ${ip_cl_14} to any via ${eth_1} ${fwcmd} add 115 queue 6 ip from any to ${ip_cl_14} via ${eth_1} ${fwcmd} add 116 queue 7 ip from ${ip_cl_50} to any via ${eth_1} ${fwcmd} add 117 queue 7 ip from any to ${ip_cl_50} via ${eth_1} ${fwcmd} queue 1 config pipe 3 weight 3 mask all ${fwcmd} queue 2 config pipe 3 weight 3 mask all ${fwcmd} queue 3 config pipe 3 weight 3 mask all ${fwcmd} queue 4 config pipe 3 weight 3 mask all ${fwcmd} queue 5 config pipe 3 weight 3 mask all ${fwcmd} queue 6 config pipe 3 weight 3 mask all ${fwcmd} queue 7 config pipe 3 weight 1 mask all ${fwcmd} pipe 3 config bw ${bw_share} With that rule I want to limit every client (IN/OUT) with ratio: for ex: client-01 =3D> 3/19 * 152 Kbit/s =3D 24 Kbit/s client-10 =3D> 3/19 * 153 Kbit/s =3D 24 Kbit/s etc.. I assume all of my client already active using internet. But sometime "client-11" always get 100 Kbit/s. Does my rule is OK? if not, would you give me example the right rule for this situation, of couse with clarification (step by step). FYI, I use FreeBSD 4.10-RELEASE & FreeBSD 4.11-STABLE. Thanks You. -- budsz From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 11:52:17 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ED2216A41F; Tue, 3 Jan 2006 11:52:17 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: from a.6f2.net (a.6f2.net [213.189.5.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6460F43D45; Tue, 3 Jan 2006 11:52:10 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: by a.6f2.net (Postfix, from userid 66) id EDEC7BF8D4E; Tue, 3 Jan 2006 12:52:08 +0100 (CET) Received: by cc.bashibuzuk.net (Postfix, from userid 1001) id EF538BEC0; Tue, 3 Jan 2006 12:51:20 +0100 (CET) Date: Tue, 3 Jan 2006 12:51:20 +0100 From: Yann Berthier To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Message-ID: <20060103115120.GG840@bashibuzuk.net> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org References: <43B9C7CC.7090703@mr0vka.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43B9C7CC.7090703@mr0vka.eu.org> X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.11 Cc: Subject: Re: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 11:52:17 -0000 Hello, On Tue, 03 Jan 2006, at 01:39, ?ukasz Bromirski wrote: > Hi, > > Following some short discussion on freebsd-pf I've written (mostly > copied, but let's skip that for a moment) short patch for ip_input.c, > that does uRPF check for incoming packets. > > In some simple words, it's exactly the function ipfw2 is calling when > You specify a rule with `versrcreach', but it's there in core > network processing path and it's controlled via sysctl, so You don't > need any packet filter in system to get the job done. > > If sysctl net.inet.ip.urpf is set to 0 check is disabled, and if > it's set to 1, checking of source address/interface against routing > table is in effect. Checks will skip packets coming on from > loopback or CARP interfaces. > > When the packet is going to be dropped, there's syslog message > generated with source IP address and input interface it came on, > and system counters are increased. > > Patch applies cleanly on ip_input.c version 1.301.2.3 dated 2005/10/09 > (latest RELENG_5 checkout). It will also work with latest RELENG_4 > checkout (ip_input.c version 1.130.2.55 dated 2005/01/02). > > Please note however, this code is for IPv4 only. > > http://lukasz.bromirski.net/projekty/freebsd/ip_input.urpf.diff > SHA1 (ip_input.urpf.diff) = c76319f619a43f1d031e729d361324d3a4d86daf Nice ! > Please also note, there's already similar sysctl in ip_input.c - > it's named ip_checkinterface and does subset of urpf checks, so > while I don't think this patch is going to make into source tree, > maybe it's time for someone wiser than me to review the code and > 'update' ip_input.c code? If this yet to be found wiser guy would not forget the loose check too (verrevpath in ipfw speaking), where packets matching the default route are ok ... :) Cheers, - yann From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 12:45: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4D7416A41F for ; Tue, 3 Jan 2006 12:45:45 +0000 (GMT) (envelope-from jon.otterholm@ide.resurscentrum.se) Received: from mail1.cil.se (mail1.cil.se [217.197.56.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18EBF43D4C for ; Tue, 3 Jan 2006 12:45:44 +0000 (GMT) (envelope-from jon.otterholm@ide.resurscentrum.se) Received: from [192.168.2.10] ([192.168.2.10]) by mail1.cil.se with Microsoft SMTPSVC(6.0.3790.0); Tue, 3 Jan 2006 13:45:42 +0100 Message-ID: <43BA71F6.2080305@ide.resurscentrum.se> Date: Tue, 03 Jan 2006 13:45:42 +0100 From: Jon Otterholm User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051210) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Jan 2006 12:45:42.0192 (UTC) FILETIME=[9B6AEB00:01C61063] Subject: Router + ADM64 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, 03 Jan 2006 12:45:45 -0000 Hi! What is there to gain in performance choosing AMD64 on a Dell PE1850 (Xeon EMT64) when used as router? /Jon From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 13:58:28 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4D8C16A420; Tue, 3 Jan 2006 13:58:28 +0000 (GMT) (envelope-from lukasz@bromirski.net) Received: from r2d2.bromirski.net (r2d2.bromirski.net [217.153.57.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5860B43D64; Tue, 3 Jan 2006 13:58:23 +0000 (GMT) (envelope-from lukasz@bromirski.net) Received: from [127.0.0.1] (r2d2.bromirski.net [217.153.57.194]) by r2d2.bromirski.net (Postfix) with ESMTP id D11251089C8; Tue, 3 Jan 2006 15:05:17 +0100 (CET) Message-ID: <43BA82F7.7070408@bromirski.net> Date: Tue, 03 Jan 2006 14:58:15 +0100 From: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= User-Agent: Thunderbird 1.5 (Windows/20051207) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org References: <43B9C7CC.7090703@mr0vka.eu.org> <20060103115120.GG840@bashibuzuk.net> In-Reply-To: <20060103115120.GG840@bashibuzuk.net> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 13:58:28 -0000 Yann Berthier wrote: > If this yet to be found wiser guy would not forget the loose check > too (verrevpath in ipfw speaking), where packets matching the default > route are ok ... :) Actually it does that and will until we'll have option to have two or more default routes. Presently, if packets comes via interface and reply for it should be sent on the same interface (because default route points to it and there are no other routes pointing for the same destination to another interface) it will work. Check fails if there's either interface mismatch, or source is present in routing table but marked as RTF_REJECT/BLACKHOLE one. OpenBSD imported KAME mroute extension that enables them to have more than one route for given destination simultaneously in routing table. I'm looking into it now, as it's very attractive thing, however as Andre is doing rework of network code I'm sure we'll have it sooner or later and then maybe someone will revise old checks already marked as 'XXX' in the code ;) -- this space was intentionally left blank | Łukasz Bromirski you can insert your favourite quote here | lukasz:bromirski,net From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 14:32:10 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98CFE16A41F; Tue, 3 Jan 2006 14:32:10 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: from a.6f2.net (a.6f2.net [213.189.5.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35AF343D5A; Tue, 3 Jan 2006 14:32:10 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: by a.6f2.net (Postfix, from userid 66) id D4CFBBF8D34; Tue, 3 Jan 2006 15:32:08 +0100 (CET) Received: by cc.bashibuzuk.net (Postfix, from userid 1001) id 63FE9BEC0; Tue, 3 Jan 2006 15:31:16 +0100 (CET) Date: Tue, 3 Jan 2006 15:31:16 +0100 From: Yann Berthier To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Message-ID: <20060103143116.GH840@bashibuzuk.net> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org References: <43B9C7CC.7090703@mr0vka.eu.org> <20060103115120.GG840@bashibuzuk.net> <43BA82F7.7070408@bromirski.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43BA82F7.7070408@bromirski.net> X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.11 Cc: Subject: Re: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 14:32:10 -0000 On Tue, 03 Jan 2006, at 14:58, ?ukasz Bromirski wrote: > Yann Berthier wrote: > > > If this yet to be found wiser guy would not forget the loose check > > too (verrevpath in ipfw speaking), where packets matching the default > > route are ok ... :) > > Actually it does that and will until we'll have option to have two > or more default routes. > > Presently, if packets comes via interface and reply for it should be > sent on the same interface (because default route points to it and > there are no other routes pointing for the same destination to > another interface) it will work. > > Check fails if there's either interface mismatch, or source is present > in routing table but marked as RTF_REJECT/BLACKHOLE one. My bad, i didn't looked at your patch, I was misleaded by the verrevpath / versrcreach description. > OpenBSD imported KAME mroute extension that enables them to have > more than one route for given destination simultaneously in routing > table. I'm looking into it now, as it's very attractive thing, > however as Andre is doing rework of network code I'm sure we'll have > it sooner or later and then maybe someone will revise old checks > already marked as 'XXX' in the code ;) Amen - yann From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 15:29:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B517C16A41F for ; Tue, 3 Jan 2006 15:29:11 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2237843D48 for ; Tue, 3 Jan 2006 15:29:11 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 2EBBAC8; Tue, 3 Jan 2006 10:29:32 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id DDBBF3948; Tue, 3 Jan 2006 10:29:30 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Eto5z-0002sp-7h; Tue, 03 Jan 2006 15:29:07 +0000 Date: Tue, 3 Jan 2006 15:29:07 +0000 From: Brian Candler To: Paul Message-ID: <20060103152907.GA11044@uk.tiscali.com> 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 Subject: Re: FreeBSD 6.0 release, 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, 03 Jan 2006 15:29:11 -0000 On Sat, Dec 31, 2005 at 02:52:14AM +0000, Paul wrote: > I've just installed FreeBSD 6.0 Release yesterday, I've spend the last > two days trying to resolve a networking problem, the problem is this: > when I try and connect to a domain or an IP for that matter, it takes > several minutes for it to connect + receive the content. It doesn't > seem to effect all addresses though, I've had no problems connecting > to ftp://ftp.freebsd.org to download software etc., nor have I had any > problems connecting to domains inside my LAN. > > As far as I can tell, it isn't a dns problem because I can ping > without any problems. I had a similar problem here, and it was due to IPv6. Grr, I hate it. What happened was: some router was allocating IPv6 prefixes, and so my network interface picks up an IPv6 address. However actually there is no working IPv6 connectivity here. As a result, whenever I try to connect to a site which has both IPv6 and IPv4 addresses, I get a long delay of several minutes while the IPv6 one is tried out, before it falls back to IPv4. To show if this is the problem, use 'ifconfig' to show if your interface has been polluted by an IPv6 address. Then use 'ping6 www.foo.com' where www.foo.com is one of the sites you're having problems with. The problem is hidden by ping because ping only asks the DNS for IPv4 addresses. You can check if a site has an IPv6 address using $ dig www.foo.com. aaaa or $ nslookup -q=aaaa www.foo.com. IMO, the best solution to this is to remove IPv6 entirely from your kernel (comment out 'options INET6' and recompile). Your life will be much happier. Of course this would not be a problem if the IP stack were to try IPv4 addresses first, falling back to IPv6 if it fails. Of course, if IPv4 were to have precedence over IPv6, then the IPv6 stack would never get exercised. This is one of several problems which have plagued me simply because IPv6 is enabled by default when I don't want or use it. However if that's not the problem, then maybe your problem is with reverse DNS. That is, when you connect from your address (x.x.x.x) to a remote site (y.y.y.y), the remote site may do a reverse DNS lookup for x.x.x.x to try to find your hostname; if it gets a hostname, it will then do a forward DNS lookup to see if it maps back to x.x.x.x. You won't notice this problem as DNS lookups with ping, because you're just mapping www.foo.com to y.y.y.y; you're not trying to convert your own address x.x.x.x back to a domain, as a remote webserver would do. The solution then is to fix your reverse DNS. If your own IP address is 192.0.2.1, then a PTR query for 1.2.0.192.in-addr.arpa. is where you should be looking. Probably you have a lame delegation somewhere in the tree. Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 15:33:16 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59A1616A41F for ; Tue, 3 Jan 2006 15:33:16 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE1CB43D68 for ; Tue, 3 Jan 2006 15:33:15 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 45771F1; Tue, 3 Jan 2006 10:33:37 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id F13841FC8; Tue, 3 Jan 2006 10:33:35 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Eto9w-0002tD-UT; Tue, 03 Jan 2006 15:33:12 +0000 Date: Tue, 3 Jan 2006 15:33:12 +0000 From: Brian Candler To: Aluminium Oxide Message-ID: <20060103153312.GB11044@uk.tiscali.com> References: <1136167766.17477.250884723@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1136167766.17477.250884723@webmail.messagingengine.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: /usr/src/lib/libc/net/res_debug.c: compile problem fixed 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, 03 Jan 2006 15:33:16 -0000 On Mon, Jan 02, 2006 at 12:39:26PM +1030, Aluminium Oxide wrote: > Below is the output of `diff res_debug.org.c res_debug.c` > > I've also attached this. > ===================================================== > 574,575c574,575 > < precsize_aton(strptr) > < char **strptr; > --- > > precsize_aton(char **strptr) > > /* char **strptr; */ > 616,618c616,618 > < latlon2ul(latlonstrptr,which) > < char **latlonstrptr; > < int *which; Suggestion: use unified diff (diff -u res_debug.org.c res_debug.c). It's *much* easier to read. Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 18:15:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8363916A420 for ; Tue, 3 Jan 2006 18:15:04 +0000 (GMT) (envelope-from squigly@xsmail.com) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 509B443D90 for ; Tue, 3 Jan 2006 18:14:42 +0000 (GMT) (envelope-from squigly@xsmail.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id AEE96D2EF68; Tue, 3 Jan 2006 13:14:34 -0500 (EST) Received: from web2.messagingengine.com ([10.202.2.211]) by frontend1.internal (MEProxy); Tue, 03 Jan 2006 13:14:34 -0500 Received: by web2.messagingengine.com (Postfix, from userid 99) id 4B766E310; Tue, 3 Jan 2006 13:14:28 -0500 (EST) Message-Id: <1136312068.14794.250993952@webmail.messagingengine.com> X-Sasl-Enc: 4rSyWai55MWFsHrpbLl39VqS0qtmK9WL+fbq9nFzjAiz 1136312068 From: "Squigly" To: "Julian Elischer" , "Alexander Zhuravlev" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) References: <1135871527.31733.250727230@webmail.messagingengine.com> <43B40A23.7080502@mac.com> <1135874757.4898.250730784@webmail.messagingengine.com> <20051229171331.GA24337@orion.ulstu.ru> <43B46841.1030107@elischer.org> In-Reply-To: <43B46841.1030107@elischer.org> Date: Tue, 03 Jan 2006 10:14:28 -0800 Cc: freebsd-net@freebsd.org Subject: Re: Writing a netgraph module 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, 03 Jan 2006 18:15:04 -0000 > probably not too much.. :-) >=20 > has anyome actually looked at it? :-) >=20 >=20 > I can't get to Archie's doc on Daemonnews at the moment so here's my > copy: > http://people.freebsd.org/~julian/netgraph.html Great, Thanks! I did read this paper a while back (actualy, this what turned me on with netgraph to begin with) but the deamonnews article was down. I'll read it carfuly now, along with the source example, and of course, with any specific toungle I'll come back here. Thanks again guys. Squigly --=20 Squigly squigly@xsmail.com --=20 http://www.fastmail.fm - Same, same, but different=85 From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 18:28: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4180F16A41F; Tue, 3 Jan 2006 18:28:30 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4843443D60; Tue, 3 Jan 2006 18:28:29 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 03 Jan 2006 10:28:30 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43BAC24C.9050702@elischer.org> Date: Tue, 03 Jan 2006 10:28:28 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= References: <43B9C7CC.7090703@mr0vka.eu.org> <20060103115120.GG840@bashibuzuk.net> <43BA82F7.7070408@bromirski.net> In-Reply-To: <43BA82F7.7070408@bromirski.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 18:28:30 -0000 Łukasz Bromirski wrote: >Yann Berthier wrote: > > > >> If this yet to be found wiser guy would not forget the loose check >> too (verrevpath in ipfw speaking), where packets matching the default >> route are ok ... :) >> >> > >Actually it does that and will until we'll have option to have two >or more default routes. > >Presently, if packets comes via interface and reply for it should be >sent on the same interface (because default route points to it and >there are no other routes pointing for the same destination to >another interface) it will work. > >Check fails if there's either interface mismatch, or source is present >in routing table but marked as RTF_REJECT/BLACKHOLE one. > >OpenBSD imported KAME mroute extension that enables them to have >more than one route for given destination simultaneously in routing >table. I'm looking into it now, as it's very attractive thing, >however as Andre is doing rework of network code I'm sure we'll have >it sooner or later and then maybe someone will revise old checks >already marked as 'XXX' in the code ;) > > Several routes with the same dest would be interesting but how do you select between them? What I'm looking for is a way to make a machine use two totally separate routes depending on the socket address locally.. I'm currenty achieving this with ipfw fwd rules, bu that has side effects that are troublesome.. The vimage patches would do this for me but they are only for 4.x and I see no way to do what they do in a truely extensible manner that woruld work for 5.x and beyond.' From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 18:32:36 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AF4C16A41F for ; Tue, 3 Jan 2006 18:32:36 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id E832543D64 for ; Tue, 3 Jan 2006 18:32:35 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 03 Jan 2006 10:32:37 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43BAC343.7090508@elischer.org> Date: Tue, 03 Jan 2006 10:32:35 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Squigly References: <1135871527.31733.250727230@webmail.messagingengine.com> <43B40A23.7080502@mac.com> <1135874757.4898.250730784@webmail.messagingengine.com> <20051229171331.GA24337@orion.ulstu.ru> <43B46841.1030107@elischer.org> <1136312068.14794.250993952@webmail.messagingengine.com> In-Reply-To: <1136312068.14794.250993952@webmail.messagingengine.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Zhuravlev , freebsd-net@freebsd.org Subject: Re: Writing a netgraph module 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, 03 Jan 2006 18:32:36 -0000 Squigly wrote: >>probably not too much.. :-) >> >>has anyome actually looked at it? :-) >> >> >>I can't get to Archie's doc on Daemonnews at the moment so here's my >>copy: >> http://people.freebsd.org/~julian/netgraph.html >> >> > >Great, Thanks! > >I did read this paper a while back (actualy, this what turned me on with >netgraph to >begin with) but the deamonnews article was down. > >I'll read it carfuly now, along with the source example, and of course, >with any specific toungle >I'll come back here. > >Thanks again guys. > >Squigly > > remember that things changed a bit after teh 5.x transition. teh video referred to covers that change a bit. > > > > From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 19:44:09 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E28A16A41F for ; Tue, 3 Jan 2006 19:44:09 +0000 (GMT) (envelope-from pieter@thedarkside.nl) Received: from mail.thelostparadise.com (129pc197.sshunet.nl [145.97.197.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7825D43D45 for ; Tue, 3 Jan 2006 19:43:57 +0000 (GMT) (envelope-from pieter@thedarkside.nl) Received: from [195.16.84.92] (ip-84-92.members.virt-ix.net [195.16.84.92]) by mail.thelostparadise.com (8.13.1/8.13.1) with ESMTP id k03JhkGP026646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Jan 2006 20:43:48 +0100 (CET) (envelope-from pieter@thedarkside.nl) Message-ID: <43BAD3F2.9040406@thedarkside.nl> Date: Tue, 03 Jan 2006 20:43:46 +0100 From: Pieter de Boer User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050805) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Zongsheng Zhang References: <43B11DF3.8070501@ist.osaka-u.ac.jp> <43B7CC3C.4080606@roq.com> <43BA4D6F.6060706@ist.osaka-u.ac.jp> In-Reply-To: <43BA4D6F.6060706@ist.osaka-u.ac.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Michael Vince , freebsd-net@freebsd.org Subject: Re: tcp performance 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, 03 Jan 2006 19:44:09 -0000 Zongsheng Zhang wrote: > I have confirmed that there is no problem with settings of Dummynet. > When Host-A/B uses Linux, the throughput of RTT=20ms (using Iperf) is > same as that of RTT=0ms. > > Host-A/B use FreeBSD v6.0 release. Does anyone have > experience/suggestion for achieving high throughput with FreeBSD? In June 2005, a former fellow-student and me did such tests using FreeBSD 5.4. Our test setup was the same as yours. We used three Dell Poweredge 1850's (iirc) with dual Xeon processors, PCI-X gbit 'em' interfaces and we used iperf too. Performance was terrible with high RTT's. We tried all kinds of things: SMP or UP kernels, polling (and it's settings), fiddling with HZ on the dummynet-host, lowering and raising the IP input queue maxlen, etc. In the end we pinged the sending host over it's external/non-test interface. We saw enormous packet loss and latency up to 5 -seconds-. This lead us to believe the TCP or socket buffer code (but probably the former, since the socket buffer is appended to using a simple tail pointer) was that inefficient that the kernel wasn't doing much else than sending TCP packets. Sadly, we did not have any time to research it any more. Perhaps Andre Opperman can shed some light on this, seeing as he's hacking away at the TCP/IP code now.. In any case, when his work is committed, you should have a lot more performance :) -- Pieter From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 20:36:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1698A16A420 for ; Tue, 3 Jan 2006 20:36:04 +0000 (GMT) (envelope-from lukasz@bromirski.net) Received: from r2d2.bromirski.net (r2d2.bromirski.net [217.153.57.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D48443D55 for ; Tue, 3 Jan 2006 20:36:03 +0000 (GMT) (envelope-from lukasz@bromirski.net) Received: from [127.0.0.1] (r2d2.bromirski.net [217.153.57.194]) by r2d2.bromirski.net (Postfix) with ESMTP id AE97A108AC6; Tue, 3 Jan 2006 21:43:00 +0100 (CET) Message-ID: <43BAE02E.2020401@bromirski.net> Date: Tue, 03 Jan 2006 21:35:58 +0100 From: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= User-Agent: Thunderbird 1.5 (Windows/20051207) MIME-Version: 1.0 To: Julian Elischer References: <43B9C7CC.7090703@mr0vka.eu.org> <20060103115120.GG840@bashibuzuk.net> <43BA82F7.7070408@bromirski.net> <43BAC24C.9050702@elischer.org> In-Reply-To: <43BAC24C.9050702@elischer.org> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: Reverse Path Filtering check in ip_input.c 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, 03 Jan 2006 20:36:04 -0000 Julian Elischer wrote: > Several routes with the same dest would be interesting but how do you > select between them? Via some sort of load-balancing or policy routing mechanism on network stack level? There is so much we miss in current FreeBSD stack in this area it's hard to say some single feature will change everything completely. I only mentioned OpenBSD KAME import because they are clearly going for having multihomed router fully operable and we're lacking in this area. Also, Henning, Claudio and other team members push for routing protocols interoperability (OpenOSPFd and OpenBGPd integration) which again is far from what we're currently able to do and integrate. Andre as I understand is cleaning code and making everything run a lot faster (especially routing operation optimization is great thing), but I'm worried that being able to have things like administrative distance for various routing protocols (which would enable router with for example OSPF and BGP to choose routes from both protocols in clear selection process), ability to store few paths for the same destination via different interfaces or next-hops is a long road ahead. But there's always someone who has to do first step... ;) -- this space was intentionally left blank | Łukasz Bromirski you can insert your favourite quote here | lukasz:bromirski,net From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 23:42:29 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30AEB16A423 for ; Tue, 3 Jan 2006 23:42:28 +0000 (GMT) (envelope-from dennisolvany@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3952E43D46 for ; Tue, 3 Jan 2006 23:42:27 +0000 (GMT) (envelope-from dennisolvany@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so2432700wra for ; Tue, 03 Jan 2006 15:42:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=m8MhyAvczHFltCQhUL/Uap0UTCUJFattafR0+AdZaxktzu4Mer5cm9l09kSt1hfw0BO34XVebb+BuvpqY6bYzstq/ajFDgHiSDEujDDfjZICHEy4duN6cdDOO0lWtG8UjxdBO7J1zEXJk2fIUPdMPusfU4sl9KOIFav48lYo2h8= Received: by 10.54.72.15 with SMTP id u15mr1857832wra; Tue, 03 Jan 2006 15:42:26 -0800 (PST) Received: from ?192.168.10.2? ( [67.102.60.210]) by mx.gmail.com with ESMTP id 28sm2545102wrl.2006.01.03.15.42.25; Tue, 03 Jan 2006 15:42:26 -0800 (PST) Message-ID: <43BB0BC6.3070409@gmail.com> Date: Tue, 03 Jan 2006 17:41:58 -0600 From: Dennis Olvany User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051129) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org X-Enigmail-Version: 0.93.0.0 OpenPGP: id=D71A85AB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Client Load Balancing: LSNAT-router using IPFW and NATD on FreeBSD 6.0 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, 03 Jan 2006 23:42:29 -0000 Client Load Balancing: LSNAT-router using IPFW and NATD on FreeBSD 6.0 The Internet gateways must reside in different logical networks for this configuration to work. 1. Compile Custom Kernel options IPFIREWALL options IPFIREWALL_FORWARD options IPDIVERT options IPFIREWALL_FORWARD_EXTENDED 2. Configure System (/etc/rc.conf) firewall_enable="yes" firewall_type="/etc/ipfw.rules" ifconfig_ste0="195.16.87.38/29" ifconfig_ste0_alias0="192.168.102.62/24" ifconfig_fxp0="192.168.10.1/24" defaultrouter="192.168.102.1" gateway_enable="yes" natd_enable="yes" natd_flags="-f /etc/natd.conf" 3. Configure NATD (/etc/natd.conf) instance default alias_address 192.168.102.62 instance other alias_address 195.16.87.38 port 8669 globalport 9000 4. Configure IPFW (/etc/ipfw.rules) -f flush add skipto 20000 ip from any to 192.168.102.62 in via ste0 add skipto 30000 ip from any to 195.16.87.38 in via ste0 add divert 9000 ip from any to any out via ste0 add skipto 40000 ip from { 192.168.102.62 or 195.16.87.38 } to any out via ste0 add prob .5 skipto 20000 ip from any to any out via ste0 add skipto 30000 ip from any to any out via ste0 add skipto 40000 ip from any to any add 20000 divert natd ip from any to any add skipto 40000 ip from any to any add 30000 divert 8669 ip from any to any add skipto 40000 ip from any to any add 40000 check-state add deny ip from 192.168.10.0/24 to any via ste0 add allow ip from me to me via lo0 keep-state add deny ip from me to any in add allow ip from 195.16.87.38 to { me or 195.16.87.32/29 or 192.168.102.0/24 or 192.168.10.0/24 } keep-state add forward 195.16.87.33 ip from 195.16.87.38 to any keep-state add allow ip from me to any keep-state add deny ip from me to any add allow icmp from any to me icmptypes 3,4,8,11 keep-state add deny ip from any to me add allow ip from 192.168.10.0/24 to any keep-state add deny ip from 192.168.10.0/24 to any add allow icmp from any to 192.168.10.0/24 icmptypes 3,4,11 keep-state add deny ip from any to 192.168.10.0/24 From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 04:17:34 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AF1D16A41F for ; Wed, 4 Jan 2006 04:17:34 +0000 (GMT) (envelope-from Bob.Halley@nominum.com) Received: from shell-ng.nominum.com (shell-ng.nominum.com [81.200.64.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4818C43D62 for ; Wed, 4 Jan 2006 04:17:33 +0000 (GMT) (envelope-from Bob.Halley@nominum.com) Received: from [128.177.199.33] (vpn-33.vpn.nominum.com [128.177.199.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id 7F10D5685A for ; Tue, 3 Jan 2006 20:17:32 -0800 (PST) (envelope-from Bob.Halley@nominum.com) Message-ID: <43BB4C59.3010800@nominum.com> Date: Wed, 04 Jan 2006 14:47:29 +1030 From: Bob Halley User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: multipart/mixed; boundary="------------060309070601060706020401" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Unexpected EADDRINUSE 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, 04 Jan 2006 04:17:34 -0000 This is a multi-part message in MIME format. --------------060309070601060706020401 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Some of our regression tests fail randomly on FreeBSD with an unexpected EADDRINUSE error. We didn't see this problem with 4.7, but we see it in 4.11, 5.4, and 6.0. We don't see this behavior on any of our other supported platforms. We investigated the problem, and managed to come up with a way to reproduce the problem outside of our regression test suite. To reproduce, first start the sink with "python sink.py". Then run "python conn.py". When we do this, we get EADDRINUSE after a short time. Since we're binding the connecting socket to the wild port, this shouldn't happen. If the s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) call is removed, the problem seems to go away. The setting of SO_REUSEADDR is there because that's what some perhaps too-generic make-a-socket library code did; we realize it's not technically needed. Nevertheless, we don't see why it should fail either :). I looked at the differences between 4.7 and later kernels but didn't manage to figure out how the changes caused this change in behavior. Regards, /Bob --------------060309070601060706020401-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 04:22: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9F7416A420 for ; Wed, 4 Jan 2006 04:22:05 +0000 (GMT) (envelope-from Bob.Halley@nominum.com) Received: from shell-ng.nominum.com (shell-ng.nominum.com [81.200.64.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4736343D60 for ; Wed, 4 Jan 2006 04:22:05 +0000 (GMT) (envelope-from Bob.Halley@nominum.com) Received: from [128.177.199.33] (vpn-33.vpn.nominum.com [128.177.199.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id B1EFC56821 for ; Tue, 3 Jan 2006 20:22:04 -0800 (PST) (envelope-from Bob.Halley@nominum.com) Message-ID: <43BB4D6A.8030703@nominum.com> Date: Wed, 04 Jan 2006 14:52:02 +1030 From: Bob Halley User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <43BB4C59.3010800@nominum.com> In-Reply-To: <43BB4C59.3010800@nominum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Unexpected EADDRINUSE 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, 04 Jan 2006 04:22:05 -0000 Sorry my attachments didn't make it :) # # sink.py # import socket import traceback s = socket.socket(socket.AF_INET, socket.SOCK_STREAM, 0) s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) s.bind(('127.0.0.1', 12345)) s.listen(5) while True: try: n = s.accept()[0] d = None while d != '': d = n.recv(100) n.close() except socket.error: pass # # conn.py # import socket import traceback n = 0 while True: try: s = socket.socket(socket.AF_INET, socket.SOCK_STREAM, 0) s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) s.bind(('127.0.0.1', 0)) print s.getsockname() s.connect(('127.0.0.1', 12345)) s.close() n += 1 if n > 0 and n % 1000 == 0: print n except Exception, e: traceback.print_exc() break print n From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 05:12:16 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C97D16A41F for ; Wed, 4 Jan 2006 05:12:16 +0000 (GMT) (envelope-from karel.miklav@siol.net) Received: from mta1.siol.net (mta1.siol.net [193.189.160.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5752943D7C for ; Wed, 4 Jan 2006 05:12:08 +0000 (GMT) (envelope-from karel.miklav@siol.net) Received: from edge1.siol.net ([10.10.10.210]) by mta1.siol.net with ESMTP id <20060104051401.PKFR4492.mta1.siol.net@edge1.siol.net> for ; Wed, 4 Jan 2006 06:14:01 +0100 Received: from [192.168.0.149] (really [194.165.117.145]) by edge1.siol.net with ESMTP id <20060104051206.ZCHV19229.edge1.siol.net@[192.168.0.149]> for ; Wed, 4 Jan 2006 06:12:06 +0100 Message-ID: <43BB5923.7040108@siol.net> Date: Wed, 04 Jan 2006 06:12:03 +0100 From: Karel Miklav User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051109) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Direct routing 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, 04 Jan 2006 05:12:16 -0000 I'd like to do something like described on the LVS pages http://www.linuxvirtualserver.org/VS-DRouting.html, that is route requests to another server and answer from this second server directly to the client. How can I do it on FreeBSD? -- Thanks, Karel Miklav From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 05:56: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B960016A41F for ; Wed, 4 Jan 2006 05:56:47 +0000 (GMT) (envelope-from dennisolvany@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E452A43D53 for ; Wed, 4 Jan 2006 05:56:46 +0000 (GMT) (envelope-from dennisolvany@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so2477922wra for ; Tue, 03 Jan 2006 21:56:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=Wt+jwcv5P7fJcxbHG/Vv32Z6BEhXxy9H8ifuZNjQaAd4HOLgvd/ETxPbzfpnmlE8Giimx7tUVJfJ6sub6Uo32yLyGiBNYLyQJ4LpkrNiVp1pDd2UMu/UzYvjgA1N96LjPur2FIR0xjOgkLlElPjJ8aozUR/pLMPVpYGnJ9HRPZk= Received: by 10.54.153.18 with SMTP id a18mr1817842wre; Tue, 03 Jan 2006 21:56:45 -0800 (PST) Received: from ?192.168.10.2? ( [195.16.87.38]) by mx.gmail.com with ESMTP id 66sm14300587wra.2006.01.03.21.56.44; Tue, 03 Jan 2006 21:56:45 -0800 (PST) Message-ID: <43BB637F.5050402@gmail.com> Date: Tue, 03 Jan 2006 23:56:15 -0600 From: Dennis Olvany User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051129) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karel Miklav References: <43BB5923.7040108@siol.net> In-Reply-To: <43BB5923.7040108@siol.net> X-Enigmail-Version: 0.93.0.0 OpenPGP: id=D71A85AB Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Direct routing 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, 04 Jan 2006 05:56:47 -0000 Karel Miklav wrote: > I'd like to do something like described on the LVS pages > http://www.linuxvirtualserver.org/VS-DRouting.html, that is route > requests to another server and answer from this second server > directly to the client. How can I do it on FreeBSD? You can use lsnat. http://www.enterasys.com/products/whitepapers/load-sharing-nat/ -redirect_address localIP[,localIP[,...]] publicIP These forms of -redirect_port and -redirect_address are used to transparently offload network load on a single server and distribute the load across a pool of servers. This function is known as LSNAT (RFC 2391). For example, the argument tcp www1:http,www2:http,www3:http www:http means that incoming HTTP requests for host www will be trans- parently redirected to one of the www1, www2 or www3, where a host is selected simply on a round-robin basis, without regard to load on the net. http://www.freebsd.org/cgi/man.cgi?query=natd From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 14:37: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 453DE16A41F for ; Wed, 4 Jan 2006 14:37:50 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B180943D5A for ; Wed, 4 Jan 2006 14:37:47 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from lapdance.yazzy.net (unknown [192.168.99.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yazzy.org (Postfix) with ESMTP id 1522939834; Wed, 4 Jan 2006 15:38:00 +0100 (CET) Date: Wed, 4 Jan 2006 14:36:59 +0000 From: Marcin Jessa To: Dennis Olvany Message-Id: <20060104143659.04dd2174.lists@yazzy.org> In-Reply-To: <43BB637F.5050402@gmail.com> References: <43BB5923.7040108@siol.net> <43BB637F.5050402@gmail.com> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, karel.miklav@siol.net Subject: Re: Direct routing 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, 04 Jan 2006 14:37:50 -0000 On Tue, 03 Jan 2006 23:56:15 -0600 Dennis Olvany wrote: > Karel Miklav wrote: > > I'd like to do something like described on the LVS pages > > http://www.linuxvirtualserver.org/VS-DRouting.html, that is route > > requests to another server and answer from this second server > > directly to the client. How can I do it on FreeBSD? > > You can use lsnat. > > http://www.enterasys.com/products/whitepapers/load-sharing-nat/ > > -redirect_address localIP[,localIP[,...]] publicIP > > These forms of -redirect_port and -redirect_address are used > to transparently offload network load on a single server and > distribute the load across a pool of servers. This function > is known as LSNAT (RFC 2391). For example, the argument > > tcp www1:http,www2:http,www3:http www:http > > means that incoming HTTP requests for host www will be trans- > parently redirected to one of the www1, www2 or www3, where a > host is selected simply on a round-robin basis, without > regard to load on the net. > > http://www.freebsd.org/cgi/man.cgi?query=natd Check also the pf FAQ: http://www.openbsd.org/faq/pf/pools.html section "Load Balance Incoming Connections" Cheers, Marcin Jessa From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 17:54:52 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3946D16A41F for ; Wed, 4 Jan 2006 17:54:52 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) Received: from mail.npubs.com (mail.wsfamily.com [209.66.100.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F51243D66 for ; Wed, 4 Jan 2006 17:54:49 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) From: Nate Nielsen User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: multipart/mixed; boundary="------------070001070905060004070601" Message-Id: <20060104181309.8C756DCA990@mail.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Wed, 4 Jan 2006 18:13:10 +0000 (GMT) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with PMTU Discovery / DF / IPSEC / GIF Tunnels (FreeBSD 6.0 patch) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nielsen@memberwebs.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:54:52 -0000 This is a multi-part message in MIME format. --------------070001070905060004070601 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I encountered a strange problem with PMTU discovery not working properly on various machines when the packets were tunneled over a GIF / IPSEC Transport type tunnel (both ends running FreeBSD 6.0). Configuration files attached. Various older FreeBSD systems (it seemed systems that had jails running) and also Windows Virtual Machines running in Microsoft's Virtual Server 2005 system, did not perform PMTU discovery properly. The FreeBSD 6.0 routers were sending out ICMP host-unreachable need-fragment packets without an MTU hint. Most machines handle this fine, but the ones noted above did not decrease PMTU for the connection. The attached patch makes sure that the FreeBSD 6.0 router will include an MTU hint in the ICMP packet. The problem was caused by the IPSec lookup in ip_forward() returning an secpolicy pointer, but then that pointer having no details (such as request, etc...) contained in it. The attached patch (against 6.0) covers that eventuality. The 'bug' is obviously in the machines that don't handle the missing MTU hint properly, but since we can't patch Windows, this patch helps alleviate the problem from the other side. Cheers, Nate --------------070001070905060004070601 Content-Type: text/x-patch; name="pmtu-gif-ipsec.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pmtu-gif-ipsec.patch" --- sys/netinet/ip_input.c.orig Wed Jan 4 10:18:01 2006 +++ sys/netinet/ip_input.c Wed Jan 4 10:39:35 2006 @@ -1918,29 +1918,29 @@ ip_forward(struct mbuf *m, int srcrt) } } #ifdef IPSEC key_freesp(sp); #else /* FAST_IPSEC */ KEY_FREESP(&sp); #endif - ipstat.ips_cantfrag++; - break; - } else + } #endif /*IPSEC || FAST_IPSEC*/ - /* - * When doing source routing 'ia' can be NULL. Fall back - * to the minimum guaranteed routeable packet size and use - * the same hack as IPSEC to setup a dummyifp for icmp. - */ - if (ia == NULL) - mtu = IP_MSS; - else - mtu = ia->ia_ifp->if_mtu; + if (!mtu) { + /* + * When doing source routing 'ia' can be NULL. Fall back + * to the minimum guaranteed routeable packet size and use + * the same hack as IPSEC to setup a dummyifp for icmp. + */ + if (ia == NULL) + mtu = IP_MSS; + else + mtu = ia->ia_ifp->if_mtu; + } #if defined(IPSEC) || defined(FAST_IPSEC) } #endif /*IPSEC || FAST_IPSEC*/ ipstat.ips_cantfrag++; break; case ENOBUFS: /* --------------070001070905060004070601-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 23:19:02 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19B7816A41F for ; Wed, 4 Jan 2006 23:19:02 +0000 (GMT) (envelope-from karel@lovetemple.net) Received: from mta1.siol.net (mta1.siol.net [193.189.160.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id B02B743D72 for ; Wed, 4 Jan 2006 23:18:36 +0000 (GMT) (envelope-from karel@lovetemple.net) Received: from edge1.siol.net ([10.10.10.210]) by mta1.siol.net with ESMTP id <20060104232025.OAJB4492.mta1.siol.net@edge1.siol.net> for ; Thu, 5 Jan 2006 00:20:25 +0100 Received: from [192.168.0.149] (really [193.77.226.244]) by edge1.siol.net with ESMTP id <20060104231823.XLEL19229.edge1.siol.net@[192.168.0.149]> for ; Thu, 5 Jan 2006 00:18:23 +0100 Message-ID: <43BC57B9.1040309@lovetemple.net> Date: Thu, 05 Jan 2006 00:18:17 +0100 From: Karel Miklav User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051109) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <43BB5923.7040108@siol.net> <43BB637F.5050402@gmail.com> <20060104143659.04dd2174.lists@yazzy.org> In-Reply-To: <20060104143659.04dd2174.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Direct routing 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, 04 Jan 2006 23:19:02 -0000 Dennis and Marcin, thanks very much for your replies. I've also found the 'LVS on FreeBSD' page at http://dragon.linux-vs.org/~dragonfly/htm/lvs_freebsd.htm. -- Regards, Karel Miklav From owner-freebsd-net@FreeBSD.ORG Thu Jan 5 03:38:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF4AF16A41F for ; Thu, 5 Jan 2006 03:38:04 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54F3743D49 for ; Thu, 5 Jan 2006 03:38:04 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id C95154CC1A; Thu, 5 Jan 2006 03:38:08 +0000 (GMT) Received: from [192.168.0.2] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id EC5274CC2A; Thu, 5 Jan 2006 03:38:07 +0000 (GMT) Message-ID: <43BC949A.2020405@roq.com> Date: Thu, 05 Jan 2006 14:38:02 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jon Otterholm References: <43BA71F6.2080305@ide.resurscentrum.se> In-Reply-To: <43BA71F6.2080305@ide.resurscentrum.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-net@freebsd.org Subject: Re: Router + ADM64 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, 05 Jan 2006 03:38:05 -0000 Jon Otterholm wrote: > Hi! > > What is there to gain in performance choosing AMD64 on a Dell PE1850 > (Xeon EMT64) when used as router? > > /Jon I have one running under Amd64 FreeBSD. When polling is enabled I do get transfer speeds of up to 112megabytes/sec, the only real down side as far as I am concerned is missing out on VPN capability, which is broken on the AMD64 arch for unknown reasons, I can only hope I won't need it. Mike From owner-freebsd-net@FreeBSD.ORG Thu Jan 5 11:04:09 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB19016A41F for ; Thu, 5 Jan 2006 11:04:09 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31BCF43D55 for ; Thu, 5 Jan 2006 11:04:08 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 92270D9 for ; Thu, 5 Jan 2006 06:04:28 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 5F2A91FC8 for ; Thu, 5 Jan 2006 06:04:28 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuSua-0006hu-Ty for freebsd-net@freebsd.org; Thu, 05 Jan 2006 11:04:05 +0000 Date: Thu, 5 Jan 2006 11:04:04 +0000 From: Brian Candler To: freebsd-net@freebsd.org Message-ID: <20060105110404.GA25737@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: sl2tps, MRU, MTU, and MSS 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, 05 Jan 2006 11:04:09 -0000 I've done a bit more debugging on the MSS problem I'm having with sl2tps running with IPSEC transport layer security. The client is Windows XP out-of-the-box. Here's what happens: 1. PPP negotiates an MRU of 1400 2. However, ifconfig ng0 shows an MTU of 1376 (where does that come from?) 3. When the client opens a TCP connection, it offers an MSS of 1360 4. When the remote webserver responds, it offers an MSS of 1380 (?) 5. The client sends a HTTP request, the server responds (MSS1360 / MTU1400), but that's too large to fit ng0 (MTU 1376) root@candlerb ~# ifconfig ng0 ng0: flags=88d1 mtu 1376 inet 172.17.0.216 --> 192.168.100.100 netmask 0xffffffff root@candlerb ~# tcpdump -i rl0 -n -s1500 tcp port 80 or icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on rl0, link-type EN10MB (Ethernet), capture size 1500 bytes 10:41:16.454720 IP 172.17.0.216.58826 > 212.100.234.54.80: S 1482417021:1482417021(0) win 16384 10:41:16.464675 IP 212.100.234.54.80 > 172.17.0.216.58826: S 1193972421:1193972421(0) ack 1482417022 win 5840 10:41:16.465486 IP 172.17.0.216.58826 > 212.100.234.54.80: . ack 1 win 17680 10:41:16.466490 IP 172.17.0.216.58826 > 212.100.234.54.80: P 1:522(521) ack 1 win 17680 10:41:16.477538 IP 212.100.234.54.80 > 172.17.0.216.58826: . ack 522 win 6432 10:41:16.485841 IP 212.100.234.54.80 > 172.17.0.216.58826: . 1:1361(1360) ack 522 win 6432 10:41:16.485983 IP 172.17.0.216 > 212.100.234.54: ICMP 172.17.0.216 unreachable - need to frag, length 36 10:41:16.487047 IP 212.100.234.54.80 > 172.17.0.216.58826: . 1361:2721(1360) ack 522 win 6432 10:41:16.487114 IP 172.17.0.216 > 212.100.234.54: ICMP 172.17.0.216 unreachable - need to frag, length 36 10:41:19.512030 IP 212.100.234.54.80 > 172.17.0.216.58826: . 1:1361(1360) ack 522 win 6432 10:41:19.512182 IP 172.17.0.216 > 212.100.234.54: ICMP 172.17.0.216 unreachable - need to frag, length 36 172.17.0.216 is the IP address of the FreeBSD box; the client's L2TP pool address has been NATted to this using pf. And of course, being a private address, the FreeBSD box is also behind a NAT firewall. And because of this, the ICMP 'need to frag' message isn't getting back to the webserver, and everything falls over. So I have the following questions: 1. If the PPP MRU is 1400 (which appears to be correctly picked up on the Windows side), why is the ng0 MTU 1376? 2. How can I fix this problem, without manually frigging the MTU at the Windows client side? I don't think the IPSEC transport header is anything to do with this: the PPP session sits *within* the IPSEC encapsulation, and 1400 is plenty of space for an IPSEC header to be added and still fit within Ethernet MTU. Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Thu Jan 5 15:28: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27A7D16A41F for ; Thu, 5 Jan 2006 15:28:01 +0000 (GMT) (envelope-from EDouglass@gaylordhotels.com) Received: from gaylordentertainment.com (mail.gaylordentertainment.com [12.153.11.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A35543D53 for ; Thu, 5 Jan 2006 15:27:42 +0000 (GMT) (envelope-from EDouglass@gaylordhotels.com) Received: from 10.42.4.102 by gaylordentertainment.com with ESMTP (TN SMTP Relay); Thu, 05 Jan 2006 09:27:22 -0600 X-Server-Uuid: E485C1F1-10DB-4031-9668-820096A468D3 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 5 Jan 2006 09:26:02 -0600 Message-ID: <566E54419328A642A3A6E91376E885B1047BA1F6@txex.tx.get> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proxy Thread-Index: AcYSDFVPf/hZmfxHT3GL2ZdLrrPuqw== From: "Douglass, Erik" To: freebsd-net@freebsd.org X-MMS-Spam-Filter-ID: A2006010505_2.0.4,4.0-7 X-TMWD-Spam-Summary: SEV=0.9; DFV=A2006010505; IFV=2.0.4,4.0-7; RPD=NA; RPDID=NA; ENG=IBF; TS=20060105152724; CAT=NONE; CON=NONE; X-WSS-ID: 6FA3E55327S13101267-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Proxy 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, 05 Jan 2006 15:28:01 -0000 Hello, =20 I know this may sound as if I am biting off a bit more than I can chew as I don't have much exp with FreeBSD or Unix. I work at a hotel, and have been tasked to implement a proxy for all of the guest rooms that displays an html legal disclaimer that the guest has to agree to in order to get out. I have chosen to use FreeBSD as I do have some (very minimal) experience with it. I don't expect a full step by step, but if anyone could throw me some key words, tips, etc to get my internet searches started I would be most thankful. =20 Any tips on how to -=20 =20 Set up a proxy/router Serve the web page that needs to be agreed to before it allows one out. =20 Thanks!! =20 Erik From owner-freebsd-net@FreeBSD.ORG Thu Jan 5 16:44: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C01416A41F for ; Thu, 5 Jan 2006 16:44:33 +0000 (GMT) (envelope-from regnauld@catpipe.net) Received: from moof.catpipe.net (moof.catpipe.net [195.249.214.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B6CC43D5A for ; Thu, 5 Jan 2006 16:44:31 +0000 (GMT) (envelope-from regnauld@catpipe.net) Received: from localhost (localhost [127.0.0.1]) by localhost.catpipe.net (Postfix) with ESMTP id 0E3931B35F; Thu, 5 Jan 2006 17:44:30 +0100 (CET) Received: from moof.catpipe.net ([127.0.0.1]) by localhost (moof.catpipe.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34705-10; Thu, 5 Jan 2006 17:44:24 +0100 (CET) Received: from vinyl.catpipe.net (vinyl.catpipe.net [195.249.214.189]) by moof.catpipe.net (Postfix) with ESMTP id 91D3E1B358; Thu, 5 Jan 2006 17:44:16 +0100 (CET) Received: by vinyl.catpipe.net (Postfix, from userid 1006) id AC5BA39834; Thu, 5 Jan 2006 17:41:44 +0100 (CET) Date: Thu, 5 Jan 2006 17:41:44 +0100 From: Phil Regnauld To: "Douglass, Erik" Message-ID: <20060105164144.GA77891@catpipe.net> References: <566E54419328A642A3A6E91376E885B1047BA1F6@txex.tx.get> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <566E54419328A642A3A6E91376E885B1047BA1F6@txex.tx.get> X-Operating-System: FreeBSD 5.4-STABLE i386 Organization: catpipe Systems ApS User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at catpipe.net Cc: freebsd-net@freebsd.org Subject: Re: Proxy 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, 05 Jan 2006 16:44:33 -0000 Douglass, Erik (EDouglass) writes: > Hello, > > > > I know this may sound as if I am biting off a bit more than I can chew > as I don't have much exp with FreeBSD or Unix. I work at a hotel, and > have been tasked to implement a proxy for all of the guest rooms that > displays an html legal disclaimer that the guest has to agree to in > order to get out. I have chosen to use FreeBSD as I do have some (very > minimal) experience with it. I don't expect a full step by step, but if > anyone could throw me some key words, tips, etc to get my internet > searches started I would be most thankful. You are looking for what's called a captive gateway. Try looking at www.m0n0.ch/wall (m0n0wall) to start with. > Any tips on how to - > > Set up a proxy/router > > Serve the web page that needs to be agreed to before it allows one out. They're not very complicated tasks, you should start by looking at: NoCatAuth is our original "catch and release" captive portal implementation. It provides a simple splash screen web page for clients on your network, as well as a variety of authenticated modes. It is written in Perl. NoCatSplash is the C port of NoCatAuth. It currently supports a splash screen (also known as "open mode") and has beta support for authenticated access. http://nocat.net/ From owner-freebsd-net@FreeBSD.ORG Fri Jan 6 02:15: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DCB716A41F for ; Fri, 6 Jan 2006 02:15:26 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 130B743D45 for ; Fri, 6 Jan 2006 02:15:25 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k062FKwk012642; Thu, 5 Jan 2006 18:15:20 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k062FKYD012641; Thu, 5 Jan 2006 18:15:20 -0800 Date: Thu, 5 Jan 2006 18:15:20 -0800 From: Brooks Davis To: JK Message-ID: <20060106021520.GG31301@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="reI/iBAAp9kzkmX4" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-net@freebsd.org Subject: Re: 5.4 / 6.0 wi0 and dhcp with closed network 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, 06 Jan 2006 02:15:26 -0000 --reI/iBAAp9kzkmX4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 28, 2005 at 04:04:57PM -0400, JK wrote: > On Wed, 28 Dec 2005 12:05:10 -0400 > "JK" wrote: > >I cannot get this to work at startup time on 5.4 > > > >On 6.0 I put ifconfig_wi0=3D"ssid mynet DHCP" into /etc/rc.conf and=20 > >that works. I end up on the closed 'mynet' network via a DHCP=20 > >address. > > > >On 5.4 neither that line nor other combinations in /etc/rc.conf of > > > >ifconfig_wi0=3D"DHCP" > >ifconfig_wi0=3D"ssid mynet" > >dhclient wi0 > > > >work. I _can_ get up on 5.4 by booting and then manually doing > > > >ifconfig wi0 ssid mynet > >dhclient wi0 > > > >After dhclient receives the IP etc from the server the machine is up=20 > >fine. > > > >How in the world do I do this in /etc/rc.conf ( or other files ) on=20 > >5.4 so it works automatically at startup time? > >_____________________________________ >=20 > Following myself up, the only way I could get this to work in 5.4 at=20 > startup time was to create a /etc/start_if.wi0 that contained >=20 > ifconfig wi0 ssid mynet > dhclient wi0 >=20 > and not put any ifconfig_XX commands into my /etc/rc.conf >=20 > That seems pretty cheesey to me but it works. If anyone else has a=20 > cleaner way I'd love to know what it is. /etc/start_if.* is the only option in 5.4. It is indeed lame, that's why I wrote the better support in 6.0. You should be able to set ifconfig_XX=3D"DHCP" instead of running dhclient manually though. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --reI/iBAAp9kzkmX4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDvdK4XY6L6fI4GtQRAk0uAKC3TZxgnNJwiukgPtoS6mx2WHG9zACfQ7dy u5glk13tRLmqC8hvdntnfnY= =dbKc -----END PGP SIGNATURE----- --reI/iBAAp9kzkmX4-- From owner-freebsd-net@FreeBSD.ORG Fri Jan 6 07:18:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FAF216A41F for ; Fri, 6 Jan 2006 07:18:08 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: from web30008.mail.mud.yahoo.com (web30008.mail.mud.yahoo.com [68.142.200.71]) by mx1.FreeBSD.org (Postfix) with SMTP id E2FF943D45 for ; Fri, 6 Jan 2006 07:18:07 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: (qmail 87773 invoked by uid 60001); 6 Jan 2006 07:18:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=o1YWOHvxfevcs92RVeOmo77/pYcZpq0nJkomnMHHMTUgl8+wCn4fZKNLdaDlV4T9NVzqCeG3ampl8C7v4mMbgnuXiUQv0JY25NXkXL0eWaW3OlsSKImTov/FvWZ9I6C54nYu+5TPwl5aWtF9V0jvT9VMkvzbtxnLzyZ9YUGWn0U= ; Message-ID: <20060106071807.87771.qmail@web30008.mail.mud.yahoo.com> Received: from [202.161.131.69] by web30008.mail.mud.yahoo.com via HTTP; Thu, 05 Jan 2006 23:18:07 PST Date: Thu, 5 Jan 2006 23:18:07 -0800 (PST) From: kamal kc To: freebsd MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: increasing the ethernet MTU greater than 1500 (1502) 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, 06 Jan 2006 07:18:08 -0000 dear everbody, i have working to compress/decompress the packets. i know there are various schemes and facilities to do so in the freebsd, i have developed the compression facility myself. i am just a beginner in freebsd programming and overall in network programming. since i compress packet i add 2 byte custom header. now the problem is when the MTU sized packet is incompressible, i still add my 2 bytes which exceeds the MTU (1500) and the size becomes 1502. there was two options for me : either fragment the packet or increase the mtu. i don't want to fragment the packet as i think that is too much overhead for 2 bytes. rather i want to increase the mtu. i tried -->ifconfig xl1 mtu 1502 but it gave the message: -->ifconfig: ioctl (set mtu): invalid argument How can i increase the MTU ??? Will it have any effect whatsoever ??? i guess ethernet should support MTU of 1502. isn't it correct ?? help !! kamal __________________________________________ Yahoo! DSL – Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com From owner-freebsd-net@FreeBSD.ORG Fri Jan 6 18:02:17 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA4F816A420 for ; Fri, 6 Jan 2006 18:02:17 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DFCD43D49 for ; Fri, 6 Jan 2006 18:02:16 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k06I288U098718; Fri, 6 Jan 2006 10:02:08 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k06I28hJ098717; Fri, 6 Jan 2006 10:02:08 -0800 (PST) (envelope-from jmg) Date: Fri, 6 Jan 2006 10:02:07 -0800 From: John-Mark Gurney To: kamal kc Message-ID: <20060106180207.GE69162@funkthat.com> Mail-Followup-To: kamal kc , freebsd References: <20060106071807.87771.qmail@web30008.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060106071807.87771.qmail@web30008.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd Subject: Re: increasing the ethernet MTU greater than 1500 (1502) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 18:02:17 -0000 kamal kc wrote this message on Thu, Jan 05, 2006 at 23:18 -0800: > i tried > -->ifconfig xl1 mtu 1502 > > but it gave the message: > -->ifconfig: ioctl (set mtu): invalid argument > > How can i increase the MTU ??? > Will it have any effect whatsoever ??? > i guess ethernet should support MTU of 1502. isn't it > correct ?? Nope, for pre-gige, only 1500 MTU is supported... This was extended slightly to support vlan tagging, but I believe many of the drivers to magic behind the scenes to know when the vlan tagged packets are comming, and let them through... You could look at the drivers into fixing this.. If you have a good gige card, you can go to 9000 MTU and beyond... there is still the problem of the receiving station.. (and all switches, routers inbetween)... They must be able to support the larger MTU packet, otherwise, it coulde get dropped from the wire as too long of a packet... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@FreeBSD.ORG Fri Jan 6 19: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE40716A41F for ; Fri, 6 Jan 2006 19:52:30 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 580B443D46 for ; Fri, 6 Jan 2006 19:52:30 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from lapdance.yazzy.net (unknown [192.168.99.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yazzy.org (Postfix) with ESMTP id D3B693982E; Fri, 6 Jan 2006 20:52:49 +0100 (CET) Date: Fri, 6 Jan 2006 19:51:45 +0000 From: Marcin Jessa To: Karel Miklav Message-Id: <20060106195145.45616bef.lists@yazzy.org> In-Reply-To: <43BC57B9.1040309@lovetemple.net> References: <43BB5923.7040108@siol.net> <43BB637F.5050402@gmail.com> <20060104143659.04dd2174.lists@yazzy.org> <43BC57B9.1040309@lovetemple.net> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Direct routing 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, 06 Jan 2006 19:52:30 -0000 On Thu, 05 Jan 2006 00:18:17 +0100 Karel Miklav wrote: > Dennis and Marcin, > thanks very much for your replies. You're welcome. >I've also found the 'LVS on > FreeBSD' page at > http://dragon.linux-vs.org/~dragonfly/htm/lvs_freebsd.htm. I played with it on Linux before. How does it work, perform on FreeBSD? Could you share with your experience regardless how bad/good it may be? Marcin. From owner-freebsd-net@FreeBSD.ORG Fri Jan 6 23:23:34 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8704516A41F for ; Fri, 6 Jan 2006 23:23:34 +0000 (GMT) (envelope-from leimy2k@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E956A43D48 for ; Fri, 6 Jan 2006 23:23:33 +0000 (GMT) (envelope-from leimy2k@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so3429273nzo for ; Fri, 06 Jan 2006 15:23:33 -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; b=Ki7qBV6irNPbmkdBJZuvuInyX4UCrjQkPL7wy14eGO5j7G3zOIxvehq44PHpVriUE0NB0CpR+RVf3zrTR5TBwgKJA3Gl+IA9ly1f0CpWdwcBTVE8nYRFK5Tot3MwJz7QUS376kwPTyik04t9pLU4lCb0P8CDovsmWwod8YfcpHE= Received: by 10.36.36.12 with SMTP id j12mr2945005nzj; Fri, 06 Jan 2006 15:23:33 -0800 (PST) Received: by 10.36.41.7 with HTTP; Fri, 6 Jan 2006 15:23:33 -0800 (PST) Message-ID: <3e1162e60601061523k742d46cdreade7fb276232f13@mail.gmail.com> Date: Fri, 6 Jan 2006 15:23:33 -0800 From: David Leimbach To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: if_bridge FreeBSD 6.0 on a Broadcom interface not working 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, 06 Jan 2006 23:23:34 -0000 To whom it may concern. I've been using qemu with the vde port [until recently, the qemu port is to= o far ahead of the vde one now] on an x86 machine with FreeBSD 6 and using if_bridge to connect the tap0 interface with xl0 with great success. I tried to duplicate this configuration on a dual opteron machine that has Broadcom adapters and when I add the bge0 or bge1 interfaces to the bridge0 iface that I create I lose all connectivity. The moment I destroy the bridge0 interface, bge0 or bge1 as it may be begins responding again. I'm all for not supporting Broadcom here... I don't care for their business practices so much and will likely get another network card to work around this problem. I just thought I'd bring it up since I think if_bridge is really excellent otherwise! If you want/need more information I'll be glad to provide. Dave Leimbach From owner-freebsd-net@FreeBSD.ORG Fri Jan 6 23:45: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D8F416A41F for ; Fri, 6 Jan 2006 23:45:14 +0000 (GMT) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (e-gerbil.net [69.31.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB6D43D46 for ; Fri, 6 Jan 2006 23:45:13 +0000 (GMT) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (ras@localhost.e-gerbil.net [127.0.0.1]) by overlord.e-gerbil.net (8.13.3/8.13.3) with ESMTP id k06NjBgH094904; Fri, 6 Jan 2006 18:45:11 -0500 (EST) (envelope-from ras@overlord.e-gerbil.net) Received: (from ras@localhost) by overlord.e-gerbil.net (8.13.3/8.13.3/Submit) id k06NjBOZ094903; Fri, 6 Jan 2006 18:45:11 -0500 (EST) (envelope-from ras) Date: Fri, 6 Jan 2006 18:45:11 -0500 From: Richard A Steenbergen To: kamal kc , freebsd Message-ID: <20060106234511.GY826@overlord.e-gerbil.net> References: <20060106071807.87771.qmail@web30008.mail.mud.yahoo.com> <20060106180207.GE69162@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060106180207.GE69162@funkthat.com> User-Agent: Mutt/1.5.6i Cc: Subject: Re: increasing the ethernet MTU greater than 1500 (1502) 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, 06 Jan 2006 23:45:14 -0000 On Fri, Jan 06, 2006 at 10:02:07AM -0800, John-Mark Gurney wrote: > Nope, for pre-gige, only 1500 MTU is supported... This was extended > slightly to support vlan tagging, but I believe many of the drivers to > magic behind the scenes to know when the vlan tagged packets are comming, > and let them through... You could look at the drivers into fixing this.. > If you have a good gige card, you can go to 9000 MTU and beyond... > > there is still the problem of the receiving station.. (and all switches, > routers inbetween)... They must be able to support the larger MTU > packet, otherwise, it coulde get dropped from the wire as too long of > a packet... Technically speaking, the problem was not fixed by GigE or even 10GigE. The wonderful folks over at the IEEE feel there is no need to bring us out of the ethernet networking dark ages by defining any kind of standards for anything > 1500 bytes. We're left with a bunch of vendors who are each trying to do the right thing by picking random sizes ranging from 1518 (stock + 4 bytes for a single .1q tag) to 16384, but there are no real standards, no mechanisms for ensuring interoperability, no protocols for negotiating MTUs between networks, etc. GigE and beyond is statistically more likely to support some kind of jumbo frame just because it is newer, but the only way to find out is to ask the vendor/manufacturer. Lots of newer FastE cards support jumbos or some kind of mini jumbo too. There are still plenty of NICs and switches out there with no or very half-ass jumbo support though. -- Richard A Steenbergen http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 01:36:20 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E886A16A41F for ; Sat, 7 Jan 2006 01:36:20 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from dbmail-mx2.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D45A43D46 for ; Sat, 7 Jan 2006 01:36:18 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by dbmail-mx2.orcon.net.nz (8.13.2/8.13.2/Debian-1) with ESMTP id k071empa002495; Sat, 7 Jan 2006 14:40:48 +1300 Received: by heff.fud.org.nz (Postfix, from userid 1001) id BA80B2843B; Sat, 7 Jan 2006 14:36:27 +1300 (NZDT) Date: Sat, 7 Jan 2006 14:36:27 +1300 From: Andrew Thompson To: David Leimbach Message-ID: <20060107013627.GA82454@heff.fud.org.nz> References: <3e1162e60601061523k742d46cdreade7fb276232f13@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3e1162e60601061523k742d46cdreade7fb276232f13@mail.gmail.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on dbmail-mx2.orcon.net.nz X-Virus-Status: Clean Cc: freebsd-net@freebsd.org Subject: Re: if_bridge FreeBSD 6.0 on a Broadcom interface not working 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, 07 Jan 2006 01:36:21 -0000 On Fri, Jan 06, 2006 at 03:23:33PM -0800, David Leimbach wrote: > To whom it may concern. > > I've been using qemu with the vde port [until recently, the qemu port is too > far ahead of the vde one now] on an x86 machine with FreeBSD 6 and using > if_bridge to connect the tap0 interface with xl0 with great success. > > I tried to duplicate this configuration on a dual opteron machine that has > Broadcom adapters and when I add the bge0 or bge1 interfaces to the bridge0 > iface that I create I lose all connectivity. The moment I destroy the > bridge0 interface, bge0 or bge1 as it may be begins responding again. > The only thing the bridge does to the interface is put it in PROMISC mode, can you try using tcpdump or similar to see if that is whats causing the problem. Andrew From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 01:37: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AF2C16A41F for ; Sat, 7 Jan 2006 01:37:42 +0000 (GMT) (envelope-from leimy2k@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id B21F843D5D for ; Sat, 7 Jan 2006 01:37:37 +0000 (GMT) (envelope-from leimy2k@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so3445989nzo for ; Fri, 06 Jan 2006 17:37:37 -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=nAOKE8lM7SThOMX2p9X73auOXHzoN68YdyyKYkCXoQU1xJs3AdxBQorrxExraQeo5LmacGLrs1DKjKeT2oSYGI+sS7wBWMnM53kFF4A3PFuN7AEaL5JgelxHyZ2P4Ubu9CnSR2nIZE7reCulDGAfks8UQTn88ErsFstMwhG9vtM= Received: by 10.36.43.12 with SMTP id q12mr8867601nzq; Fri, 06 Jan 2006 17:37:36 -0800 (PST) Received: by 10.36.41.7 with HTTP; Fri, 6 Jan 2006 17:37:36 -0800 (PST) Message-ID: <3e1162e60601061737j70c0e594o2fe0adc00a5f6b65@mail.gmail.com> Date: Fri, 6 Jan 2006 17:37:36 -0800 From: David Leimbach To: Andrew Thompson In-Reply-To: <20060107013627.GA82454@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <3e1162e60601061523k742d46cdreade7fb276232f13@mail.gmail.com> <20060107013627.GA82454@heff.fud.org.nz> Cc: freebsd-net@freebsd.org Subject: Re: if_bridge FreeBSD 6.0 on a Broadcom interface not working 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, 07 Jan 2006 01:37:42 -0000 On 1/6/06, Andrew Thompson wrote: > On Fri, Jan 06, 2006 at 03:23:33PM -0800, David Leimbach wrote: > > To whom it may concern. > > > > I've been using qemu with the vde port [until recently, the qemu port i= s too > > far ahead of the vde one now] on an x86 machine with FreeBSD 6 and usin= g > > if_bridge to connect the tap0 interface with xl0 with great success. > > > > I tried to duplicate this configuration on a dual opteron machine that = has > > Broadcom adapters and when I add the bge0 or bge1 interfaces to the bri= dge0 > > iface that I create I lose all connectivity. The moment I destroy the > > bridge0 interface, bge0 or bge1 as it may be begins responding again. > > > > The only thing the bridge does to the interface is put it in PROMISC > mode, can you try using tcpdump or similar to see if that is whats > causing the problem. > > > Andrew > Thanks for the tip... I'll give it a shot and see what's going on. Dave From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 02:35: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 788BE16A41F for ; Sat, 7 Jan 2006 02:35:01 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: from web30001.mail.mud.yahoo.com (web30001.mail.mud.yahoo.com [68.142.200.64]) by mx1.FreeBSD.org (Postfix) with SMTP id 0779843D46 for ; Sat, 7 Jan 2006 02:35:00 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: (qmail 68516 invoked by uid 60001); 7 Jan 2006 02:35:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=XPoy8LSesbaPNbFUABieY5CnCZ4/eHdei6IMPKj21BOW3bChVag9u0HpSMWJ56nUGiq6Yd1kORzgyK3NneaHwJUcEoaErz+HEszBi8avBcqzE3ClBXxxJbaLud25XE3W1L/KUiJBJ8IkzD2X0HNVFuoRRvtFJPlA4b3b5v/ysoY= ; Message-ID: <20060107023500.68514.qmail@web30001.mail.mud.yahoo.com> Received: from [202.79.62.13] by web30001.mail.mud.yahoo.com via HTTP; Fri, 06 Jan 2006 18:35:00 PST Date: Fri, 6 Jan 2006 18:35:00 -0800 (PST) From: kamal kc To: freebsd In-Reply-To: <20060106234511.GY826@overlord.e-gerbil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: increasing the ethernet MTU greater than 1500 (1502) 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, 07 Jan 2006 02:35:01 -0000 --- Richard A Steenbergen wrote: > On Fri, Jan 06, 2006 at 10:02:07AM -0800, John-Mark > Gurney wrote: > > Nope, for pre-gige, only 1500 MTU is supported... > This was extended > > slightly to support vlan tagging, but I believe > many of the drivers to > > If you have a good gige card, you can go to 9000 > MTU and beyond... > Technically speaking, the problem was not fixed by > GigE or even 10GigE. > The wonderful folks over at the IEEE feel there is > no need to bring us out > of the ethernet networking dark ages by defining any > kind of standards for > anything > 1500 bytes. We're left with a bunch of > vendors who are each > trying to do the right thing by picking random sizes > ranging from 1518 > (stock + 4 bytes for a single .1q tag) to 16384, but > there are no real > standards, no mechanisms for ensuring > interoperability, no protocols for > negotiating MTUs between networks, etc. Lots of newer FastE cards > support jumbos or some kind > of mini jumbo too. There are still plenty of NICs > and switches out there > with no or very half-ass jumbo support though. thanks for providing the insight. I would try with GigE next time. since it seems a bad option to try MTU larger than 1500 in 10/100 Mbps ethernet i tried another option to solve my problem. Now i don't add additional header(2 bytes) to distinguish the packets that were processed. I rather tried for protocol mapping. This is what i did, i mapped the protocol (in the protocol field of the ip header) 0..56 to 138..194 if compressed 0..56 to 195..251 if uncompressed with this simple protocol mapping i could only compress 57 protocol data. I guess the protocols 138 to 251 will not be used for couple of years. OR Is there any slighest possibility ???? thanks, kamal __________________________________________ Yahoo! DSL – Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 03:53: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29C1D16A41F for ; Sat, 7 Jan 2006 03:53:15 +0000 (GMT) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (e-gerbil.net [69.31.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1A6543D45 for ; Sat, 7 Jan 2006 03:53:14 +0000 (GMT) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (ras@localhost.e-gerbil.net [127.0.0.1]) by overlord.e-gerbil.net (8.13.3/8.13.3) with ESMTP id k073rAee096735; Fri, 6 Jan 2006 22:53:10 -0500 (EST) (envelope-from ras@overlord.e-gerbil.net) Received: (from ras@localhost) by overlord.e-gerbil.net (8.13.3/8.13.3/Submit) id k073rAmA096734; Fri, 6 Jan 2006 22:53:10 -0500 (EST) (envelope-from ras) Date: Fri, 6 Jan 2006 22:53:10 -0500 From: Richard A Steenbergen To: kamal kc Message-ID: <20060107035310.GB826@overlord.e-gerbil.net> References: <20060106234511.GY826@overlord.e-gerbil.net> <20060107023500.68514.qmail@web30001.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060107023500.68514.qmail@web30001.mail.mud.yahoo.com> User-Agent: Mutt/1.5.6i Cc: freebsd Subject: Re: increasing the ethernet MTU greater than 1500 (1502) 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, 07 Jan 2006 03:53:15 -0000 On Fri, Jan 06, 2006 at 06:35:00PM -0800, kamal kc wrote: > > thanks for providing the insight. I would try > with GigE next time. > > since it seems a bad option to try MTU larger than > 1500 in 10/100 Mbps ethernet i tried another option to > solve my problem. Also try any number of other $5 10/100 NICs with vlan/mini-jumbo capabilities. > Now i don't add additional header(2 bytes) to > distinguish > the packets that were processed. I rather tried for > protocol mapping. > > This is what i did, > > i mapped the protocol (in the protocol field of the ip > header) > > 0..56 to 138..194 if compressed > 0..56 to 195..251 if uncompressed > > with this simple protocol mapping i could only > compress > 57 protocol data. > > I guess the protocols 138 to 251 will not be used for > couple of years. > OR Is there any slighest possibility ???? If you're sure you're not going to deal with fragments, and you're ok with violating rfc's and hacking the headers to suit your needs, why not steal the id and/or frag offset fields? -- Richard A Steenbergen http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 07:45: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D45E416A447 for ; Sat, 7 Jan 2006 07:45:20 +0000 (GMT) (envelope-from fooler@skyinet.net) Received: from smtp1.skyinet.net (smtp1.skyinet.net [202.78.97.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E1743D46 for ; Sat, 7 Jan 2006 07:45:19 +0000 (GMT) (envelope-from fooler@skyinet.net) Received: from fooler (fooler.ilo.skyinet.net [202.78.118.66]) by smtp1.skyinet.net (Postfix) with SMTP id F1F84582C4; Sat, 7 Jan 2006 15:45:18 +0800 (PHT) Message-ID: <018e01c6135e$4c25b130$42764eca@ilo.skyinet.net> From: "fooler" To: "kamal kc" , "freebsd" References: <20060106071807.87771.qmail@web30008.mail.mud.yahoo.com> Date: Sat, 7 Jan 2006 15:45:14 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: Subject: Re: increasing the ethernet MTU greater than 1500 (1502) 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, 07 Jan 2006 07:45:22 -0000 ----- Original Message ----- From: "kamal kc" To: "freebsd" Sent: Friday, January 06, 2006 3:18 PM Subject: increasing the ethernet MTU greater than 1500 (1502) > i don't want to fragment the packet as i think > that is too much overhead for 2 bytes. rather i > want to increase the mtu. why increase the mtu when you can decrease it? one good example is the PPPoE... default mtu size of pppoe is 1492 because of the 6 bytes pppoe header and 2 bytes ppp protocol id to fit into the default 1500 mtu of ethernet.... therefore you set your mtu to 1498 to fit your 2 bytes extra header :-> in that way you are safe from any violation of rfcs... fooler. From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 13:35: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 [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F5E716A41F for ; Sat, 7 Jan 2006 13:35:40 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [87.74.4.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F2B143D45 for ; Sat, 7 Jan 2006 13:35:39 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (genius.tao.org.uk [87.74.4.41]) by mailhost.tao.org.uk (Postfix) with ESMTP id E09045C34 for ; Sat, 7 Jan 2006 13:35:36 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 100) id 4E51B40FF; Sat, 7 Jan 2006 13:35:37 +0000 (GMT) Date: Sat, 7 Jan 2006 13:35:37 +0000 From: Josef Karthauser To: freebsd-net@freebsd.org Message-ID: <20060107133537.GA1035@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: Crashes with aue0 and FBSD-6.X 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, 07 Jan 2006 13:35:40 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, I've just upgraded a box from 5 to 6 and am having all sorts of woes with the aue interface. (SHORT_TRANSFERS followed by panic). Anyone know who to speak to about aue problems with RELENG_6? Joe --=20 Josef Karthauser (joe@tao.org.uk) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an= d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iEYEARECAAYFAkO/w6gACgkQXVIcjOaxUBZVwQCg4v+oPbIkJPQxAvgNy0cJI5u3 O0UAn3Nhqn6MqQ85cwFGGiOPacYOtwPB =AY6j -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf--