From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 09:31:35 2006 Return-Path: X-Original-To: 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 11D2516A403 for ; Sun, 17 Sep 2006 09:31:35 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id B74E643D45 for ; Sun, 17 Sep 2006 09:31:34 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id k8H9VRpN093447; Sun, 17 Sep 2006 02:31:28 -0700 (PDT) Date: Sun, 17 Sep 2006 18:31:27 +0900 Message-ID: From: gnn@freebsd.org To: "Matt Reimer" In-Reply-To: References: User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.7.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: net@freebsd.org Subject: Re: Can someone take a look at PR 89061 (ipv6 autoconfigure 6to4) 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, 17 Sep 2006 09:31:35 -0000 At Fri, 8 Sep 2006 17:14:18 -0700, Matt Reimer wrote: > > Can someone take a look at PR 89061 > (http://www.freebsd.org/cgi/query-pr.cgi?pr=89061). It contains a > patch adding an /etc/rc.conf knob to autoconfigure an RFC 3068 6to4 > address. > The comments in the PR indicate that awk can't be used at that point, so if that's true, while I think it's a good idea, the implementation will have to changed. From an IPv6 standpoint it's fine though. Later, George From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 10:59:48 2006 Return-Path: X-Original-To: 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 45E9916A417 for ; Sun, 17 Sep 2006 10:59:48 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (bewilderbeast.blackhelicopters.org [198.22.63.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF32843D5D for ; Sun, 17 Sep 2006 10:59:47 +0000 (GMT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (mwlucas@localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.12.10/8.12.10) with ESMTP id k8HAxkNG052475; Sun, 17 Sep 2006 06:59:46 -0400 (EDT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.12.10/8.12.10/Submit) id k8HAxkwt052474; Sun, 17 Sep 2006 06:59:46 -0400 (EDT) (envelope-from mwlucas) Date: Sun, 17 Sep 2006 06:59:46 -0400 From: "Michael W. Lucas" To: Robert Blacquiere Message-ID: <20060917105946.GA52413@bewilderbeast.blackhelicopters.org> References: <20060907025648.GA22003@bewilderbeast.blackhelicopters.org> <20060907091520.GB87346@bombur.guldan.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060907091520.GB87346@bombur.guldan.demon.nl> User-Agent: Mutt/1.4.1i X-Spam-Score: (0) X-Scanned-By: MIMEDefang 2.39 Cc: "Michael W. Lucas" , net@freebsd.org Subject: Re: problems with ng_fec 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, 17 Sep 2006 10:59:48 -0000 Thank you, this was exactly right. Just had to wait for maintenance day to try it. (copying the list for the archives) On Thu, Sep 07, 2006 at 11:15:20AM +0200, Robert Blacquiere wrote: > On Wed, Sep 06, 2006 at 10:56:48PM -0400, Michael W. Lucas wrote: > > > > Hi, > > > > (asked this first on -questions, but it seems that this exceeds their > > wisdom...) > > > > I'm using a recent -current on amd64, and trying to use ng_fec to > > hopefully provide a wide-bandwidth connection with cable-level > > redundancy, and instead I get get errors and sporadic connectivity. > > > > I configured fec0 as such: > > > > #!/bin/sh > > > > ngctl mkpeer fec dummy fec > > ngctl msg fec0: add_iface '"em3"' > > ngctl msg fec0: add_iface '"em7"' > > ngctl msg fec0: set_mode_inet > > ifconfig fec0 up > > ifconfig fec0 inet 10.184.1.19 netmask 255.255.0.0 > > > > The Cisco 6509 I was attached to had ports configured with: > > > > switchport trunk encapsulation dot1q > > switchport mode trunk > > You need a port channel interface and make the switchports member of the > port channel. > > some thing like: > > ! > interface Port-channel1 > description 2 combined interfaces to freebsd fec0 > switchport > ! only needed for vlan tagging... > ! switchport trunk encapsulation dot1q > ! switchport trunk allowed vlan x,y,z,... > ! switchport mode trunk > ! mtu 9216 > no ip address > > interface GigabitEthernet5/1 > description UPLINK #1 > switchport > ! needer only for vlan tagging > ! switchport trunk encapsulation dot1q > ! switchport trunk allowed vlan x,y,z,... > ! switchport mode trunk > ! mtu 9216 > no ip address > no cdp enable > channel-group 1 mode on > > interface GigabitEthernet5/2 > description UPLINK #2 > switchport > ! needer only for vlan tagging > ! switchport trunk encapsulation dot1q > ! switchport trunk allowed vlan x,y,z,... > ! switchport mode trunk > ! mtu 9216 > no ip address > no cdp enable > channel-group 1 mode on > > > > > > When I tried to ping various hosts, however, I got sporadic and > > intermittent connectivity to other hosts on the network. > > This is spanning tree behavour.... > > > > > Dmesg follows after log entries. > > > > Any suggestions? > > > > Thanks, > > ==ml > > Hopeful this will give you a head start in configuring the cisco. > > Robert > -- > Microsoft: Where do you want to go today? > Linux: Where do you want to go tomorrow? > FreeBSD: Are you guys coming or what? > OpenBSD: Hey guys you left some holes out there! -- Michael W. Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.BlackHelicopters.org/~mwlucas/ Latest book: PGP & GPG -- http://www.pgpandgpg.com "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 11:11:27 2006 Return-Path: X-Original-To: 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 BC30216A587; Sun, 17 Sep 2006 11:11:27 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id B957243D60; Sun, 17 Sep 2006 11:11:26 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:PTVemcoM03+nrhJE8PglxlnNyBCTQEWiUCLbyF74+FNaSLapT3cG5sxqq6bcgW9C@kasuga-iwi.mahoroba.org [IPv6:2001:2f0:104:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.8/8.13.8) with ESMTP/inet6 id k8HBAmi1084423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Sep 2006 20:10:48 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 17 Sep 2006 20:10:47 +0900 Message-ID: From: Hajimu UMEMOTO To: "Julian Stacey" In-Reply-To: <200609141344.k8EDiI42092840@flat.berklix.org> References: <200609141344.k8EDiI42092840@flat.berklix.org> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-pc-freebsd) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.2-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0a6 (ameno.mahoroba.org [IPv6:2001:2f0:104:8010::1]); Sun, 17 Sep 2006 20:10:49 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.5 X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on ameno.mahoroba.org Cc: Gary Jennejohn , brian@Awfulhak.org, net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 17 Sep 2006 11:11:27 -0000 Hi, >>>>> On Thu, 14 Sep 2006 15:44:18 +0200 (CEST) >>>>> "Julian Stacey" said: jhs> I'm not clear if this is a bug or a config error: jhs> It seems though my /usr/sbin/ppp was moving traffic jhs> to & from internet, it was only listening for commands jhs> (not data) on ipv6, not ipv4, thus I could not type commands jhs> like dial & drop, unless instead of running ppp -auto jhs> instead I invoked ppp manually in foreground on localhost. As far as I read the source of ppp(8), it only listen on an IPv6, and expects to listen on an IPv4 through an IPv4-mapped IPv6 address. However, an IPv4-mapped IPv6 address feature is disabled by default. ppp(8) should be rewritten to listen on both an IPv4 and an IPv6. But, it is slightly complex. So, I made a patch to enable an IPv4-mapped IPv6 address only for the socket that ppp(8) is listening on. I have no environment for testing this. Could you try this patch? Index: usr.sbin/ppp/server.c diff -u -p usr.sbin/ppp/server.c.orig usr.sbin/ppp/server.c --- usr.sbin/ppp/server.c.orig Sun Sep 5 10:46:52 2004 +++ usr.sbin/ppp/server.c Sun Sep 17 19:54:43 2006 @@ -346,6 +346,13 @@ server_TcpOpen(struct bundle *bundle, u_ goto failed; } +#ifndef NOINET6 + if (probe.ipv6_available) { + int off = 0; + setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, (char *)&off, sizeof(off)); + } +#endif + setsockopt(s, SOL_SOCKET, SO_REUSEADDR, &s, sizeof s); if (bind(s, (struct sockaddr *)&ss, sz) < 0) { log_Printf(LogWARN, "Tcp: bind: %s\n", strerror(errno)); Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 12:55: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 546CD16A416 for ; Sun, 17 Sep 2006 12:55:42 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from leia.fdn.fr (ns0.fdn.org [80.67.169.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0426443D58 for ; Sun, 17 Sep 2006 12:55:39 +0000 (GMT) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by leia.fdn.fr (8.13.3/8.13.3/FDN) with ESMTP id k8HCta2R025595 for ; Sun, 17 Sep 2006 14:55:37 +0200 Received: from jayce.zen.inc (jayce.zen.inc [192.168.1.7]) by smtp.zeninc.net (smtpd) with ESMTP id 0337F3F17 for ; Sun, 17 Sep 2006 14:55:30 +0200 (CEST) Received: by jayce.zen.inc (Postfix, from userid 1000) id CDD302E1FD; Sun, 17 Sep 2006 14:55:31 +0200 (CEST) Date: Sun, 17 Sep 2006 14:55:31 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20060917125531.GA1611@jayce.zen.inc> References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: All mail clients suck. This one just sucks less. Subject: Re: FAST_IPSEC NAT-T support 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, 17 Sep 2006 12:55:42 -0000 On Fri, Sep 15, 2006 at 12:07:58PM -0400, Scott Ullrich wrote: [....] > Next problem that I have encountered (with FAST_IPSEC) is: > > # /sbin/setkey -D > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > > Let me know if I can do any further testing, still waiting for status > reports from a few of the pfSense users, but IPSEC seems to work okay > even with this small cosmetic setkey issue. Make sure your ipsec-tools port have been recompiled after your system has been patched / compiled / upgraded, and use /usr/local/sbin/setkey. FreeBSD's setkey does not (yet ?) support NAT-T extensions at all. Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 13:57:33 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B79316A407 for ; Sun, 17 Sep 2006 13:57:33 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41B0143D55 for ; Sun, 17 Sep 2006 13:57:31 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 64046 invoked from network); 17 Sep 2006 13:40:29 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 17 Sep 2006 13:40:29 -0000 Message-ID: <450D544E.3070500@freebsd.org> Date: Sun, 17 Sep 2006 15:57:34 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------050000070406050000030805" Cc: freebsd-net@freebsd.org Subject: HEADS-UP: VLAN tag changes committed 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, 17 Sep 2006 13:57:33 -0000 This is a multi-part message in MIME format. --------------050000070406050000030805 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit FYI. --------------050000070406050000030805 Content-Type: message/rfc822; name*0="cvs commit: src/sys/dev/bce if_bce.c src/sys/dev/bge if_bge.c "; name*1=" src/sys/dev/em if_em.c src/sys/dev/ixgb if_ixgb.c src/sys/"; name*2="dev/nfe if_nfe.c src/sys/dev/nge if_nge.c src/sys/dev/re"; name*3=" if_re.c src/sys/dev/stge if_stge.c src/sys/dev/ti if_ti"; name*4=".c src/sys/dev/txp ..." Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename*0="cvs commit: src/sys/dev/bce if_bce.c src/sys/dev/bge if_bge."; filename*1="c src/sys/dev/em if_em.c src/sys/dev/ixgb if_ixgb.c "; filename*2="src/sys/dev/nfe if_nfe.c src/sys/dev/nge if_nge.c sr"; filename*3="c/sys/dev/re if_re.c src/sys/dev/stge if_stge.c src/"; filename*4="sys/dev/ti if_ti.c src/sys/dev/txp ..." X-Account-Key: account3 Return-Path: Delivered-To: andre@networx.ch Received: (qmail 63885 invoked from network); 17 Sep 2006 13:17:10 -0000 Received: from mx2.freebsd.org ([216.136.204.119]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 17 Sep 2006 13:17:10 -0000 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 96C865C2AA for ; Sun, 17 Sep 2006 13:33:33 +0000 (GMT) (envelope-from owner-src-committers@FreeBSD.org) Received: by hub.freebsd.org (Postfix) id 1039F16A47C; Sun, 17 Sep 2006 13:33:32 +0000 (UTC) Delivered-To: andre@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 538) id 0027A16A40F; Sun, 17 Sep 2006 13:33:31 +0000 (UTC) X-Original-To: src-committers@FreeBSD.org Delivered-To: src-committers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8DCE16A407; Sun, 17 Sep 2006 13:33:30 +0000 (UTC) (envelope-from andre@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E56D43D46; Sun, 17 Sep 2006 13:33:30 +0000 (GMT) (envelope-from andre@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.6/8.13.6) with ESMTP id k8HDXUvq029747; Sun, 17 Sep 2006 13:33:30 GMT (envelope-from andre@repoman.freebsd.org) Received: (from andre@localhost) by repoman.freebsd.org (8.13.6/8.13.4/Submit) id k8HDXUht029746; Sun, 17 Sep 2006 13:33:30 GMT (envelope-from andre) Message-Id: <200609171333.k8HDXUht029746@repoman.freebsd.org> From: Andre Oppermann Date: Sun, 17 Sep 2006 13:33:30 +0000 (UTC) To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/dev/bce if_bce.c src/sys/dev/bge if_bge.c src/sys/dev/em if_em.c src/sys/dev/ixgb if_ixgb.c src/sys/dev/nfe if_nfe.c src/sys/dev/nge if_nge.c src/sys/dev/re if_re.c src/sys/dev/stge if_stge.c src/sys/dev/ti if_ti.c src/sys/dev/txp ... X-FreeBSD-CVS-Branch: HEAD Sender: owner-src-committers@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG andre 2006-09-17 13:33:30 UTC FreeBSD src repository Modified files: sys/dev/bce if_bce.c sys/dev/bge if_bge.c sys/dev/em if_em.c sys/dev/ixgb if_ixgb.c sys/dev/nfe if_nfe.c sys/dev/nge if_nge.c sys/dev/re if_re.c sys/dev/stge if_stge.c sys/dev/ti if_ti.c sys/dev/txp if_txp.c sys/dev/vge if_vge.c sys/net if_vlan.c if_vlan_var.h sys/net80211 ieee80211_input.c ieee80211_output.c sys/netgraph ng_vlan.c sys/sys mbuf.h Log: Move ethernet VLAN tags from mtags to its own mbuf packet header field m_pkthdr.ether_vlan. The presence of the M_VLANTAG flag on the mbuf signifies the presence and validity of its content. Drivers that support hardware VLAN tag stripping fill in the received VLAN tag (containing both vlan and priority information) into the ether_vtag mbuf packet header field: m->m_pkthdr.ether_vtag = vlan_id; /* ntohs()? */ m->m_flags |= M_VLANTAG; to mark the packet m with the specified VLAN tag. On output the driver should check the mbuf for the M_VLANTAG flag to see if a VLAN tag is present and valid: if (m->m_flags & M_VLANTAG) { ... = m->m_pkthdr.ether_vtag; /* htons()? */ ... pass tag to hardware ... } VLAN tags are stored in host byte order. Byte swapping may be necessary. (Note: This driver conversion was mechanic and did not add or remove any byte swapping in the drivers.) Remove zone_mtag_vlan UMA zone and MTAG_VLAN definition. No more tag memory allocation have to be done. Reviewed by: thompsa, yar Sponsored by: TCP/IP Optimization Fundraise 2005 Revision Changes Path 1.8 +4 -7 src/sys/dev/bce/if_bce.c 1.146 +4 -6 src/sys/dev/bge/if_bge.c 1.145 +7 -12 src/sys/dev/em/if_em.c 1.20 +13 -4 src/sys/dev/ixgb/if_ixgb.c 1.5 +5 -16 src/sys/dev/nfe/if_nfe.c 1.89 +5 -8 src/sys/dev/nge/if_nge.c 1.75 +6 -9 src/sys/dev/re/if_re.c 1.3 +6 -6 src/sys/dev/stge/if_stge.c 1.125 +4 -7 src/sys/dev/ti/if_ti.c 1.42 +4 -7 src/sys/dev/txp/if_txp.c 1.26 +5 -8 src/sys/dev/vge/if_vge.c 1.115 +5 -17 src/sys/net/if_vlan.c 1.25 +16 -39 src/sys/net/if_vlan_var.h 1.95 +2 -10 src/sys/net80211/ieee80211_input.c 1.43 +2 -3 src/sys/net80211/ieee80211_output.c 1.4 +8 -8 src/sys/netgraph/ng_vlan.c 1.196 +1 -4 src/sys/sys/mbuf.h --------------050000070406050000030805-- From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 15:58: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 C6D4D16A416 for ; Sun, 17 Sep 2006 15:58:20 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2F5843D5D for ; Sun, 17 Sep 2006 15:58:19 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so320850uge for ; Sun, 17 Sep 2006 08:58:18 -0700 (PDT) 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=K17sfXQtSkZKNF81hRIcvt8W42nhfSxajAsQ/KOpfLA9CL13krxKf1MO5F3OkOCTfdAykqkbJriSmVSAZUxzQxE+N53KLSFs8udbElTxuqwdOKBI1e/FmMjpoZup4SzKflRcCFRfz4yHXyhLnjMgQe0LaHJ725Dif4ggkpN2c9g= Received: by 10.67.97.7 with SMTP id z7mr6666752ugl; Sun, 17 Sep 2006 08:58:18 -0700 (PDT) Received: by 10.67.105.8 with HTTP; Sun, 17 Sep 2006 08:58:17 -0700 (PDT) Message-ID: Date: Sun, 17 Sep 2006 11:58:17 -0400 From: "Scott Ullrich" To: "VANHULLEBUS Yvan" In-Reply-To: <20060917125531.GA1611@jayce.zen.inc> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> Cc: freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support 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, 17 Sep 2006 15:58:20 -0000 On 9/17/06, VANHULLEBUS Yvan wrote: > Make sure your ipsec-tools port have been recompiled after your system > has been patched / compiled / upgraded, and use > /usr/local/sbin/setkey. > > FreeBSD's setkey does not (yet ?) support NAT-T extensions at all. I tried both /sbin/setkey and /usr/locals/bin/setkey and both result in the same Invalid extension type errors. builder# ls -la /sbin/setkey -r-xr-xr-x 1 root wheel 56456 Jun 16 03:49 /sbin/setkey builder# ls -la /usr/local/sbin/setkey -r-xr-xr-x 1 root wheel 86472 Sep 17 15:54 /usr/local/sbin/setkey # /sbin/setkey -D Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type # /usr/local/sbin/setkey -D Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Invalid extension type Can you think of anything else to try? I re-compiled ipsec-tools on the same host before sending this. Thanks! From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 18:28:55 2006 Return-Path: X-Original-To: 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 3D89D16A403; Sun, 17 Sep 2006 18:28:55 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6D9B43D67; Sun, 17 Sep 2006 18:28:53 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A7449.dip.t-dialin.net [84.154.116.73]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8HISjpj075018; Sun, 17 Sep 2006 20:28:45 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id k8HISraK005866; Sun, 17 Sep 2006 20:28:54 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8HISrY9092923; Sun, 17 Sep 2006 20:28:53 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609171828.k8HISrY9092923@fire.jhs.private> To: Hajimu UMEMOTO In-reply-to: References: <200609141344.k8EDiI42092840@flat.berklix.org> Comments: In-reply-to Hajimu UMEMOTO message dated "Sun, 17 Sep 2006 20:10:47 +0900." Date: Sun, 17 Sep 2006 20:28:53 +0200 From: "Julian H. Stacey" Cc: Gary Jennejohn , brian@Awfulhak.org, net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 17 Sep 2006 18:28:55 -0000 > I have no environment for testing this. Could you try this patch? Yes certainly, thanks a lot, delighted to get a reply & will report back soon. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 18:40:03 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8038216A403 for ; Sun, 17 Sep 2006 18:40:03 +0000 (UTC) (envelope-from anton@abutsyk.sumy.ua) Received: from mail.etsplus.net (cable-tv.sumy.ua [193.110.17.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD70343D5A for ; Sun, 17 Sep 2006 18:40:02 +0000 (GMT) (envelope-from anton@abutsyk.sumy.ua) Received: (qmail 86390 invoked by uid 0); 17 Sep 2006 18:40:01 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.etsplus.net X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled Received: from unknown (HELO ?10.0.161.118?) (10.0.161.118) by 0 with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Sep 2006 18:40:00 -0000 Message-ID: <450D9680.2020700@abutsyk.sumy.ua> Date: Sun, 17 Sep 2006 21:40:00 +0300 From: Anton Butsyk User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: kevent/kqueue http socks 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: Sun, 17 Sep 2006 18:40:03 -0000 Hi list. I've found bsdproxy using kevent/kqueue(2) system calls. Is there any http/https and/or socks proxy using this mechanism? Thanks From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 19:07:11 2006 Return-Path: X-Original-To: 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 84FA816A40F; Sun, 17 Sep 2006 19:07:11 +0000 (UTC) (envelope-from brian@Awfulhak.org) Received: from storm.uk.FreeBSD.org (storm.uk.FreeBSD.org [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7FF843D55; Sun, 17 Sep 2006 19:07:10 +0000 (GMT) (envelope-from brian@Awfulhak.org) Received: from gw.Awfulhak.org (root@gw.lan.Awfulhak.org [172.16.0.1]) by storm.uk.FreeBSD.org (8.13.8/8.13.8) with ESMTP id k8HJ77ue015312; Sun, 17 Sep 2006 20:07:07 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from dev.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5]) by gw.Awfulhak.org (8.13.6/8.13.6) with ESMTP id k8HJ72PW055457; Sun, 17 Sep 2006 12:07:02 -0700 (PDT) (envelope-from brian@Awfulhak.org) Date: Sun, 17 Sep 2006 12:07:01 -0700 From: Brian Somers To: Hajimu UMEMOTO Message-ID: <20060917120701.4d8eb7ec@dev.lan.Awfulhak.org> In-Reply-To: References: <200609141344.k8EDiI42092840@flat.berklix.org> X-Mailer: Sylpheed-Claws 2.4.0 (GTK+ 2.8.20; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Gary Jennejohn , Julian Stacey , net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 17 Sep 2006 19:07:11 -0000 On Sun, 17 Sep 2006 20:10:47 +0900 Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Thu, 14 Sep 2006 15:44:18 +0200 (CEST) > >>>>> "Julian Stacey" said: > > jhs> I'm not clear if this is a bug or a config error: > jhs> It seems though my /usr/sbin/ppp was moving traffic > jhs> to & from internet, it was only listening for commands > jhs> (not data) on ipv6, not ipv4, thus I could not type commands > jhs> like dial & drop, unless instead of running ppp -auto > jhs> instead I invoked ppp manually in foreground on localhost. > > As far as I read the source of ppp(8), it only listen on an IPv6, and > expects to listen on an IPv4 through an IPv4-mapped IPv6 address. > However, an IPv4-mapped IPv6 address feature is disabled by default. > ppp(8) should be rewritten to listen on both an IPv4 and an IPv6. > But, it is slightly complex. So, I made a patch to enable an > IPv4-mapped IPv6 address only for the socket that ppp(8) is listening > on. > I have no environment for testing this. Could you try this patch? > > Index: usr.sbin/ppp/server.c > diff -u -p usr.sbin/ppp/server.c.orig usr.sbin/ppp/server.c > --- usr.sbin/ppp/server.c.orig Sun Sep 5 10:46:52 2004 > +++ usr.sbin/ppp/server.c Sun Sep 17 19:54:43 2006 > @@ -346,6 +346,13 @@ server_TcpOpen(struct bundle *bundle, u_ > goto failed; > } > > +#ifndef NOINET6 > + if (probe.ipv6_available) { > + int off = 0; > + setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, (char *)&off, sizeof(off)); > + } > +#endif > + > setsockopt(s, SOL_SOCKET, SO_REUSEADDR, &s, sizeof s); > if (bind(s, (struct sockaddr *)&ss, sz) < 0) { > log_Printf(LogWARN, "Tcp: bind: %s\n", strerror(errno)); > > > Sincerely, AFAIR I had trouble getting that code to work and was advised at the time that I'd just get the mapped port for free. I haven't been using IPv6 on production machines for some time, so I haven't seen the problem :( It'd be great if you'd commit the patch if Julian says it works ok for him. Cheers. -- Brian Somers Don't _EVER_ lose your sense of humour ! From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 19:21: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 72FB316A40F for ; Sun, 17 Sep 2006 19:21:11 +0000 (UTC) (envelope-from lists@wm-access.no) Received: from lakepoint.domeneshop.no (lakepoint.domeneshop.no [194.63.248.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC8443D5E for ; Sun, 17 Sep 2006 19:21:09 +0000 (GMT) (envelope-from lists@wm-access.no) Received: from [192.168.4.8] (nets.arcticwireless.no [194.19.37.80]) (authenticated bits=0) by lakepoint.domeneshop.no (8.13.8/8.13.8) with ESMTP id k8HJKedt001344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 17 Sep 2006 21:20:41 +0200 Message-ID: <450D9FE2.5030902@wm-access.no> Date: Sun, 17 Sep 2006 21:20:02 +0200 From: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Sam Leffler References: <44F4CF17.8060203@xs4all.nl> <44F70983.40705@errno.com> <44F71402.1060405@xs4all.nl> <44F7558A.4030907@errno.com> <450B48C2.7030501@xs4all.nl> <450C21B4.5030703@errno.com> In-Reply-To: <450C21B4.5030703@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, Hans Nieser Subject: Re: iwi discarding oversized packets while mtu=1500 for src/dst 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, 17 Sep 2006 19:21:11 -0000 Sam Leffler wrote: > Hans Nieser wrote: >> Sam Leffler wrote: >>> Hans Nieser wrote: >>> >>>> root@aphax-laptop:~# uname -a >>>> FreeBSD aphax-laptop.lan 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Thu May= 11 >>>> 07:17:09 CEST 2006 >>>> root@aphax-laptop.nieser.local:/usr/obj/usr/src/sys/APHAX-LAPTOP i3= 86 >>> Are you running the iwi driver that came with 6.1-release? If so it = has >>> numerous problems that have been fixed in 6-STABLE and HEAD. I'm not= >>> sure how best to update your system except by going to 6-STABLE via a= >>> src upgrade. >> Today I have upgraded my laptop to 6-STABLE, but unfortunately the >> problems remain. I don't even know wether iwi is to blame, because I c= an't >> figure out wether perhaps xl on my server really is sending out too la= rge >> packets. >> >> That is, so far I've been assuming that an mtu of 1500 may not mean th= at >> there's exactly 1500 bytes going over the wire (overhead of protocols = to >> which the mtu doesn't apply or something, I dunno, I'm no networking >> expert obviously :), because xl is definitely sending out packets of 1= 518 >> bytes. Which iwi on my laptop doesn't like, but the NIC in my desktop >> machine (which runs Linux) has no problem with. Maybe someone can tell= me >> which of the machines is in error here, at least I'd know what to blam= e :( >> >> The fact that my Linux box doesn't discard these packages coming from = my >> server made me suspicious of iwi initially, but maybe iwi is doing not= hing >> wrong and my Linux box is simply willing to accept these oversized pac= kets. >> >=20 > I can't speak to linux but an mtu of 1500 will cause a 1518 byte packet= > to be discarded. I don't recall what your problem was but if the iwi > driver is receiving the frame and passing it up only to be discarded by= > the 802.3 layer then you've received a frame that's too large and you > should look at the sender side for why it's being generated. If you > don't want to do that you can probably just up the mtu on iwi and let > the frame through. >=20 This does sound awfully lot like the driver doesn't strip the 4 byte checksum of a basic 802.[23] ethernet frame. My initial thought was that it was a vlan frame but the frame protocol indicates it's an IP packet. Perhaps it's a frame that slips through the AP's checks on it's way out to the wireless? --=20 Sten Daniel S=F8rsdal From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 19:57:38 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8A7316A40F for ; Sun, 17 Sep 2006 19:57:38 +0000 (UTC) (envelope-from h.nieser@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40DE743D60 for ; Sun, 17 Sep 2006 19:57:38 +0000 (GMT) (envelope-from h.nieser@xs4all.nl) Received: from [192.168.1.64] (aphax.nl [82.92.29.227]) by smtp-vbr9.xs4all.nl (8.13.6/8.13.6) with ESMTP id k8HJvZRQ056979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Sep 2006 21:57:36 +0200 (CEST) (envelope-from h.nieser@xs4all.nl) Message-ID: <450DA861.7030507@xs4all.nl> Date: Sun, 17 Sep 2006 21:56:17 +0200 From: Hans Nieser User-Agent: Thunderbird 1.5.0.5 (X11/20060910) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= References: <44F4CF17.8060203@xs4all.nl> <44F70983.40705@errno.com> <44F71402.1060405@xs4all.nl> <44F7558A.4030907@errno.com> <450B48C2.7030501@xs4all.nl> <450C21B4.5030703@errno.com> <450D9FE2.5030902@wm-access.no> In-Reply-To: <450D9FE2.5030902@wm-access.no> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-net@freebsd.org Subject: Re: iwi discarding oversized packets while mtu=1500 for src/dst 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, 17 Sep 2006 19:57:38 -0000 Sten Daniel Sørsdal wrote: > Sam Leffler wrote: >> Hans Nieser wrote: >>> Sam Leffler wrote: >>>> Hans Nieser wrote: >>>> >>>>> root@aphax-laptop:~# uname -a >>>>> FreeBSD aphax-laptop.lan 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Thu May 11 >>>>> 07:17:09 CEST 2006 >>>>> root@aphax-laptop.nieser.local:/usr/obj/usr/src/sys/APHAX-LAPTOP i386 >>>> Are you running the iwi driver that came with 6.1-release? If so it has >>>> numerous problems that have been fixed in 6-STABLE and HEAD. I'm not >>>> sure how best to update your system except by going to 6-STABLE via a >>>> src upgrade. >>> Today I have upgraded my laptop to 6-STABLE, but unfortunately the >>> problems remain. I don't even know wether iwi is to blame, because I can't >>> figure out wether perhaps xl on my server really is sending out too large >>> packets. >>> >>> That is, so far I've been assuming that an mtu of 1500 may not mean that >>> there's exactly 1500 bytes going over the wire (overhead of protocols to >>> which the mtu doesn't apply or something, I dunno, I'm no networking >>> expert obviously :), because xl is definitely sending out packets of 1518 >>> bytes. Which iwi on my laptop doesn't like, but the NIC in my desktop >>> machine (which runs Linux) has no problem with. Maybe someone can tell me >>> which of the machines is in error here, at least I'd know what to blame :( >>> >>> The fact that my Linux box doesn't discard these packages coming from my >>> server made me suspicious of iwi initially, but maybe iwi is doing nothing >>> wrong and my Linux box is simply willing to accept these oversized packets. >>> >> I can't speak to linux but an mtu of 1500 will cause a 1518 byte packet >> to be discarded. I don't recall what your problem was but if the iwi >> driver is receiving the frame and passing it up only to be discarded by >> the 802.3 layer then you've received a frame that's too large and you >> should look at the sender side for why it's being generated. If you >> don't want to do that you can probably just up the mtu on iwi and let >> the frame through. >> > > This does sound awfully lot like the driver doesn't strip the 4 byte > checksum of a basic 802.[23] ethernet frame. My initial thought was that > it was a vlan frame but the frame protocol indicates it's an IP packet. > Perhaps it's a frame that slips through the AP's checks on it's way out > to the wireless? Hmm, I'm not exactly sure what all this means but I suppose I could spent some time capturing packets on both sides and see if anything happens in between, and maybe read a book or two on networking/tcp-ip =] I should maybe also mention that my desktop Linux box is connected over wifi as well. Perhaps if the AP is at fault, it would explain some weird packetloss problems I've been having when playing online games (and maybe in other situations as well, but I guess this kind of thing is most noticable with online games). From owner-freebsd-net@FreeBSD.ORG Sun Sep 17 21:06: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 28EBE16A40F for ; Sun, 17 Sep 2006 21:06:30 +0000 (UTC) (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 C175643D73 for ; Sun, 17 Sep 2006 21:06:29 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (sb7acjvt90xvx4mi@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8HL6NuQ090503; Sun, 17 Sep 2006 14:06:23 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8HL6Jhd090502; Sun, 17 Sep 2006 14:06:19 -0700 (PDT) (envelope-from jmg) Date: Sun, 17 Sep 2006 14:06:19 -0700 From: John-Mark Gurney To: Anton Butsyk Message-ID: <20060917210619.GJ9421@funkthat.com> Mail-Followup-To: Anton Butsyk , freebsd-net@freebsd.org References: <450D9680.2020700@abutsyk.sumy.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <450D9680.2020700@abutsyk.sumy.ua> 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-net@freebsd.org Subject: Re: kevent/kqueue http socks proxy 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: Sun, 17 Sep 2006 21:06:30 -0000 Anton Butsyk wrote this message on Sun, Sep 17, 2006 at 21:40 +0300: > I've found bsdproxy using kevent/kqueue(2) system calls. > Is there any http/https and/or socks proxy using this mechanism? I believe squid makes use of kqueue, or our port of squid has patches the uses it... -- 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 Sun Sep 17 21:36:12 2006 Return-Path: X-Original-To: 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 8459716A407; Sun, 17 Sep 2006 21:36:12 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E71843D45; Sun, 17 Sep 2006 21:36:10 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6AEA.dip.t-dialin.net [84.154.106.234]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8HLa68E075464; Sun, 17 Sep 2006 23:36:06 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id k8HLZvQq001129; Sun, 17 Sep 2006 23:36:02 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8HLZvN5094226; Sun, 17 Sep 2006 23:35:57 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609172135.k8HLZvN5094226@fire.jhs.private> To: Hajimu UMEMOTO In-reply-to: <20060917120701.4d8eb7ec@dev.lan.Awfulhak.org> References: <200609141344.k8EDiI42092840@flat.berklix.org> <20060917120701.4d8eb7ec@dev.lan.Awfulhak.org> Comments: In-reply-to Brian Somers message dated "Sun, 17 Sep 2006 12:07:01 -0700." Date: Sun, 17 Sep 2006 23:35:57 +0200 From: "Julian H. Stacey" Cc: Gary Jennejohn , Brian Somers , net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 17 Sep 2006 21:36:12 -0000 Brian Somers wrote: > On Sun, 17 Sep 2006 20:10:47 +0900 Hajimu UMEMOTO wrote: > > Hi, > > > > >>>>> On Thu, 14 Sep 2006 15:44:18 +0200 (CEST) > > >>>>> "Julian Stacey" said: > > > > jhs> I'm not clear if this is a bug or a config error: > > jhs> It seems though my /usr/sbin/ppp was moving traffic > > jhs> to & from internet, it was only listening for commands > > jhs> (not data) on ipv6, not ipv4, thus I could not type commands > > jhs> like dial & drop, unless instead of running ppp -auto > > jhs> instead I invoked ppp manually in foreground on localhost. > > > > As far as I read the source of ppp(8), it only listen on an IPv6, and > > expects to listen on an IPv4 through an IPv4-mapped IPv6 address. > > However, an IPv4-mapped IPv6 address feature is disabled by default. > > ppp(8) should be rewritten to listen on both an IPv4 and an IPv6. > > But, it is slightly complex. So, I made a patch to enable an > > IPv4-mapped IPv6 address only for the socket that ppp(8) is listening > > on. > > I have no environment for testing this. Could you try this patch? > > > > Index: usr.sbin/ppp/server.c > > diff -u -p usr.sbin/ppp/server.c.orig usr.sbin/ppp/server.c > > --- usr.sbin/ppp/server.c.orig Sun Sep 5 10:46:52 2004 > > +++ usr.sbin/ppp/server.c Sun Sep 17 19:54:43 2006 > > @@ -346,6 +346,13 @@ server_TcpOpen(struct bundle *bundle, u_ > > goto failed; > > } > > > > +#ifndef NOINET6 > > + if (probe.ipv6_available) { > > + int off = 0; > > + setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, (char *)&off, sizeof(off)); > > + } > > +#endif > > + > > setsockopt(s, SOL_SOCKET, SO_REUSEADDR, &s, sizeof s); > > if (bind(s, (struct sockaddr *)&ss, sz) < 0) { > > log_Printf(LogWARN, "Tcp: bind: %s\n", strerror(errno)); > > > > > > Sincerely, > > AFAIR I had trouble getting that code to work and was advised at > the time that I'd just get the mapped port for free. I haven't > been using IPv6 on production machines for some time, so I haven't > seen the problem :( > > It'd be great if you'd commit the patch if Julian says it works > ok for him. Tested. It Works. Thanks ! I tested the patch on PPP running under both kernels IPV4+6 & V4only just to be sure, it works on both, & allows me to type dial & down (all I tried or wanted.) Output With patch: ------------------------ strings /boot/kernel/kernel | grep ___ | grep INET ___options INET ___options INET6 sockstat -l USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root ppp 939 9 tcp46 *:12345 *:* ------------------------ strings /boot/kernel/kernel | grep ___ | grep INET ___options INET ___# options INET6 sockstat -l USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root ppp 931 9 tcp4 *:12345 *:* ------------------------ Old V4+6 Kernel pre patch: USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root ppp 1020 9 tcp6 *:12345 *:* I hope it's commited. (Dont't know if a 2nd tester is needed to verify ?) Thanks Hajimu :-) Julian -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 03:53:50 2006 Return-Path: X-Original-To: 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 1D4D716A416; Mon, 18 Sep 2006 03:53:50 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id C394A43D60; Mon, 18 Sep 2006 03:53:45 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:vNTjmqJEVW3CRTxW19T8Ml5KzWQ/Yt/hF55fEVDstCltdqg/8wrj3Ox3W95KZ4N8@kasuga-iwi.mahoroba.org [IPv6:2001:2f0:104:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.8/8.13.8) with ESMTP/inet6 id k8I3rIfW057380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Sep 2006 12:53:23 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 18 Sep 2006 12:53:17 +0900 Message-ID: From: Hajimu UMEMOTO To: "Julian H. Stacey" In-Reply-To: <200609172135.k8HLZvN5094226@fire.jhs.private> References: <200609141344.k8EDiI42092840@flat.berklix.org> <20060917120701.4d8eb7ec@dev.lan.Awfulhak.org> <200609172135.k8HLZvN5094226@fire.jhs.private> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-pc-freebsd) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.2-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0a6 (ameno.mahoroba.org [IPv6:2001:2f0:104:8010::1]); Mon, 18 Sep 2006 12:53:24 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.5 X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on ameno.mahoroba.org Cc: Gary Jennejohn , Brian Somers , net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 18 Sep 2006 03:53:50 -0000 Hi, >>>>> On Sun, 17 Sep 2006 23:35:57 +0200 >>>>> "Julian H. Stacey" said: > AFAIR I had trouble getting that code to work and was advised at > the time that I'd just get the mapped port for free. I haven't > been using IPv6 on production machines for some time, so I haven't > seen the problem :( > > It'd be great if you'd commit the patch if Julian says it works > ok for him. jhs> Tested. It Works. Thanks ! jhs> I tested the patch on PPP running under both kernels IPV4+6 & V4only jhs> just to be sure, it works on both, & allows me to type dial & down jhs> (all I tried or wanted.) jhs> Output With patch: ------------------------ jhs> strings /boot/kernel/kernel | grep ___ | grep INET jhs> ___options INET jhs> ___options INET6 jhs> sockstat -l jhs> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS jhs> root ppp 939 9 tcp46 *:12345 *:* ------------------------ jhs> strings /boot/kernel/kernel | grep ___ | grep INET jhs> ___options INET jhs> ___# options INET6 jhs> sockstat -l jhs> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS jhs> root ppp 931 9 tcp4 *:12345 *:* ------------------------ jhs> Old V4+6 Kernel pre patch: jhs> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS jhs> root ppp 1020 9 tcp6 *:12345 *:* jhs> I hope it's commited. (Dont't know if a 2nd tester is needed to verify ?) Thank you for testing. I've just committed it. jhs> Thanks Hajimu :-) You are welcome. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 04:27: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 58BFF16A407 for ; Mon, 18 Sep 2006 04:27:45 +0000 (UTC) (envelope-from freebsd-net@goldenpath.org) Received: from mail.sbsnet.com (mail.sbsnet.com [63.147.233.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC10A43D45 for ; Mon, 18 Sep 2006 04:27:44 +0000 (GMT) (envelope-from freebsd-net@goldenpath.org) Received: from [192.168.254.199] [24.199.124.213] by mail.sbsnet.com with ESMTP (SMTPD-8.22) id AFDE02F8; Mon, 18 Sep 2006 00:26:06 -0400 Message-ID: <450E2032.6070106@goldenpath.org> Date: Mon, 18 Sep 2006 00:27:30 -0400 From: Tim Allender User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <450B93F6.4090409@goldenpath.org> <1255523FBB4AAE9CBCE5E949@paul-schmehls-powerbook59.local> In-Reply-To: <1255523FBB4AAE9CBCE5E949@paul-schmehls-powerbook59.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: NIC Problems 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, 18 Sep 2006 04:27:45 -0000 pauls@utdallas.edu wrote: > > > --On September 16, 2006 2:04:38 AM -0400 Tim Allender > wrote: > >> Not sure if I should post this here or straight to the pfSensse list. >> I suspect this kind of thing is a faulty NIC but since I've not seen it >> before I'm not sure: >> >> vr0: receive error (81): rx buffer error >> vr0: revieve error (0024) no buffers >> vr0: receive error (81): rx buffer error >> vr0: revieve error (0024) no buffers >> vr0: receive error (81): rx buffer error >> vr0: revieve error (0024) no buffers >> vr0: receive error (81): rx buffer error >> vr0: revieve error (0024) no buffers >> > What NIC is it? Good question. It's the onboard NIC for a Intel® Desktop Board D850GB. (http://www.intel.com/support/motherboards/desktop/d850gb/) You know, one of those one's from about 5 years back when RDRAM looked like it might be promising. The board uses RDRAM. It also uses one of those upgrade processor socket extensions to use socket 478 procs (upgraded from socket 423), so that I could put a spare 1.7 p4 in it that I didn't want to go to waste. I guess I've really squeezed my money's worth out of this old puppy. Actually, though, (concerning the issue) it seems to have stopped happening now that I've undone most of the traffic shaping rules I had setup. I did leave on "Prioritize VoIP traffic", but disabled all the other rules I'd thrown in for the heck of it. Seems to be working fine now. (We'll see how the phone holds up). Maybe it's an issue with the extent to which the NIC supports ALTQ? I know, the one I setup at the office doesn't do traffic shaping at all. (old p3 board, onboard NIC not supporting ALTQ, that is). So, I wanted to try it out at home. I really want to get the full use out of the traffic shaping, though. It'll really come in handy at the office. I'm going to order a few NICs, for this purpose and to have some spares on hand. I'm not really sure, though, how to measure the quality of NICs beyond the typical 10/100/1000 rating. Are there certain NICs recommended to get the most out of ALTQ? > > Paul Schmehl (pauls@utdallas.edu) > Adjunct Information Security Officer > The University of Texas at Dallas > http://www.utdallas.edu/ir/security/ From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 11:08: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 0331B16A40F for ; Mon, 18 Sep 2006 11:08:20 +0000 (UTC) (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 C34B943D46 for ; Mon, 18 Sep 2006 11:08:19 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8IB8JJT041041 for ; Mon, 18 Sep 2006 11:08:19 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8IB8ILG041037 for freebsd-net@FreeBSD.org; Mon, 18 Sep 2006 11:08:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Sep 2006 11:08:18 GMT Message-Id: <200609181108.k8IB8ILG041037@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 11:08:20 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/92552 net A serious bug in most network drivers from 5.X to 6.X f kern/93220 net [inet6] nd6_lookup: failed to add route for a neighbor 2 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19875 net A new protocol family, PF_IPOPTION, to handle IP optio o conf/23063 net [PATCH] for static ARP tables in rc.network o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/95267 net packet drops periodically appear o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o kern/102607 net [if_bridge] don't generate random L2 address 8 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 11:49: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 892E216A407 for ; Mon, 18 Sep 2006 11:49:40 +0000 (UTC) (envelope-from nayak_purushotham@yahoo.com) Received: from web56107.mail.re3.yahoo.com (web56107.mail.re3.yahoo.com [216.252.110.201]) by mx1.FreeBSD.org (Postfix) with SMTP id 158F743D5C for ; Mon, 18 Sep 2006 11:49:12 +0000 (GMT) (envelope-from nayak_purushotham@yahoo.com) Received: (qmail 72367 invoked by uid 60001); 18 Sep 2006 11:49:12 -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=0fZByQKvpu0cGy3ylPpwW3+5tA4WQM/+MAShDwcVilsa5dUc0prEBPq9bvolw+plAfpEl+CqiCeMDBtU4KyvmNtEyC7WTECjmdImndimNWKQO1o0WzoNelxpwUa2ILOwuLOSER7RzgZZ4PHWN9kgB7TOmxiz5pJl40Jkn5MsM/8= ; Message-ID: <20060918114912.72365.qmail@web56107.mail.re3.yahoo.com> Received: from [68.55.32.211] by web56107.mail.re3.yahoo.com via HTTP; Mon, 18 Sep 2006 04:49:12 PDT Date: Mon, 18 Sep 2006 04:49:12 -0700 (PDT) From: Purushotham Nayak To: freebsd-net@freebsd.org In-Reply-To: <20060917120041.7852E16A57C@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: freebsd-net Digest, Vol 181, Issue 9 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, 18 Sep 2006 11:49:40 -0000 freebsd-net-request@freebsd.org wrote: Send freebsd-net mailing list submissions to freebsd-net@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-net or, via email, send a message with subject or body 'help' to freebsd-net-request@freebsd.org You can reach the person managing the list at freebsd-net-owner@freebsd.org When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-net digest..." Today's Topics: 1. Re: FreeBSD 6.1 + ath0 + NAT (Sam Leffler) 2. Re: iwi discarding oversized packets while mtu=1500 for src/dst (Sam Leffler) 3. Re: NIC Problems (pauls@utdallas.edu) 4. Re: Can someone take a look at PR 89061 (ipv6 autoconfigure 6to4) (gnn@freebsd.org) 5. Re: problems with ng_fec (Michael W. Lucas) 6. Re: ppp command port does not listens on ipv4 unless no INET6 in kernel (Hajimu UMEMOTO) ---------------------------------------------------------------------- Message: 1 Date: Sat, 16 Sep 2006 09:06:11 -0700 From: Sam Leffler Subject: Re: FreeBSD 6.1 + ath0 + NAT To: Phil Chadwick Cc: freebsd-net@freebsd.org Message-ID: <450C20F3.2000005@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Phil Chadwick wrote: > Hi all, > > This is my first post, so please be gentle :-) > > I have a Linksys WAG54G V.2 ADSL modem (Firmware Version: 1.00.39) > connection to the Internet, and a Netgear WG311T wireless Ethernet card > running on FreeBSD 6.1 (PC#1). > > Recently I added a second FreeBSD 6.1 system (PC#2) which has no > wireless card (well it does, but it's a TI chipset not supported in > FreeBSD). So I connected it to PC#1 with a Gigabit copper wire > connection. I also added firewall and NATing on PC#1 to provide PC#2 > with a route to the Internet. > > When I boot PC#1, the connection between ath0 and the ADSL modem will run > as expected (routing to the Internet for itself and PC#2) for some time > (roughly anywhere from 0 to 30 minutes), but always eventually hangs. > It's then not possible to ping the ADSL modem. Do you really mean you ping the modem or a host on the far side of the modem? > > The hang happens regardless of whether the new (PC#2) system is booted > or not. Then ignore PC#2 and remove it from the system. > > The PC#1 ath0 wireless connection has been woking flawlessly (without > the firewall and NAT changs) for nearly a year (originally under FreeBSD > 6.0 with Sam Lefflers ath patches) and more recently on FreeBSD 6.1. > > Can anybody spot anything obviously wrong with the new setup, or know of > any bug reports that might impact a NATing gateway on a wireless connection? > > I have also recently discovered the link goes up and down every 20 or 30 > minutes with what looks like a DHCP lease renewal. This extracted from > /var/log/messages: > > Sep 13 19:42:21 kt400 kernel: ath0: link state changed to DOWN > Sep 13 19:42:23 kt400 kernel: ath0: link state changed to UP > Sep 13 19:42:23 kt400 dhclient: New IP Address (ath0): 192.168.1.64 > Sep 13 19:42:23 kt400 dhclient: New Subnet Mask (ath0): 255.255.255.0 > Sep 13 19:42:23 kt400 dhclient: New Broadcast Address (ath0): 192.168.1.255 > Sep 13 19:42:23 kt400 dhclient: New Routers (ath0): 192.168.1.1 > Sep 13 20:12:21 kt400 kernel: ath0: link state changed to DOWN > Sep 13 20:12:23 kt400 kernel: ath0: link state changed to UP > Sep 13 20:12:23 kt400 dhclient: New IP Address (ath0): 192.168.1.64 > Sep 13 20:12:23 kt400 dhclient: New Subnet Mask (ath0): 255.255.255.0 > Sep 13 20:12:23 kt400 dhclient: New Broadcast Address (ath0): 192.168.1.255 > Sep 13 20:12:23 kt400 dhclient: New Routers (ath0): 192.168.1.1 > Sep 13 21:32:21 kt400 kernel: ath0: link state changed to DOWN > Sep 13 21:32:24 kt400 kernel: ath0: link state changed to UP > > Looks like a smoking gun? Is this likely to upset the firewall/NATing? Unlikely. > > [I have not yet had a chance to correlate the hang with the lease renewal, > but will test that tomorrow.] > > In the kernel config file I have added: > > options IPFIREWALL > options IPDIVERT > > In /etc/rc.conf I have: > > # See also /etc/wpa_supplicant.conf > ifconfig_ath0="WPA DHCP" > # Private x-over to printer > ifconfig_rl0="inet kt400pr netmask 255.255.255.0 broadcast 10.0.0.255" > # Private x-over to Dell 350 (PC#2) > ifconfig_sk0="inet gbkt400 netmask 255.255.255.0 broadcast 192.168.2.255" > # These added for firewall/NATing > gateway_enable="YES" > firewall_enable="YES" > firewall_type="OPEN" > natd_enable="YES" > natd_interface="ath0" > natd_flags="" > > [kt400.145] cat /etc/wpa_supplicant.conf > network={ > ssid="linksys" > key_mgmt=NONE > wep_key0=xxxxxxxxxx > wep_tx_keyidx=0 > } > > [kt400.146] ifconfig -a > sk0: flags=8843 mtu 1500 > options=8 > inet6 fe80::215:e9ff:feb0:e5b0%sk0 prefixlen 64 scopeid 0x1 > inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 > ether 00:15:e9:b0:e5:b0 > media: Ethernet autoselect (none) > status: no carrier > > ath0: flags=8843 mtu 1500 > inet6 fe80::20f:b5ff:fef6:28eb%ath0 prefixlen 64 scopeid 0x2 > inet 192.168.1.64 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:0f:b5:f6:28:eb > media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > status: associated > ssid linksys channel 11 bssid 00:14:bf:7a:57:94 > authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit txpowmax 37 > protmode CTS burst roaming MANUAL bintval 100 > > rl0: flags=8843 mtu 1500 > options=8 > inet6 fe80::220:edff:fe70:471a%rl0 prefixlen 64 scopeid 0x3 > inet 10.0.0.254 netmask 0xffffff00 broadcast 10.0.0.255 > ether 00:20:ed:70:47:1a > media: Ethernet autoselect (none) > status: no carrier > > fwe0: flags=108802 mtu 1500 > options=8 > ether 02:00:20:71:b9:a6 > ch 1 dma -1 > lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 > inet 127.0.0.1 netmask 0xff000000 > > > Thanks, > > I am confused about what the config is and what exactly is wrong. Try simplifying your configuration so you can pinpoint the problem. It sounds like you've got a sta associated to an ap using ath. That sta cannot pass packets beyond the ap after some period of time. Have you look on the ap to see if packets are still flowing? Have you used tcpdump to look for packets on the far side of the ap (on the wired network)? Sam Hi Phil, Just adding my 2cents for wat it's worth. Did you check the routing table to see if the DHCP renewal with the link going up and down is causing any problems ?. Also, have you made sure there is no other aps or stations on the same channel which could be causing your link to go up and down ?. nayak --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 12:25:43 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 5DC5C16A4A0 for ; Mon, 18 Sep 2006 12:25:43 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 733F943D69 for ; Mon, 18 Sep 2006 12:25:41 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k8ICPPaf074942; Mon, 18 Sep 2006 15:25:25 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k8ICPPUV074939; Mon, 18 Sep 2006 15:25:25 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Mon, 18 Sep 2006 15:25:25 +0300 (EEST) From: Dmitry Pryanishnikov To: Nikolas Britton In-Reply-To: Message-ID: <20060918150510.D33680@atlantis.atlantis.dp.ua> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Marvell YukonII Status Update? 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, 18 Sep 2006 12:25:43 -0000 Hello! On Thu, 29 Jun 2006, Nikolas Britton wrote: > Last I checked somebody was developing an experimental driver and > Marvell had just released the code to their FreeBSD 5.x/6.x driver: > mykbsd60x86-8.12.2.3.tar (bindary kmod package) > mykbsd60x86-8.12.1.3-src.tgz (source code) I can confirm that this (mykbsd60x86-8.12.1.3-src.tgz) package compiles and attaches OK to both of built-in LAN controllers on the ASUS P5W DH motherboard under mid-August RELENG_6: myk0: port 0xa800-0xa8ff mem 0xff7fc000-0xff7fffff irq 16 at device 0.0 on pci3 myk0: Ethernet address: 00:17:31:ee:d1:aa myk1: port 0xb800-0xb8ff mem 0xff8fc000-0xff8fffff irq 19 at device 0.0 on pci4 myk1: Ethernet address: 00:17:31:ee:d8:7f Data transfers (at least in media auto-detect mode) also work OK both in 10/FULL and 100/FULL mode (haven't tried 1000 yet). > Has checksum offloading or the performance problems been fixed? Has > Marvell updated their driver? Is someone going to commit Marvell's > driver to -CURRENT? And what's happening with the experimental driver? So I've got 2 questions: 1. Has situation with this driver improved somehow (is somebody going to support it and commit into the CURRENT)? 2. What kinds of performance problems / stability issues should I expect with the driver in it's current state under 6-STABLE? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 12:44: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 C365316A415 for ; Mon, 18 Sep 2006 12:44:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D67E643D46 for ; Mon, 18 Sep 2006 12:44:07 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so1509228nzn for ; Mon, 18 Sep 2006 05:44:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=EDax+Pv5ArEUaFG/HZcSGcjSK+F/EfjkVGQMn8HRYYXbs0EWfq0LdcdrFD07i0e+U6/b+k0o/9vSyH0nbLc0QnlFSNQgKtQLLXb3Ov/W6hjDysB/iHG4h6duxOWdme9Eie7usiskvxUFJHC+KfhULAaJU6fU91c8BaG1g4mdgvQ= Received: by 10.65.112.5 with SMTP id p5mr15761733qbm; Mon, 18 Sep 2006 05:43:58 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 15sm1485749nzp.2006.09.18.05.43.56; Mon, 18 Sep 2006 05:43:58 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k8ICiXXu032484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Sep 2006 21:44:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k8ICiWVv032483; Mon, 18 Sep 2006 21:44:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 18 Sep 2006 21:44:32 +0900 From: Pyun YongHyeon To: Dmitry Pryanishnikov Message-ID: <20060918124431.GD30078@cdnetworks.co.kr> References: <20060918150510.D33680@atlantis.atlantis.dp.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060918150510.D33680@atlantis.atlantis.dp.ua> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Nikolas Britton Subject: Re: Marvell YukonII Status Update? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 12:44:22 -0000 On Mon, Sep 18, 2006 at 03:25:25PM +0300, Dmitry Pryanishnikov wrote: > > Hello! > > On Thu, 29 Jun 2006, Nikolas Britton wrote: > >Last I checked somebody was developing an experimental driver and > >Marvell had just released the code to their FreeBSD 5.x/6.x driver: > >mykbsd60x86-8.12.2.3.tar (bindary kmod package) > >mykbsd60x86-8.12.1.3-src.tgz (source code) > > I can confirm that this (mykbsd60x86-8.12.1.3-src.tgz) package compiles and > attaches OK to both of built-in LAN controllers on the ASUS P5W DH > motherboard > under mid-August RELENG_6: > > myk0: port > 0xa800-0xa8ff mem 0xff7fc000-0xff7fffff irq 16 at device 0.0 on pci3 > myk0: Ethernet address: 00:17:31:ee:d1:aa > myk1: port > 0xb800-0xb8ff mem 0xff8fc000-0xff8fffff irq 19 at device 0.0 on pci4 > myk1: Ethernet address: 00:17:31:ee:d8:7f > > Data transfers (at least in media auto-detect mode) also work OK both in > 10/FULL and 100/FULL mode (haven't tried 1000 yet). > > >Has checksum offloading or the performance problems been fixed? Has > >Marvell updated their driver? Is someone going to commit Marvell's > >driver to -CURRENT? And what's happening with the experimental driver? > > So I've got 2 questions: > > 1. Has situation with this driver improved somehow (is somebody going to > support it and commit into the CURRENT)? > I'm working on it. Unlike OpenBSD/NetBSD msk(4) my code is based on sk(4) and myk(4) from Marvell. I've managed to send packets with new driver but it needs more testing and codes to support hardware features(VLAN tagging, TSO support, RX checksum offload etc). I can't sure TSO support could be done due to lack of documentation. > 2. What kinds of performance problems / stability issues should I expect > with the driver in it's current state under 6-STABLE? > You can see lots of witness warnings. Unloading the driver module or using Jumboframe may panic your system. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 13:30: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 3326716A4D8; Mon, 18 Sep 2006 13:30:47 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41A2B43D82; Mon, 18 Sep 2006 13:30:39 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id 0D7882A451; Mon, 18 Sep 2006 10:30:38 -0300 (BRT) Date: Mon, 18 Sep 2006 10:30:38 -0300 From: Marcelo Gardini do Amaral To: Mike Silbersack Message-ID: <20060918133038.GG6701@registro.br> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> <20060913182457.W50147@fledge.watson.org> <20060914175049.GH49126@registro.br> <450A2A6E.3040408@yandex.ru> <20060915145120.GA93074@registro.br> <20060915223211.R65248@odysseus.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060915223211.R65248@odysseus.silby.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, "Andrey V. Elsukov" , Robert Watson , freebsd-stable@freebsd.org Subject: Re: DNS query 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: Mon, 18 Sep 2006 13:30:47 -0000 Hello Mike, > Although it sounds silly, could you try recompiling 6.1 and 7.0 with a > non-SMP kernel and see how they perform? That would at least tell us if > it's a general performance problem in 6.x and 7.x, or if SMP is somehow > hurting performance in this case. I have this numbers spread over my e-mails. Just putting they together: OS q/s --- --- FreeBSD 6.1 SMP 14953 FreeBSD 6.1 UP 15516 FreeBSD 7.x SMP 15323 FreeBSD 7.x UP 16200 FreeBSD 4.11 SMP 34977 FreeBSD 4.11 UP 33926 I think is a general problem in 6.x and 7.x. UP kernel is always a little bit better, but I can't see big changes tweaking from SMP to UP. On the other hand, with the same hardware, 4.11 is twice better in performance. -- Att., Marcelo Gardini From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 14:52: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 57EF816A412 for ; Mon, 18 Sep 2006 14:52:10 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from leia.fdn.fr (ns0.fdn.org [80.67.169.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id B533243D6B for ; Mon, 18 Sep 2006 14:52:08 +0000 (GMT) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by leia.fdn.fr (8.13.3/8.13.3/FDN) with ESMTP id k8IEq6S4000455 for ; Mon, 18 Sep 2006 16:52:07 +0200 Received: by smtp.zeninc.net (smtpd, from userid 1000) id 17EEC3F17; Mon, 18 Sep 2006 16:52:01 +0200 (CEST) Date: Mon, 18 Sep 2006 16:52:00 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20060918145200.GA26025@zen.inc> References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: All mail clients suck. This one just sucks less. Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 14:52:10 -0000 On Sun, Sep 17, 2006 at 11:58:17AM -0400, Scott Ullrich wrote: > On 9/17/06, VANHULLEBUS Yvan wrote: > >Make sure your ipsec-tools port have been recompiled after your system > >has been patched / compiled / upgraded, and use > >/usr/local/sbin/setkey. > > > >FreeBSD's setkey does not (yet ?) support NAT-T extensions at all. > > I tried both /sbin/setkey and /usr/locals/bin/setkey and both result > in the same Invalid extension type errors. Strange.... [....] > # /usr/local/sbin/setkey -D > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > Invalid extension type > > Can you think of anything else to try? I re-compiled ipsec-tools on > the same host before sending this. That really looks like ipsec-tools have been compiled without NAT-T support. By default in FreeBSd's port, NAT-T support is enabled if support is detected on the system (checks for some structs in include/net/pfkeyv2.h). Can you compile again ipsec-tools port, but not clean it, and check in config.h if you have NAT-T support enabled. Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 15:05: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 72E0B16A557 for ; Mon, 18 Sep 2006 15:05:22 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA05F43D67 for ; Mon, 18 Sep 2006 15:05:11 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 719EB1FFDBC; Mon, 18 Sep 2006 17:05:10 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id A6CF91FFD70; Mon, 18 Sep 2006 17:05:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 4715C444871; Mon, 18 Sep 2006 15:04:04 +0000 (UTC) Date: Mon, 18 Sep 2006 15:04:04 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: VANHULLEBUS Yvan In-Reply-To: <20060918145200.GA26025@zen.inc> Message-ID: <20060918145727.F2478@maildrop.int.zabbadoz.net> References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> <20060918145200.GA26025@zen.inc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 15:05:22 -0000 On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote: > By default in FreeBSd's port, NAT-T support is enabled if support is > detected on the system (checks for some structs in > include/net/pfkeyv2.h). > > Can you compile again ipsec-tools port, but not clean it, and check in > config.h if you have NAT-T support enabled. What I had found in the past is that the port (more exactly ipsec-tools) does not complain if configure is run with --enable-natt but the correct header files are no there. It silently continues and just disables natt support. That beahvior would be fine for "autodetect" but not for a command line option that says "I want natt support and you give me". -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 15:53: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 2D43716A47E for ; Mon, 18 Sep 2006 15:53:12 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from leia.fdn.fr (ns0.fdn.org [80.67.169.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F6A143D6A for ; Mon, 18 Sep 2006 15:52:51 +0000 (GMT) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by leia.fdn.fr (8.13.3/8.13.3/FDN) with ESMTP id k8IFqlHs017514 for ; Mon, 18 Sep 2006 17:52:51 +0200 Received: by smtp.zeninc.net (smtpd, from userid 1000) id 045643F17; Mon, 18 Sep 2006 17:52:35 +0200 (CEST) Date: Mon, 18 Sep 2006 17:52:35 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20060918155235.GA26545@zen.inc> References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> <20060918145200.GA26025@zen.inc> <20060918145727.F2478@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060918145727.F2478@maildrop.int.zabbadoz.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 15:53:12 -0000 On Mon, Sep 18, 2006 at 03:04:04PM +0000, Bjoern A. Zeeb wrote: > On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote: > > >By default in FreeBSd's port, NAT-T support is enabled if support is > >detected on the system (checks for some structs in > >include/net/pfkeyv2.h). > > > >Can you compile again ipsec-tools port, but not clean it, and check in > >config.h if you have NAT-T support enabled. > > What I had found in the past is that the port (more exactly > ipsec-tools) does not complain if configure is run with > --enable-natt but the correct header files are no there. It silently > continues and just disables natt support. > That beahvior would be fine for "autodetect" but not for a command > line option that says "I want natt support and you give me". By default, I have set the value of port's configuration to "kernel", which is exactly "use it if supported". I just checked ./configure --enable-natt=yes (which forces NAT-T support) on a FreeBSD 6.1 without NAT-T patchset, and I got that: checking kernel NAT-Traversal support... checking for struct sadb_x_nat_t_type.sadb_x_nat_t_type_len... no no checking whether to support NAT-T... yes configure: error: NAT-T requested, but no kernel support! Aborting. If I start again with just --enable-natt, I get the same. if I use --enable-natt=kernel, I'll have: checking kernel NAT-Traversal support... checking for struct sadb_x_nat_t_type.sadb_x_nat_t_type_len... no no checking whether to support NAT-T... no checking which NAT-T versions to support... none [etc....] If you are able to reproduce that problem, please send me at least the output of configure, and, if possible, the corresponding part of config.log ! Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 16:21: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 6A39A16A40F for ; Mon, 18 Sep 2006 16:21:15 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17DFF43D46 for ; Mon, 18 Sep 2006 16:21:02 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so400147uge for ; Mon, 18 Sep 2006 09:21:01 -0700 (PDT) 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=Bx1q6tCVeHxUvII3qc+KgxqILghh2YbQi/7xRcaqnPpbwV+kBeLUGFc7Klw+YSjPLj9jCN606r+zP+mW/jHfPzjIEKpyeWdW2VC0iCVsLMIe/gXv/DqiRu6SabVwWTcoGd/e5rQTEssBQirSHoEiUoPs4L+9eM82IGnD5cbuh4Y= Received: by 10.67.89.5 with SMTP id r5mr7326723ugl; Mon, 18 Sep 2006 09:21:01 -0700 (PDT) Received: by 10.67.105.8 with HTTP; Mon, 18 Sep 2006 09:20:59 -0700 (PDT) Message-ID: Date: Mon, 18 Sep 2006 12:20:59 -0400 From: "Scott Ullrich" To: "VANHULLEBUS Yvan" In-Reply-To: <20060918155235.GA26545@zen.inc> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> <20060918145200.GA26025@zen.inc> <20060918145727.F2478@maildrop.int.zabbadoz.net> <20060918155235.GA26545@zen.inc> Cc: freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 16:21:15 -0000 On 9/18/06, VANHULLEBUS Yvan wrote: > By default, I have set the value of port's configuration to "kernel", > which is exactly "use it if supported". > > I just checked ./configure --enable-natt=yes (which forces NAT-T > support) on a FreeBSD 6.1 without NAT-T patchset, and I got that: > > checking kernel NAT-Traversal support... checking for struct > sadb_x_nat_t_type.sadb_x_nat_t_type_len... no > no > checking whether to support NAT-T... yes > configure: error: NAT-T requested, but no kernel support! Aborting. > > > If I start again with just --enable-natt, I get the same. > > if I use --enable-natt=kernel, I'll have: > > checking kernel NAT-Traversal support... checking for struct > sadb_x_nat_t_type.sadb_x_nat_t_type_len... no > no > checking whether to support NAT-T... no > checking which NAT-T versions to support... none > [etc....] > > > If you are able to reproduce that problem, please send me at least the > output of configure, and, if possible, the corresponding part of > config.log ! Hello, here is what I attempted: 1. Reinstalled kernel with NAT-T support 2. cd /usr/ports/security/ipsec-tools && make rmconfig && make install * Selected NAT-T support The portions of configure that mentions NAT-T: builder# make | grep NAT-T ===> ATTENTION: You need a kernel patch to enable NAT-Traversal functionality! checking kernel NAT-Traversal support... checking for struct sadb_x_nat_t_type.sadb_x_nat_t_type_len... no checking whether to support NAT-T... no checking which NAT-T versions to support... none And finally the config.log file (rather long so I posted to my home directory): http://www.pfsense.com/~sullrich/logs/ipsec-tools/config.log Thanks for all your help! Scott From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 17:14:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C869E16A417 for ; Mon, 18 Sep 2006 17:14:59 +0000 (UTC) (envelope-from scuppers@hotmail.com) Received: from bay0-omc1-s30.bay0.hotmail.com (bay0-omc1-s30.bay0.hotmail.com [65.54.246.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id B473343D5F for ; Mon, 18 Sep 2006 17:14:53 +0000 (GMT) (envelope-from scuppers@hotmail.com) Received: from BAY111-W6 ([64.4.17.106]) by bay0-omc1-s30.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Sep 2006 10:14:53 -0700 X-Originating-IP: [131.167.67.12] X-Originating-Email: [scuppers@hotmail.com] Message-ID: MIME-Version: 1.0 From: "Scott Spare" To: dgl@dlee.org; scphantm@yahoo.com; pb@mps.com; cplnet@gmx.net; mikej@rogers.com; ccxfb52@dial.pipex.com Date: Mon, 18 Sep 2006 17:14:53 +0000 X-OriginalArrivalTime: 18 Sep 2006 17:14:53.0695 (UTC) FILETIME=[F50A30F0:01C6DB45] X-Mailman-Approved-At: Mon, 18 Sep 2006 17:21:45 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: FreeBSD kernel: smb_maperror: Unmapped error 1:158 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, 18 Sep 2006 17:15:00 -0000 Hello all,I'm writing you because I found that at some point in the past, y= ou had trouble with FreeBSD and the smb_maperror: Unmapped error 1:158 mess= age. For the folks who wrote about it, has anyone here resolved this issue? I have also copied the freebsd mailing list on the issue. =20 The background seems to be that there are over 640 messages on Google about= smb_maperror: Unmapped error 1:158 (many of them duplicates), with no ans= wer. There's a general agreement from looking at the sourcecode that Windows is = handing samba some sort of error it can't understand. =20 So far I've tried: -check all permissions on windows box against info used for logon; check sm= b and nsmb.conf -set up more verbose event logging on windows box, check event log for perm= ission related problems. =20 Other notes: -only seems to happen under streaming or heavy loading. =20 Hardware: -250GB IDE (PATA) drive shared via Windows=20 -Linksys WRT64G router operating via wired mode (100Mb/s.) =20 I might try in the future: -reinstall windows-run perfmon to check for performance-related problems li= ke dropping net packets, or disk thrashing due to page fault.-sniff network= to see what's going on ScottPS Some of the guys using Openoffice mentioned this might be related t= o .net Framework(?) _________________________________________________________________ Check the weather nationwide with MSN Search: Try it now! http://search.msn.com/results.aspx?q=3Dweather&FORM=3DWLMTAG= From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 17: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 596CC16A47B for ; Mon, 18 Sep 2006 17:45:21 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4418443D6A for ; Mon, 18 Sep 2006 17:45:12 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id C6CA01FFDD7; Mon, 18 Sep 2006 19:45:10 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id ED19D1FFDC1; Mon, 18 Sep 2006 19:45:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id A4DBB444871; Mon, 18 Sep 2006 17:40:33 +0000 (UTC) Date: Mon, 18 Sep 2006 17:40:33 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Scott Ullrich In-Reply-To: Message-ID: <20060918174000.U2478@maildrop.int.zabbadoz.net> References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> <20060918145200.GA26025@zen.inc> <20060918145727.F2478@maildrop.int.zabbadoz.net> <20060918155235.GA26545@zen.inc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org, VANHULLEBUS Yvan Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 17:45:21 -0000 On Mon, 18 Sep 2006, Scott Ullrich wrote: > 1. Reinstalled kernel with NAT-T support you need to re-install the includes/header files too (which is part of installworld). -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 17:45: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 451FC16A403 for ; Mon, 18 Sep 2006 17:45:22 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 447C443D7B for ; Mon, 18 Sep 2006 17:45:12 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id E3A601FFDD8; Mon, 18 Sep 2006 19:45:10 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id F3F991FFDD6; Mon, 18 Sep 2006 19:45:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 6171D444871; Mon, 18 Sep 2006 17:41:40 +0000 (UTC) Date: Mon, 18 Sep 2006 17:41:40 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: VANHULLEBUS Yvan In-Reply-To: <20060918155235.GA26545@zen.inc> Message-ID: <20060918174035.N2478@maildrop.int.zabbadoz.net> References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> <20060918145200.GA26025@zen.inc> <20060918145727.F2478@maildrop.int.zabbadoz.net> <20060918155235.GA26545@zen.inc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 17:45:22 -0000 On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote: > On Mon, Sep 18, 2006 at 03:04:04PM +0000, Bjoern A. Zeeb wrote: >> On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote: >> >>> By default in FreeBSd's port, NAT-T support is enabled if support is >>> detected on the system (checks for some structs in >>> include/net/pfkeyv2.h). >>> >>> Can you compile again ipsec-tools port, but not clean it, and check in >>> config.h if you have NAT-T support enabled. >> >> What I had found in the past is that the port (more exactly >> ipsec-tools) does not complain if configure is run with >> --enable-natt but the correct header files are no there. It silently >> continues and just disables natt support. >> That beahvior would be fine for "autodetect" but not for a command >> line option that says "I want natt support and you give me". > > By default, I have set the value of port's configuration to "kernel", > which is exactly "use it if supported". could you change that in the port to "yes" then. If NATT is enabled the build must fail else the choice in make config does not make any sense - does it? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 17:46:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3713216A403 for ; Mon, 18 Sep 2006 17:46:18 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7895243D7E for ; Mon, 18 Sep 2006 17:46:14 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so407007uge for ; Mon, 18 Sep 2006 10:46:13 -0700 (PDT) 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=A38o0MJ2S/Q+X7djETLgXF0126Mg7GoCmaGABcnlkTtgDybqieXKj8gAvylTYvmGYMBZT6S45oisvM6JoTddbHi7iSnLCfzZZqihouGqkoRe3SPqy72en3A0SOl5L2JTSwsktdeccuB0jkrf0Sx1y2hRWjNkVXR7KDbBJQvCAY4= Received: by 10.66.221.6 with SMTP id t6mr7375425ugg; Mon, 18 Sep 2006 10:46:13 -0700 (PDT) Received: by 10.67.105.8 with HTTP; Mon, 18 Sep 2006 10:46:12 -0700 (PDT) Message-ID: Date: Mon, 18 Sep 2006 13:46:12 -0400 From: "Scott Ullrich" To: "Bjoern A. Zeeb" In-Reply-To: <20060918174000.U2478@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060914093034.A83805@gta.com> <20060915091430.A45488@gta.com> <20060917125531.GA1611@jayce.zen.inc> <20060918145200.GA26025@zen.inc> <20060918145727.F2478@maildrop.int.zabbadoz.net> <20060918155235.GA26545@zen.inc> <20060918174000.U2478@maildrop.int.zabbadoz.net> Cc: freebsd-net@freebsd.org, VANHULLEBUS Yvan Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 17:46:18 -0000 On 9/18/06, Bjoern A. Zeeb wrote: > On Mon, 18 Sep 2006, Scott Ullrich wrote: > > > 1. Reinstalled kernel with NAT-T support > > you need to re-install the includes/header files too (which is part of > installworld). Okay, now that makes more sense. For the record, I am using FreeSBIE to build these images so this explains why this is not working now. Thanks for the hint, I'll give it a try. From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 18:00:55 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 D23E216A4E8 for ; Mon, 18 Sep 2006 18:00:55 +0000 (UTC) (envelope-from lab@gta.com) Received: from gta.com (gta-edge-199-20.gta.com [199.120.225.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 87E1543D72 for ; Mon, 18 Sep 2006 18:00:54 +0000 (GMT) (envelope-from lab@gta.com) Received: (qmail 73855 invoked by uid 1000); 18 Sep 2006 18:00:53 -0000 Date: 18 Sep 2006 18:00:53 -0000 Message-ID: <20060918180053.73854.qmail@gta.com> From: Larry Baird To: bzeeb-lists@lists.zabbadoz.net (\"Bjoern A. Zeeb\") In-Reply-To: <20060918174000.U2478@maildrop.int.zabbadoz.net> User-Agent: tin/1.5.9-20010723 ("Chord of Souls") (UNIX) (FreeBSD/4.10-RELEASE (i386)) Cc: freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 18:00:55 -0000 In article <20060918174000.U2478@maildrop.int.zabbadoz.net> you wrote: > On Mon, 18 Sep 2006, Scott Ullrich wrote: > >> 1. Reinstalled kernel with NAT-T support > > you need to re-install the includes/header files too (which is part of > installworld). >From my testing on a new 6.x box I just set up, I was wondering if this was the step that was being left out. Glad to hear it was something easy. Larry -- ------------------------------------------------------------------------ Larry Baird | http://www.gta.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 19:44: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 85C1416A4CA for ; Mon, 18 Sep 2006 19:44:08 +0000 (UTC) (envelope-from Joerg.Pulz@frm2.tum.de) Received: from mailhost.frm2.tum.de (mailhost.frm2.tum.de [129.187.179.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C5C943D79 for ; Mon, 18 Sep 2006 19:43:50 +0000 (GMT) (envelope-from Joerg.Pulz@frm2.tum.de) Received: from localhost (mailhost.frm2.tum.de [129.187.179.12]) by mailhost.frm2.tum.de (8.13.8/8.13.8) with ESMTP id k8IJhnHD008382; Mon, 18 Sep 2006 21:43:49 +0200 (CEST) (envelope-from jpulz@frm2.tum.de) X-Virus-Scanned: at mailhost.frm2.tum.de Received: from hades.admin.frm2 (hades.admin.frm2 [172.25.1.10]) by mailhost.frm2.tum.de (8.13.8/8.13.8) with ESMTP id k8IJhjjH008378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Sep 2006 21:43:45 +0200 (CEST) (envelope-from jpulz@frm2.tum.de) Received: from hades.admin.frm2 (localhost [127.0.0.1]) by hades.admin.frm2 (8.13.6/8.13.6) with ESMTP id k8IJhj3q025067; Mon, 18 Sep 2006 21:43:45 +0200 (CEST) (envelope-from jpulz@frm2.tum.de) Received: (from jpulz@localhost) by hades.admin.frm2 (8.13.6/8.13.6/Submit) id k8IJhiea025066; Mon, 18 Sep 2006 21:43:44 +0200 (CEST) (envelope-from jpulz) Date: Mon, 18 Sep 2006 21:43:41 +0200 (CEST) From: Joerg Pulz To: Larry Baird In-Reply-To: <20060918180053.73854.qmail@gta.com> Message-ID: <20060918210519.J978@hades.admin.frm2> References: <20060918180053.73854.qmail@gta.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1595678069-1158608621=:978" Cc: freebsd-net@freebsd.org, VANHULLEBUS Yvan Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 19:44:08 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1595678069-1158608621=:978 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, first of all, a big thanks to Yvan and Larry, and all others, for their work. IPSEC_NAT_T is working fine for me with either IPSEC or FAST_IPSEC with RELENG_6 as server and FAST_IPSEC with CURRENT (small modifications after patching where necessary) as client. Regarding the /sbin/setkey against ${LOCALBASE}/sbin/setkey (ipsec-tools version) discussion, i found a minor difference in the output between those two when using aes/rijndael encryption and executing "setkey -D". The FreeBSD base version of setkey outputs something like this: E: rijndael-cbc XXXXXXXX ... and the ipsec-tools version of setkey outputs this: E: 12 XXXXXXXX ... The difference comes out of libipsec/pfkey_dump.c . In the FreeBSD base version of this file we have this: #ifdef SADB_X_EALG_RIJNDAELCBC { SADB_X_EALG_RIJNDAELCBC, "rijndael-cbc", }, #endif and in the ipsec-tools version this: #ifdef SADB_X_EALG_AESCBC { SADB_X_EALG_AESCBC, "aes-cbc", }, #endif Unfortunately, we have no definition for SADB_X_EALG_AESCBC in FreeBSD's pfkeyv2.h file. The definition for encryption algorithm number 12 in pfkeyv2.h is the following: #define SADB_X_EALG_RIJNDAELCBC 12 #define SADB_X_EALG_AES 12 I'm not sure which one is right in this case, but as a quick fix i've attached two small patches for the ipsec-tools port. Simply copy both files to ${PORTSDIR}/security/ipsec-tools/files and rebuild/reinstall the port. Any comments on this? Kind regards Joerg - -- The beginning is the most important part of the work. -Plato -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFDvbwSPOsGF+KA+MRAuofAKCoYZnYVBFOTsV4WtEZKhcl2tKp6gCfYLrw /vYWOKnjgBUe0zMppDNFarQ= =OH/c -----END PGP SIGNATURE----- --0-1595678069-1158608621=:978 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=patch-src__libipsec__pfkey_dump.c Content-Transfer-Encoding: BASE64 Content-ID: <20060918214341.V978@hades.admin.frm2> Content-Description: Content-Disposition: attachment; filename=patch-src__libipsec__pfkey_dump.c LS0tIHNyYy9saWJpcHNlYy9wZmtleV9kdW1wLmMub3JpZwlNb24gU2VwIDE4 IDIwOjU2OjAyIDIwMDYNCisrKyBzcmMvbGliaXBzZWMvcGZrZXlfZHVtcC5j CU1vbiBTZXAgMTggMjA6NTg6MTMgMjAwNg0KQEAgLTE5MCw2ICsxOTAsOSBA QA0KICNpZmRlZiBTQURCX1hfRUFMR19BRVNDQkMNCiAJeyBTQURCX1hfRUFM R19BRVNDQkMsICJhZXMtY2JjIiwgfSwNCiAjZW5kaWYNCisjaWZkZWYgU0FE Ql9YX0VBTEdfUklKTkRBRUxDQkMNCisJeyBTQURCX1hfRUFMR19SSUpOREFF TENCQywgInJpam5kYWVsLWNiYyIsIH0sDQorI2VuZGlmDQogI2lmZGVmIFNB REJfWF9FQUxHX1RXT0ZJU0hDQkMNCiAJeyBTQURCX1hfRUFMR19UV09GSVNI Q0JDLCAidHdvZmlzaC1jYmMiLCB9LA0KICNlbmRpZg0K --0-1595678069-1158608621=:978 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=patch-src__setkey__token.l Content-Transfer-Encoding: BASE64 Content-ID: <20060918214341.H978@hades.admin.frm2> Content-Description: Content-Disposition: attachment; filename=patch-src__setkey__token.l LS0tIHNyYy9zZXRrZXkvdG9rZW4ubC5vcmlnCU1vbiBTZXAgMTggMjE6MzA6 MTggMjAwNg0KKysrIHNyYy9zZXRrZXkvdG9rZW4ubAlNb24gU2VwIDE4IDIx OjMxOjA1IDIwMDYNCkBAIC0yMDgsOCArMjA4LDggQEANCiAjZW5kaWYNCiB9 DQogPFNfRU5DQUxHPnJpam5kYWVsLWNiYwl7IA0KLSNpZmRlZiBTQURCX1hf RUFMR19BRVNDQkMNCi0JeXlsdmFsLm51bSA9IFNBREJfWF9FQUxHX0FFU0NC QzsgQkVHSU4gSU5JVElBTDsgcmV0dXJuKEFMR19FTkMpOyANCisjaWZkZWYg U0FEQl9YX0VBTEdfUklKTkRBRUxDQkMNCisJeXlsdmFsLm51bSA9IFNBREJf WF9FQUxHX1JJSk5EQUVMQ0JDOyBCRUdJTiBJTklUSUFMOyByZXR1cm4oQUxH X0VOQyk7IA0KICNlbmRpZg0KIH0NCiA8U19FTkNBTEc+YWVzLWN0cgl7IHl5 bHZhbC5udW0gPSBTQURCX1hfRUFMR19BRVNDVFI7IEJFR0lOIElOSVRJQUw7 IHJldHVybihBTEdfRU5DKTsgfQ0K --0-1595678069-1158608621=:978-- From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 20:42: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 603DF16A403 for ; Mon, 18 Sep 2006 20:42:47 +0000 (UTC) (envelope-from lab@gta.com) Received: from gta.com (gta-edge-199-20.gta.com [199.120.225.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 7B0B643D70 for ; Mon, 18 Sep 2006 20:42:46 +0000 (GMT) (envelope-from lab@gta.com) Received: (qmail 4351 invoked by uid 1000); 18 Sep 2006 20:42:45 -0000 Date: Mon, 18 Sep 2006 16:42:45 -0400 From: Larry Baird To: Joerg Pulz Message-ID: <20060918164245.A98717@gta.com> References: <20060918180053.73854.qmail@gta.com> <20060918210519.J978@hades.admin.frm2> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20060918210519.J978@hades.admin.frm2>; from Joerg.Pulz@frm2.tum.de on Mon, Sep 18, 2006 at 09:43:41PM +0200 Cc: freebsd-net@freebsd.org, VANHULLEBUS Yvan Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 20:42:47 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Sep 18, 2006 at 09:43:41PM +0200, Joerg Pulz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi, > > first of all, a big thanks to Yvan and Larry, and all others, for their > work. IPSEC_NAT_T is working fine for me with either IPSEC or FAST_IPSEC > with RELENG_6 as server and FAST_IPSEC with CURRENT (small modifications > after patching where necessary) as client. > > > Regarding the /sbin/setkey against ${LOCALBASE}/sbin/setkey (ipsec-tools > version) discussion, i found a minor difference in the output between > those two when using aes/rijndael encryption and executing "setkey -D". > The FreeBSD base version of setkey outputs something like this: > E: rijndael-cbc XXXXXXXX ... > and the ipsec-tools version of setkey outputs this: > E: 12 XXXXXXXX ... > > The difference comes out of libipsec/pfkey_dump.c . > In the FreeBSD base version of this file we have this: > #ifdef SADB_X_EALG_RIJNDAELCBC > { SADB_X_EALG_RIJNDAELCBC, "rijndael-cbc", }, > #endif > > and in the ipsec-tools version this: > #ifdef SADB_X_EALG_AESCBC > { SADB_X_EALG_AESCBC, "aes-cbc", }, > #endif > > Unfortunately, we have no definition for SADB_X_EALG_AESCBC in FreeBSD's > pfkeyv2.h file. The definition for encryption algorithm number 12 in > pfkeyv2.h is the following: > #define SADB_X_EALG_RIJNDAELCBC 12 > #define SADB_X_EALG_AES 12 I have attached a slight different and in mind cleaner patch for this problem. I initially thought the problem was with FreeBSD's pfkeyv2.h. To be consistent it would seem that: #define SADB_X_EALG_AES 12 should be #define SADB_X_EALG_AESCBC 12 Looking at NetBSD, they have the same definition as FreeBSD. It would seem that this problem exists for both FreebSD and NetBSD. For what its worth, Linux uses SADB_X_EALG_AESCBC. -- ------------------------------------------------------------------------ Larry Baird | http://www.gta.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="aes.diff" --- src/libipsec/pfkey_dump.c.orig Mon Sep 18 16:20:41 2006 +++ src/libipsec/pfkey_dump.c Mon Sep 18 16:22:17 2006 @@ -78,6 +78,9 @@ #define SADB_X_EALG_RC5CBC SADB_EALG_RC5CBC #endif #endif +#if defined(SADB_X_EALG_AES) && ! defined(SADB_X_EALG_AESCBC) +#define SADB_X_EALG_AESCBC SADB_X_EALG_AES +#endif #define GETMSGSTR(str, num) \ do { \ --- src/setkey/token.l.orig Mon Sep 18 16:20:55 2006 +++ src/setkey/token.l Mon Sep 18 16:22:33 2006 @@ -84,6 +84,9 @@ #ifndef SADB_X_EALG_AESCTR #define SADB_X_EALG_AESCTR (-1) #endif +#if defined(SADB_X_EALG_AES) && ! defined(SADB_X_EALG_AESCBC) +#define SADB_X_EALG_AESCBC SADB_X_EALG_AES +#endif %} /* common section */ --RnlQjJ0d97Da+TV1-- From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 21:19: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 9FF5B16A403 for ; Mon, 18 Sep 2006 21:19:12 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00BA243D53 for ; Mon, 18 Sep 2006 21:19:11 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so423334uge for ; Mon, 18 Sep 2006 14:19:10 -0700 (PDT) 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=bwNp46rqM/Kw+HQZS0+JP/wxrFW0jbaF7GGVATZLW3yUENRjb9Cko4p6p7LAUdxfkicdhbUSxw0sukkarBNi1siwhZirgTTL1N2HDOcTtinv11ny1OZ7Rsr2CD88PDgxzYSBhNO+rvYoQCDs8zRLIbjoK3L2/orL4QlMERtVzEA= Received: by 10.67.21.11 with SMTP id y11mr7520561ugi; Mon, 18 Sep 2006 14:19:10 -0700 (PDT) Received: by 10.67.105.8 with HTTP; Mon, 18 Sep 2006 14:19:09 -0700 (PDT) Message-ID: Date: Mon, 18 Sep 2006 17:19:09 -0400 From: "Scott Ullrich" To: "Larry Baird" In-Reply-To: <20060918180053.73854.qmail@gta.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060918174000.U2478@maildrop.int.zabbadoz.net> <20060918180053.73854.qmail@gta.com> Cc: "\"Bjoern A. Zeeb\"" , freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support 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, 18 Sep 2006 21:19:12 -0000 On 18 Sep 2006 18:00:53 -0000, Larry Baird wrote: > >From my testing on a new 6.x box I just set up, I was wondering if > this was the step that was being left out. Glad to hear it was something > easy. Thanks for all of the help, I am now up and running after the installworld. I should have known better to begin with but regardless, thanks for putting up with all my questions :) Scott From owner-freebsd-net@FreeBSD.ORG Mon Sep 18 21:46:16 2006 Return-Path: X-Original-To: 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 D0F8416A40F; Mon, 18 Sep 2006 21:46:16 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A0E143D49; Mon, 18 Sep 2006 21:46:15 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A7760.dip.t-dialin.net [84.154.119.96]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8ILkApo096250; Mon, 18 Sep 2006 23:46:11 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id k8ILk9wp022437; Mon, 18 Sep 2006 23:46:12 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8ILk9OS014187; Mon, 18 Sep 2006 23:46:09 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Received: (from jhs@localhost) by fire.jhs.private (8.13.6/8.13.6/Submit) id k8ILk9WC014186; Mon, 18 Sep 2006 23:46:09 +0200 (CEST) (envelope-from jhs) Date: Mon, 18 Sep 2006 23:46:09 +0200 (CEST) Message-Id: <200609182146.k8ILk9WC014186@fire.jhs.private> To: Hajimu UMEMOTO From: "Julian Stacey" Organization: http://berklix.com BSD Unix C Net Consultancy, Munich/Muenchen Fcc: sent-mail User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com/~jhs/cv/ X-Fallback: jhs@mail.brierdr.com, jhs@freebsd.org, jhs@berklix.net Cc: Gary Jennejohn , Brian Somers , net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 18 Sep 2006 21:46:16 -0000 > Tested. It Works. Thanks ! > I tested the patch on PPP running under both kernels IPV4+6 & V4only > just to be sure, it works on both, & allows me to type dial & down > (all I tried or wanted.) I'd been wondering why I was the first person to notice the problem. Then I noticed my kernel (unlike GENERIC) did not have device faith (which I had removed thinking I didnt need V6). Not sure if significant, but thought I should mention it. Julian -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Don't buy it ! Get it free ! http://berklix.org/free-software Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 02:52:55 2006 Return-Path: X-Original-To: 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 037E116A407; Tue, 19 Sep 2006 02:52:55 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 549D943D5E; Tue, 19 Sep 2006 02:52:47 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:cp0+V+hmc1X7WriooLOlXcr+t6IrsmeDspAtrCmXgauwLBcNwmZ5iEz2F3guQu+C@localhost [IPv6:::1]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.8/8.13.8) with ESMTP/inet6 id k8J2qK6f010928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Sep 2006 11:52:21 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 19 Sep 2006 11:52:20 +0900 Message-ID: From: Hajimu UMEMOTO To: "Julian Stacey" In-Reply-To: <200609182146.k8ILk9WC014186@fire.jhs.private> References: <200609182146.k8ILk9WC014186@fire.jhs.private> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-pc-freebsd) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.2-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0a6 (ameno.mahoroba.org [IPv6:::1]); Tue, 19 Sep 2006 11:52:22 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.5 X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on ameno.mahoroba.org Cc: Gary Jennejohn , Brian Somers , net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 19 Sep 2006 02:52:55 -0000 Hi, >>>>> On Mon, 18 Sep 2006 23:46:09 +0200 (CEST) >>>>> "Julian Stacey" said: jhs> I'd been wondering why I was the first person to notice the problem. I'm not sure why there was no report about it, but I had never been using inet socket. I don't want to open inet socket for controlling ppp(8) for security reason, and I used to to use just unix domain socket to control ppp(8). jhs> Then I noticed my kernel (unlike GENERIC) did not have jhs> device faith jhs> (which I had removed thinking I didnt need V6). jhs> Not sure if significant, but thought I should mention it. It is for an IPv6-to-IPv4 TCP relay. I think that most of the people are not using it, actually. So, it shouldn't be a problem. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 02:56:39 2006 Return-Path: X-Original-To: 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 01CDD16A416; Tue, 19 Sep 2006 02:56:39 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13CCC43D5A; Tue, 19 Sep 2006 02:56:35 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 2AAEA4D; Mon, 18 Sep 2006 21:56:35 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 8F32F61C3A; Mon, 18 Sep 2006 21:56:34 -0500 (CDT) Date: Mon, 18 Sep 2006 21:56:34 -0500 From: "Matthew D. Fuller" To: Julian Stacey Message-ID: <20060919025634.GA55920@over-yonder.net> References: <200609182146.k8ILk9WC014186@fire.jhs.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609182146.k8ILk9WC014186@fire.jhs.private> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: Gary Jennejohn , Brian Somers , Hajimu UMEMOTO , net@freebsd.org Subject: Re: ppp command port does not listens on ipv4 unless no INET6 in kernel 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, 19 Sep 2006 02:56:39 -0000 On Mon, Sep 18, 2006 at 11:46:09PM +0200 I heard the voice of Julian Stacey, and lo! it spake thus: > > I'd been wondering why I was the first person to notice the problem. Actually, I noticed it a while back (6 months or so? Something like that...) when I tried to run pppctl from my workstation instead of the router. I looked at sockstat, said "Huh, that's kinda annoying", and just always used pppctl from the router. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 06:20: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 EC8D716A407 for ; Tue, 19 Sep 2006 06:20:36 +0000 (UTC) (envelope-from sivakumar.subramani@wipro.com) Received: from wip-ectls-mx1.wipro.com (wip-ectls-mx1.wipro.com [203.91.193.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3DAF43D46 for ; Tue, 19 Sep 2006 06:20:35 +0000 (GMT) (envelope-from sivakumar.subramani@wipro.com) Received: from wip-ectls-mx1.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 65A8722044D for ; Tue, 19 Sep 2006 11:50:41 +0530 (IST) Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92]) by wip-ectls-mx1.wipro.com (Postfix) with ESMTP id 5923E2203C6 for ; Tue, 19 Sep 2006 11:50:41 +0530 (IST) Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Sep 2006 11:50:33 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 19 Sep 2006 11:45:21 +0530 Message-ID: <956E7FA2615F3B4595FC5F22870A72210817F1@blr-m3-msg.wipro.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to access the values of the kenv variables in driver code? Thread-Index: Acbbs7er7Mg/cvjdSumLfV9s83PuTg== From: To: X-OriginalArrivalTime: 19 Sep 2006 06:20:33.0145 (UTC) FILETIME=[B6576E90:01C6DBB3] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: How to access the values of the kenv variables in driver 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: Tue, 19 Sep 2006 06:20:37 -0000 Hi all, =0D I would like to have some of the configuration parameters of my driver to be present as part of the /boot/device.hints file. After adding a variable I could see that variable and it's value as part of kevn's ouput. =0D Can any one please let me know how to access the value of these variables in my drive code? =0D Thanks, ~Siva The information contained in this electronic message and any attachments to= this message are intended for the exclusive use of the addressee(s) and= may contain proprietary, confidential or privileged information. If you= are not the intended recipient, you should not disseminate, distribute or= copy this e-mail. Please notify the sender immediately and destroy all= copies of this message and any attachments.=0D WARNING: Computer viruses can be transmitted via email. The recipient= should check this email and any attachments for the presence of viruses.= The company accepts no liability for any damage caused by any virus= transmitted by this email. =0D www.wipro.com From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 08:05: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 B74EF16A403 for ; Tue, 19 Sep 2006 08:05:01 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from leia.fdn.fr (ns0.fdn.org [80.67.169.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B8C943D45 for ; Tue, 19 Sep 2006 08:05:00 +0000 (GMT) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by leia.fdn.fr (8.13.3/8.13.3/FDN) with ESMTP id k8J84uDl001586 for ; Tue, 19 Sep 2006 10:04:59 +0200 Received: by smtp.zeninc.net (smtpd, from userid 1000) id 6972D3F17; Tue, 19 Sep 2006 10:04:51 +0200 (CEST) Date: Tue, 19 Sep 2006 10:04:51 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20060919080451.GA3502@zen.inc> References: <20060918180053.73854.qmail@gta.com> <20060918210519.J978@hades.admin.frm2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060918210519.J978@hades.admin.frm2> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: FAST_IPSEC NAT-T support 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, 19 Sep 2006 08:05:01 -0000 On Mon, Sep 18, 2006 at 09:43:41PM +0200, Joerg Pulz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, Hi. > first of all, a big thanks to Yvan and Larry, and all others, for their > work. IPSEC_NAT_T is working fine for me with either IPSEC or FAST_IPSEC > with RELENG_6 as server and FAST_IPSEC with CURRENT (small modifications > after patching where necessary) as client. Yes, I know there are small (quite all indentation) changes since RELENG_6 which needs a separate patch. > Regarding the /sbin/setkey against ${LOCALBASE}/sbin/setkey (ipsec-tools > version) discussion, i found a minor difference in the output between > those two when using aes/rijndael encryption and executing "setkey -D". > The FreeBSD base version of setkey outputs something like this: > E: rijndael-cbc XXXXXXXX ... > and the ipsec-tools version of setkey outputs this: > E: 12 XXXXXXXX ... > > The difference comes out of libipsec/pfkey_dump.c . > In the FreeBSD base version of this file we have this: > #ifdef SADB_X_EALG_RIJNDAELCBC > { SADB_X_EALG_RIJNDAELCBC, "rijndael-cbc", }, > #endif > > and in the ipsec-tools version this: > #ifdef SADB_X_EALG_AESCBC > { SADB_X_EALG_AESCBC, "aes-cbc", }, > #endif Rijndael IS AES, and AES is now the "official" name.... > Unfortunately, we have no definition for SADB_X_EALG_AESCBC in FreeBSD's > pfkeyv2.h file. The definition for encryption algorithm number 12 in > pfkeyv2.h is the following: > #define SADB_X_EALG_RIJNDAELCBC 12 > #define SADB_X_EALG_AES 12 > > I'm not sure which one is right in this case, but as a quick fix i've > attached two small patches for the ipsec-tools port. > Simply copy both files to ${PORTSDIR}/security/ipsec-tools/files and > rebuild/reinstall the port. Larry provided very quickly another patch which does the reverse thing (always find AES), and I reported the patch to ipsec-tools HEAD, so it will be on 0.7 branch (should come soon). If there is a real need to include that patch in FreeBSD's port before that, please submit a pr and I'll add the patch to FreeBSD's port. Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 08:43: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 2837216A556; Tue, 19 Sep 2006 08:43:12 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E2343E3F; Tue, 19 Sep 2006 08:21:43 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k8J8LeGh005618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Sep 2006 12:21:41 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k8J8Lenl005617; Tue, 19 Sep 2006 12:21:40 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 19 Sep 2006 12:21:40 +0400 From: Gleb Smirnoff To: Jack Vogel Message-ID: <20060919082140.GW27667@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Jack Vogel , freebsd-net , Prafulla Deuskar References: <2a41acea0609111402g68741d86ib185e9bb77908658@mail.gmail.com> <20060915142330.GS27667@FreeBSD.org> <2a41acea0609151901v5f24643dv4cf550a5108e1052@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <2a41acea0609151901v5f24643dv4cf550a5108e1052@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: freebsd-net , Prafulla Deuskar Subject: Re: Stale PCI ID 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, 19 Sep 2006 08:43:12 -0000 Jack, On Fri, Sep 15, 2006 at 07:01:25PM -0700, Jack Vogel wrote: J> >J> In the last attempt to merge community CVS with Intel internal code I J> >J> came across an issue I'd like to bring up. J> >J> J> >J> There is an ancient e1000 card, pci id 1000, an 82542, that we J> >J> don't have in our source, yet community cvs still does. Support J> >J> for this was removed from Linux long ago because the card did J> >J> not even work. J> >J> J> >J> I just had our test group hunt up one of these and test, and sure J> >J> enough, the driver recognizes it, but it does NOT pass traffic. J> >J> J> >J> Clearly no one is using these, at least not with STABLE :) and J> >J> as Intel does not want to support this I would recommend removing J> >J> the ID from the driver. J> >J> J> >J> Comments? J> > J> >It should be removed then. When merging the Intel versions of driver to J> >FreeBSD, I've noticed that some PCI IDs disappeared from vendor driver. J> >Since I couldn't obtain any comments from the release tarball, I decided J> >to be on safe side and leave these PCI IDs in the driver untouched. J> > J> >Which exact one are you speaking about? The E1000_DEV_ID_82542, that is J> >equal to 0x1000 is supported by em-6.1.4 vendor's driver. J> J> I AM the vendor :) And I believe that the 0x1000 ID crept into my code J> from merging with your tree :) Our test group came back to me and J> said 'hey, this is old and we don't think these boards even work' , so J> I told them to test, they did, and sure enough, it wouldnt even pass J> traffic. AFAIK, the mega merge with FreeBSD code was made in version 6.0.5. But the E1000_DEV_ID_82542 is also present in em-3.2.18 and em-5.1.5 drivers. That's why I am unsure that it is the one that needs to be removed. J> There is actually 3 different rev boards, and rumor has it that the J> last revision would work, but I think its better to just drop the thing. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 09:01:08 2006 Return-Path: X-Original-To: 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 D580D16A4EA; Tue, 19 Sep 2006 09:01:08 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C839D442C6; Tue, 19 Sep 2006 08:34:52 +0000 (GMT) (envelope-from vova@sw.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GPb46-0002XK-2H; Tue, 19 Sep 2006 12:34:50 +0400 From: Vladimir Grebenschikov To: current Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 19 Sep 2006 12:34:48 +0400 Message-Id: <1158654888.1533.17.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-net Subject: iwi driver: ioctl[SIOCS80211, op 21, len 42]: Invalid argument X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 09:01:09 -0000 Hi i am triing to connect Intel(R) PRO/Wireless 2200BG - iwi0 to WPA-EAP wireless network with PEAP: # wpa_supplicant -i iwi0 -c /usr/local/etc/wpa_supplicant.conf Trying to associate with SSID 'OFFICE-PEAP' ioctl[SIOCS80211, op 21, len 42]: Invalid argument Association request to the driver failed ... # kldstat | egrep wlan\|iwi 28 1 0xc0892000 2d08 wlan_wep.ko 29 5 0xc0895000 1ed74 wlan.ko 52 1 0xc4ff9000 7000 wlan_ccmp.ko 53 1 0xc5000000 4000 wlan_tkip.ko 54 1 0xc3828000 2000 wlan_xauth.ko 57 1 0xc4f36000 d000 if_iwi.ko # changing ap_scan=2 >> ap_scan=1 improves situation a bit, but still does not work: ... State: DISCONNECTED -> SCANNING Starting AP scan (broadcast SSID) Received 0 bytes of scan results (3 BSSes) Scan results: 3 Selecting BSS from priority group 0 0: 00:14:a5:0e:eb:60 ssid='COME' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 1: 00:18:b9:2a:c4:50 ssid='OFFICE' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:13:46:fe:c2:ff ssid='pmp' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE No suitable AP found. Setting scan request: 5 sec 0 usec Starting AP scan (broadcast SSID) Received 0 bytes of scan results (1 BSSes) Scan results: 1 Selecting BSS from priority group 0 0: 00:18:b9:2a:c4:50 ssid='OFFICE' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE No suitable AP found. Setting scan request: 5 sec 0 usec ... any hints will be really appreciated. -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 09:59: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 D317816A416 for ; Tue, 19 Sep 2006 09:59:05 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B959B43D5A for ; Tue, 19 Sep 2006 09:59:04 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k8J9wxDn069005; Tue, 19 Sep 2006 12:58:59 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k8J9wxqW069002; Tue, 19 Sep 2006 12:58:59 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Tue, 19 Sep 2006 12:58:59 +0300 (EEST) From: Dmitry Pryanishnikov To: Pyun YongHyeon In-Reply-To: <20060918124431.GD30078@cdnetworks.co.kr> Message-ID: <20060919125046.E35560@atlantis.atlantis.dp.ua> References: <20060918150510.D33680@atlantis.atlantis.dp.ua> <20060918124431.GD30078@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Marvell YukonII Status Update? 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, 19 Sep 2006 09:59:05 -0000 Hello! On Mon, 18 Sep 2006, Pyun YongHyeon wrote: > > 1. Has situation with this driver improved somehow (is somebody going to > > support it and commit into the CURRENT)? > > > > I'm working on it. Unlike OpenBSD/NetBSD msk(4) my code is based on > sk(4) and myk(4) from Marvell. I've managed to send packets with new > driver but it needs more testing and codes to support hardware > features(VLAN tagging, TSO support, RX checksum offload etc). I can't > sure TSO support could be done due to lack of documentation. Wow, great! Where can I get the latest version of your driver for fresh RELENG_6? I'm willing to test it! I could live w/o TSO support and RX checksum offload; while hardware VLAN tagging is desirable feature. Does your driver support software VLAN tagging currently? > > 2. What kinds of performance problems / stability issues should I expect > > with the driver in it's current state under 6-STABLE? > You can see lots of witness warnings. Unloading the driver module or Indeed (after enabling WITNESS, loading the module and just connecting the cable): myk0: link up lock order reversal: 1st 0xc4c13084 LE Status (LE Status) @ sky2.c:1757 2nd 0xc4c131d0 Tx LE async port 1 (Tx LE async port 1) @ sky2.c:2877 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c06550e0,c06551a8,c0624924,...) at 0xc04b3eed = kdb_backtrace+0x29 witness_checkorder(c4c131d0,9,c087a299,b3d) at 0xc04be9a8 = witness_checkorder+0x578 _mtx_lock_flags(c4c131d0,0,c087a299,b3d,80246,...) at 0xc0494278 = _mtx_lock_flags+0x78 ProcessStatusList(c04ad267,40000000,2,c05f4e6c,267,...) at 0xc085757d = ProcessStatusList+0x2c9 Yk2IntServiceRoutine(c4c10000) at 0xc0857f70 = Yk2IntServiceRoutine+0x150 ithread_execute_handlers(c4bae218,c4ae0280) at 0xc0488ed6 = ithread_execute_handlers+0xe6 ithread_loop(c4c09be0,e35a5d38,c4c09be0,c0488f94,0,...) at 0xc0488ffa = ithread_loop+0x66 fork_exit(c0488f94,c4c09be0,e35a5d38) at 0xc0488144 = fork_exit+0xa0 fork_trampoline() at 0xc05b745c = fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe35a5d6c, ebp = 0 --- > using Jumboframe may panic your system. Thanks for the information! > Regards, > Pyun YongHyeon Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 10:55:37 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 7AE2616A51B for ; Tue, 19 Sep 2006 10:55:37 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3D4943D53 for ; Tue, 19 Sep 2006 10:55:36 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (bqjylq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8JAtTU4067913; Tue, 19 Sep 2006 12:55:34 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8JAtSeJ067912; Tue, 19 Sep 2006 12:55:28 +0200 (CEST) (envelope-from olli) Date: Tue, 19 Sep 2006 12:55:28 +0200 (CEST) Message-Id: <200609191055.k8JAtSeJ067912@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG, sivakumar.subramani@wipro.com In-Reply-To: <956E7FA2615F3B4595FC5F22870A72210817F1@blr-m3-msg.wipro.com> X-Newsgroups: list.freebsd-net User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 19 Sep 2006 12:55:35 +0200 (CEST) Cc: Subject: Re: How to access the values of the kenv variables in driver code? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG, sivakumar.subramani@wipro.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 10:55:37 -0000 sivakumar.subramani@wipro.com wrote: > I would like to have some of the configuration parameters of my driver > to be present as part of the /boot/device.hints file. After adding a > variable I could see that variable and it's value as part of kevn's > ouput. > > Can any one please let me know how to access the value of these > variables in my drive code? >From sys/kern/kern_environment.c: /* * The unified bootloader passes us a pointer to a preserved copy of * bootstrap/kernel environment variables. We convert them to a * dynamic array of strings later when the VM subsystem is up. * * We make these available through the kenv(2) syscall for userland * and through getenv()/freeenv() setenv() unsetenv() testenv() for * the kernel. */ The following shell command will give you lots of examples: find /usr/src/sys -name "*.c" | xargs grep -w getenv Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++: "an octopus made by nailing extra legs onto a dog" -- Steve Taylor, 1998 From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 12:00:44 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 9F3CC16A4C9 for ; Tue, 19 Sep 2006 12:00:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9E8B43D7C for ; Tue, 19 Sep 2006 12:00:40 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so1717238nzn for ; Tue, 19 Sep 2006 05:00:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=fW7I4h5EsxB2kjhLB7pifwRLMQpY44WOBdMUaWoXQsPLKkPFXHeI5Oco8Gzx/2ZxHPcXnoGQguoWnjWkR+vcNyTsksJ/PPerMZFz5ZBT1mjuPmlkh38+PqNBG9dHa+gF0nmEOReA7BfpgKzGlvGpcGrWLgUems3eNnKGazsZ70g= Received: by 10.64.180.4 with SMTP id c4mr17900116qbf; Tue, 19 Sep 2006 05:00:37 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 6sm1576564nzn.2006.09.19.05.00.35; Tue, 19 Sep 2006 05:00:37 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k8JC1Qik037201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Sep 2006 21:01:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k8JC1PRw037200; Tue, 19 Sep 2006 21:01:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 19 Sep 2006 21:01:25 +0900 From: Pyun YongHyeon To: Dmitry Pryanishnikov Message-ID: <20060919120125.GA34461@cdnetworks.co.kr> References: <20060918150510.D33680@atlantis.atlantis.dp.ua> <20060918124431.GD30078@cdnetworks.co.kr> <20060919125046.E35560@atlantis.atlantis.dp.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060919125046.E35560@atlantis.atlantis.dp.ua> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: Marvell YukonII Status Update? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 12:00:44 -0000 On Tue, Sep 19, 2006 at 12:58:59PM +0300, Dmitry Pryanishnikov wrote: > > Hello! > > On Mon, 18 Sep 2006, Pyun YongHyeon wrote: > >> 1. Has situation with this driver improved somehow (is somebody going to > >> support it and commit into the CURRENT)? > >> > > > >I'm working on it. Unlike OpenBSD/NetBSD msk(4) my code is based on > >sk(4) and myk(4) from Marvell. I've managed to send packets with new > >driver but it needs more testing and codes to support hardware > >features(VLAN tagging, TSO support, RX checksum offload etc). I can't > >sure TSO support could be done due to lack of documentation. > > Wow, great! Where can I get the latest version of your driver for fresh > RELENG_6? I'm willing to test it! I could live w/o TSO support and RX Unfortunately it's only for CURRENT at the moment and it needs big cleanups. Rx TCP/UDP checksum offload has the same issue I've seen on sk(4). I've tried every possible combinations I can think of but have no clue yet. Personally I think checksum offload has more important than that of TSO. If any guys know the magic of Rx checksum offload on Yukon II please let me know. > checksum > offload; while hardware VLAN tagging is desirable feature. Does your driver > support software VLAN tagging currently? > Yes. Today, I've made hardware VLAN tag insertion/stripping work. I'll post my code when it's ready for more testing. > >> 2. What kinds of performance problems / stability issues should I expect > >> with the driver in it's current state under 6-STABLE? > >You can see lots of witness warnings. Unloading the driver module or > > Indeed (after enabling WITNESS, loading the module and just connecting the > cable): > > myk0: link up > lock order reversal: > 1st 0xc4c13084 LE Status (LE Status) @ sky2.c:1757 > 2nd 0xc4c131d0 Tx LE async port 1 (Tx LE async port 1) @ sky2.c:2877 > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c06550e0,c06551a8,c0624924,...) at 0xc04b3eed = > kdb_backtrace+0x29 > witness_checkorder(c4c131d0,9,c087a299,b3d) at 0xc04be9a8 = > witness_checkorder+0x578 > _mtx_lock_flags(c4c131d0,0,c087a299,b3d,80246,...) at 0xc0494278 = > _mtx_lock_flags+0x78 > ProcessStatusList(c04ad267,40000000,2,c05f4e6c,267,...) at 0xc085757d = > ProcessStatusList+0x2c9 > Yk2IntServiceRoutine(c4c10000) at 0xc0857f70 = Yk2IntServiceRoutine+0x150 > ithread_execute_handlers(c4bae218,c4ae0280) at 0xc0488ed6 = > ithread_execute_handlers+0xe6 > ithread_loop(c4c09be0,e35a5d38,c4c09be0,c0488f94,0,...) at 0xc0488ffa = > ithread_loop+0x66 > fork_exit(c0488f94,c4c09be0,e35a5d38) at 0xc0488144 = fork_exit+0xa0 > fork_trampoline() at 0xc05b745c = fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xe35a5d6c, ebp = 0 --- > > >using Jumboframe may panic your system. > > Thanks for the information! > > >Regards, > >Pyun YongHyeon > > Sincerely, Dmitry > -- > Atlantis ISP, System Administrator > e-mail: dmitry@atlantis.dp.ua > nic-hdl: LYNX-RIPE -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 12:20:46 2006 Return-Path: X-Original-To: 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 1BFD516A407; Tue, 19 Sep 2006 12:20:46 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A63143D45; Tue, 19 Sep 2006 12:20:44 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.182.250] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1GPeaQ0kuY-0004T0; Tue, 19 Sep 2006 14:20:42 +0200 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org, vova@fbsd.ru Date: Tue, 19 Sep 2006 14:20:16 +0200 User-Agent: KMail/1.9.3 References: <1158654888.1533.17.camel@localhost> In-Reply-To: <1158654888.1533.17.camel@localhost> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3837701.atdZd998Nb"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200609191420.24870.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-net Subject: Re: iwi driver: ioctl[SIOCS80211, op 21, len 42]: Invalid argument 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, 19 Sep 2006 12:20:46 -0000 --nextPart3837701.atdZd998Nb Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 19 September 2006 10:34, Vladimir Grebenschikov wrote: > i am triing to connect Intel(R) PRO/Wireless 2200BG - iwi0 to WPA-EAP > wireless network with PEAP: > > # wpa_supplicant -i iwi0 -c /usr/local/etc/wpa_supplicant.conf > Trying to associate with SSID 'OFFICE-PEAP' > ioctl[SIOCS80211, op 21, len 42]: Invalid argument > Association request to the driver failed > ... Are you sure userland and kernel are in sync? Did you install possibly=20 changed include files before rebuilding wpa_supplicant? > # kldstat | egrep wlan\|iwi > 28 1 0xc0892000 2d08 wlan_wep.ko > 29 5 0xc0895000 1ed74 wlan.ko > 52 1 0xc4ff9000 7000 wlan_ccmp.ko > 53 1 0xc5000000 4000 wlan_tkip.ko > 54 1 0xc3828000 2000 wlan_xauth.ko > 57 1 0xc4f36000 d000 if_iwi.ko > # > > changing ap_scan=3D2 >> ap_scan=3D1 > improves situation a bit, but still does not work: > > ... > State: DISCONNECTED -> SCANNING > Starting AP scan (broadcast SSID) > Received 0 bytes of scan results (3 BSSes) > Scan results: 3 > Selecting BSS from priority group 0 > 0: 00:14:a5:0e:eb:60 ssid=3D'COME' wpa_ie_len=3D0 rsn_ie_len=3D0 caps=3D0= x31 > skip - no WPA/RSN IE > 1: 00:18:b9:2a:c4:50 ssid=3D'OFFICE' wpa_ie_len=3D0 rsn_ie_len=3D0 caps= =3D0x31 > skip - no WPA/RSN IE > 2: 00:13:46:fe:c2:ff ssid=3D'pmp' wpa_ie_len=3D0 rsn_ie_len=3D0 caps=3D0x= 31 > skip - no WPA/RSN IE > No suitable AP found. > Setting scan request: 5 sec 0 usec > Starting AP scan (broadcast SSID) > Received 0 bytes of scan results (1 BSSes) > Scan results: 1 > Selecting BSS from priority group 0 > 0: 00:18:b9:2a:c4:50 ssid=3D'OFFICE' wpa_ie_len=3D0 rsn_ie_len=3D0 caps= =3D0x31 > skip - no WPA/RSN IE > No suitable AP found. > Setting scan request: 5 sec 0 usec > ... > > any hints will be really appreciated. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3837701.atdZd998Nb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFD+CIXyyEoT62BG0RAlUNAJ43qeGfnRiHO8P93FNL/uwcJqW78gCdGQ4p RO+dXVzt9c3tFEc5fsjds6k= =X/Er -----END PGP SIGNATURE----- --nextPart3837701.atdZd998Nb-- From owner-freebsd-net@FreeBSD.ORG Tue Sep 19 16:33:14 2006 Return-Path: X-Original-To: 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 6D95516A40F; Tue, 19 Sep 2006 16:33:14 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82A7D43D55; Tue, 19 Sep 2006 16:33:07 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k8JGWsvQ013330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Sep 2006 09:32:59 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <45101BB6.8050205@errno.com> Date: Tue, 19 Sep 2006 09:32:54 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: vova@fbsd.ru References: <1158654888.1533.17.camel@localhost> In-Reply-To: <1158654888.1533.17.camel@localhost> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current , freebsd-net Subject: Re: iwi driver: ioctl[SIOCS80211, op 21, len 42]: Invalid argument 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, 19 Sep 2006 16:33:14 -0000 Vladimir Grebenschikov wrote: > Hi > > i am triing to connect Intel(R) PRO/Wireless 2200BG - iwi0 to WPA-EAP > wireless network with PEAP: > > # wpa_supplicant -i iwi0 -c /usr/local/etc/wpa_supplicant.conf > Trying to associate with SSID 'OFFICE-PEAP' > ioctl[SIOCS80211, op 21, len 42]: Invalid argument > Association request to the driver failed > ... "op 21" is the request to associate. The error most likely indicates the kernel had no information about the ap at the point where the ioctl was issued. Adding -d to the command line would provide useful info. > > # kldstat | egrep wlan\|iwi > 28 1 0xc0892000 2d08 wlan_wep.ko > 29 5 0xc0895000 1ed74 wlan.ko > 52 1 0xc4ff9000 7000 wlan_ccmp.ko > 53 1 0xc5000000 4000 wlan_tkip.ko > 54 1 0xc3828000 2000 wlan_xauth.ko > 57 1 0xc4f36000 d000 if_iwi.ko > # > > changing ap_scan=2 >> ap_scan=1 > improves situation a bit, but still does not work: ap_scan has no effect on freebsd if I recall; it's really intended for linux and other os's where a variety of drivers hook up to wpa_supplicant. On freebsd all drivers (except for ndis) go through net80211 and scanning is handled uniformly. > > ... > State: DISCONNECTED -> SCANNING > Starting AP scan (broadcast SSID) > Received 0 bytes of scan results (3 BSSes) > Scan results: 3 > Selecting BSS from priority group 0 > 0: 00:14:a5:0e:eb:60 ssid='COME' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > skip - no WPA/RSN IE > 1: 00:18:b9:2a:c4:50 ssid='OFFICE' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > skip - no WPA/RSN IE > 2: 00:13:46:fe:c2:ff ssid='pmp' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > skip - no WPA/RSN IE > No suitable AP found. > Setting scan request: 5 sec 0 usec > Starting AP scan (broadcast SSID) > Received 0 bytes of scan results (1 BSSes) > Scan results: 1 > Selecting BSS from priority group 0 > 0: 00:18:b9:2a:c4:50 ssid='OFFICE' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > skip - no WPA/RSN IE > No suitable AP found. > Setting scan request: 5 sec 0 usec > ... > > any hints will be really appreciated. > From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 06: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 34D9E16A550 for ; Wed, 20 Sep 2006 06:22:05 +0000 (UTC) (envelope-from gjizziisdai@classifiedtoday.com) Received: from classifiedtoday.com (cmo116.neoplus.adsl.tpnet.pl [83.31.142.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 1FE8843D73 for ; Wed, 20 Sep 2006 06:21:31 +0000 (GMT) (envelope-from gjizziisdai@classifiedtoday.com) Received: from 83.31.142.116 by classifiedtoday.com Date: Wed, 20 Sep 2006 08:21:30 +0100 From: "Mina reade" X-Sender: gjizziisdai@classifiedtoday.com To: Message-Id: <9493951592.MrbbLqwcWTL-86564-8253967@classifiedtoday.com> MIME-Version: 1.0 Content-Type: text/plain Subject: A stepping stone to. 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, 20 Sep 2006 06:22:05 -0000 HOT ALERT - THIS ONE IS STILL CLIMBING THE CHARTS ALERT -- BREAKING MARKET NEWS REPORT ---- WBRS.PK Company Name: WILD BRUSH ENERGY Lookup: WBRS.PK Current Price: .05 Expected: STEADILY CLIMB FOR THE TOP Breaking News: Wild Brush Acquires Additional Powder River Oil & Gas Lease Wild Brush Energy (PINKSHEETS: WBRS) announces the purchase of an additional Powder River Basin Federal Oil & Gas Lease in the State of Wyoming. The lease is located on the eastern side of the Basin in Weston County. This is the fifth lease the Company now controls in the region. Wild Brush maintains its expansion strategy through acquisition of low risk, high probability oil and gas properties in proven regions such as Powder River basin. Wild Brush will continue to concentrate on the Powder River Basin area, due to the number of lease acre ages it currently controls. The Powder River Basin claims a high probability rate of discoveries and proven production as demonstrated by such companies as Chevron and Western Gas. There are presently over 12,000 gas wells, in addition to nearly 400 new wells monthly, producing over 330 billion cubic feet annually, in an area with an estimated 32 trillion cubic feet of natural gas. About WBRS.PK Wild Brush Energy is a diversified energy company whose primary goal is to identify and develop Oil & Coalbed Methane sites within the State of Wyoming. In addition, Wild Brush Energy continues to evaluate clean air alternative energy producing technologies such as Wind Power. Wild Brush trades in the U.S. under the symbol "WBRS." WATCH THIS STOCK GO HIGHER AND HIGHER -------------------------------------------------------------------------------- You have to see the results to believe them once you see, you'll be convinced why this is a MUST B U Y ----------------------- She has a green thumb. Weed out. Sturdy as an oak. Two peas in a pod. There may be snow on the roof, but there's fire in the belly. Season of mists and mellow fruitfulness. Stuck in a rut. We'll hand you out to dry. So hungry I could eat a horse. They're like two peas in a pod. To live from hand to mouth. Season of mists and mellow fruitfulness. Stubborn as a mule. Sow much, reap much; sow little, reap little. Spill the beans. That's water under the bridge. Through the grapevine. The way to a man's heart is through his stomach. Water doesn't run uphill. This is for the birds. To gild refined gold, to paint the lily. Sow much, reap much; sow little, reap little. Water it down. To rule the mountains is to rule the river. Spring rain, Fall gold. Timber! When pigs fly. Your barking up the wrong tree. Sweating blood. You can lead a horse to water but you can't make him drink. Were you born in a barn? Worry often gives a small thing a big shadow. Strong as an ox. There may be snow on the roof, but there's fire in the belly. Timing is everything. Shiver me timber. Schools out for summer. Your name is mud. When the cows come home. Play a harp before a cow. Which came first, the chicken or the egg. What's done is done. Schools out for summer. From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 07:35:36 2006 Return-Path: X-Original-To: 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 4290916A47C for ; Wed, 20 Sep 2006 07:35:36 +0000 (UTC) (envelope-from hnscghbtus@cndata.com) Received: from cndata.com (30.248.71.218.broad.nb.zj.dynamic.cndata.com [218.71.248.30]) by mx1.FreeBSD.org (Postfix) with SMTP id D1C4943D49 for ; Wed, 20 Sep 2006 07:35:33 +0000 (GMT) (envelope-from hnscghbtus@cndata.com) Received: from 218.71.248.30 by cndata.com Date: Wed, 20 Sep 2006 15:36:28 -0800 From: "Rachel levey" X-Sender: hnscghbtus@cndata.com To: Message-Id: <6428226879.FxyaAayM-6733-1504034@cndata.com> MIME-Version: 1.0 Content-Type: text/plain Cc: Subject: To live from hand to mouth. 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, 20 Sep 2006 07:35:36 -0000 HOT ALERT - THIS ONE IS STILL CLIMBING THE CHARTS ALERT -- BREAKING MARKET NEWS REPORT ---- WBRS.PK Company Name: WILD BRUSH ENERGY Lookup: WBRS.PK Current Price: .05 Expected: STEADILY CLIMB FOR THE TOP Breaking News: Wild Brush Acquires Additional Powder River Oil & Gas Lease Wild Brush Energy (PINKSHEETS: WBRS) announces the purchase of an additional Powder River Basin Federal Oil & Gas Lease in the State of Wyoming. The lease is located on the eastern side of the Basin in Weston County. This is the fifth lease the Company now controls in the region. Wild Brush maintains its expansion strategy through acquisition of low risk, high probability oil and gas properties in proven regions such as Powder River basin. Wild Brush will continue to concentrate on the Powder River Basin area, due to the number of lease acre ages it currently controls. The Powder River Basin claims a high probability rate of discoveries and proven production as demonstrated by such companies as Chevron and Western Gas. There are presently over 12,000 gas wells, in addition to nearly 400 new wells monthly, producing over 330 billion cubic feet annually, in an area with an estimated 32 trillion cubic feet of natural gas. About WBRS.PK Wild Brush Energy is a diversified energy company whose primary goal is to identify and develop Oil & Coalbed Methane sites within the State of Wyoming. In addition, Wild Brush Energy continues to evaluate clean air alternative energy producing technologies such as Wind Power. Wild Brush trades in the U.S. under the symbol "WBRS." WATCH THIS STOCK GO HIGHER AND HIGHER -------------------------------------------------------------------------------- See the results for your self once you see, you'll be convinced why this is a MUST B U Y ----------------------- Tossed around like a hot potato. Useless as tits on bull. This is for the birds. Raking it in. Tools of the trade. This is for the birds. Sweet as honey. Say it with flowers. You say potayto, I say potahto. You never miss the water till the well runs dry. Stubborn as a mule. We'll cross that bridge when we come to it. Water under the bridge. You can lead a horse to water but you can't make him drink. Walking on cloud nine. Seed money. Shiver me timber. The silly season. The stronger the breeze the stronger the trees. Stone cold sober. Sweet as honey. Slow as a snail. You can't teach an old dog new tricks. Speak softly and carry a big stick. Weed out. Spaceship earth. Ugly as a mud fence. Stop and smell the roses. Weed 'um and reap. Still waters run deep. Sow dry and set wet. Sly as a fox. Timber! Water doesn't run uphill. Tossed around like a hot potato. From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 08:05:32 2006 Return-Path: X-Original-To: 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 5990816A416; Wed, 20 Sep 2006 08:05:32 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA6D43D69; Wed, 20 Sep 2006 08:05:31 +0000 (GMT) (envelope-from vova@sw.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GPx5C-000Nhh-U4; Wed, 20 Sep 2006 12:05:26 +0400 In-Reply-To: <45101BB6.8050205@errno.com> To: Sam Leffler Date: Wed, 20 Sep 2006 12:05:26 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL122i (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: From: Vladimir Grebenschikov Cc: vova@fbsd.ru, current , freebsd-net Subject: Re: iwi driver: ioctl[SIOCS80211, op 21, len 42]: Invalid argument 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, 20 Sep 2006 08:05:32 -0000 [ Charset ISO-8859-1 unsupported, converting... ] > Vladimir Grebenschikov wrote: > > Hi > > > > i am triing to connect Intel(R) PRO/Wireless 2200BG - iwi0 to WPA-EAP > > wireless network with PEAP: > > > > # wpa_supplicant -i iwi0 -c /usr/local/etc/wpa_supplicant.conf > > Trying to associate with SSID 'OFFICE-PEAP' > > ioctl[SIOCS80211, op 21, len 42]: Invalid argument > > Association request to the driver failed > > ... > > "op 21" is the request to associate. The error most likely indicates > the kernel had no information about the ap at the point where the ioctl > was issued. Adding -d to the command line would provide useful info. ... Initializing interface (2) 'iwi0' EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Own MAC address: 00:0e:35:03:82:74 wpa_driver_bsd_set_wpa: enabled=1 wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_set_countermeasures: enabled=0 wpa_driver_bsd_set_drop_unencrypted: enabled=1 Setting scan request: 0 sec 100000 usec Added interface iwi0 State: DISCONNECTED -> SCANNING Trying to associate with SSID 'OFFICE-PEAP' Cancelling scan request WPA: clearing own WPA/RSN IE Automatic auth_alg selection: 0x1 wpa_driver_bsd_set_auth_alg alg 0x1 authmode 1 WPA: clearing AP WPA IE WPA: clearing AP RSN IE WPA: clearing own WPA/RSN IE No keys have been configured - skip key clearing wpa_driver_bsd_set_drop_unencrypted: enabled=1 State: SCANNING -> ASSOCIATING wpa_driver_bsd_associate: ssid 'OFFICE-PEAP' wpa ie len 0 pairwise 4 group 4 key mgmt 3 wpa_driver_bsd_associate: set PRIVACY 1 Association request to the driver failed Setting authentication timeout: 5 sec 0 usec EAPOL: External notification - portControl=Auto CTRL-EVENT-TERMINATING - signal 2 received Removing interface iwi0 State: ASSOCIATING -> DISCONNECTED No keys have been configured - skip key clearing EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 wpa_driver_bsd_set_wpa: enabled=0 wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 wpa_driver_bsd_set_drop_unencrypted: enabled=0 wpa_driver_bsd_set_countermeasures: enabled=0 No keys have been configured - skip key clearing wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=1 Cancelling scan request ... > > > > # kldstat | egrep wlan\|iwi > > 28 1 0xc0892000 2d08 wlan_wep.ko > > 29 5 0xc0895000 1ed74 wlan.ko > > 52 1 0xc4ff9000 7000 wlan_ccmp.ko > > 53 1 0xc5000000 4000 wlan_tkip.ko > > 54 1 0xc3828000 2000 wlan_xauth.ko > > 57 1 0xc4f36000 d000 if_iwi.ko > > # Kernel and userland in sync, just rebuild everithing for sure. I've tried with and without wlan_ccmp.ko wlan_tkip.ko - no any difference (they should not be used in may case) > > changing ap_scan=2 >> ap_scan=1 > > improves situation a bit, but still does not work: > > ap_scan has no effect on freebsd if I recall; it's really intended for > linux and other os's where a variety of drivers hook up to > wpa_supplicant. On freebsd all drivers (except for ndis) go through > net80211 and scanning is handled uniformly. > > > > > ... > > State: DISCONNECTED -> SCANNING > > Starting AP scan (broadcast SSID) > > Received 0 bytes of scan results (3 BSSes) > > Scan results: 3 > > Selecting BSS from priority group 0 > > 0: 00:14:a5:0e:eb:60 ssid='COME' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > > skip - no WPA/RSN IE > > 1: 00:18:b9:2a:c4:50 ssid='OFFICE' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > > skip - no WPA/RSN IE > > 2: 00:13:46:fe:c2:ff ssid='pmp' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > > skip - no WPA/RSN IE > > No suitable AP found. > > Setting scan request: 5 sec 0 usec > > Starting AP scan (broadcast SSID) > > Received 0 bytes of scan results (1 BSSes) > > Scan results: 1 > > Selecting BSS from priority group 0 > > 0: 00:18:b9:2a:c4:50 ssid='OFFICE' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 > > skip - no WPA/RSN IE > > No suitable AP found. > > Setting scan request: 5 sec 0 usec > > ... > > > > any hints will be really appreciated. > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 11:03:37 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 079B316A403; Wed, 20 Sep 2006 11:03:37 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id E37EF43D68; Wed, 20 Sep 2006 11:03:32 +0000 (GMT) (envelope-from rrs@cisco.com) Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-5.cisco.com with ESMTP; 20 Sep 2006 04:03:32 -0700 X-IronPort-AV: i="4.09,190,1157353200"; d="scan'208"; a="323197724:sNHT32549588" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k8KB3WQd031130; Wed, 20 Sep 2006 04:03:32 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k8KB3Sw7019050; Wed, 20 Sep 2006 04:03:32 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 20 Sep 2006 04:03:27 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Sep 2006 04:03:27 -0700 Message-ID: <45112005.7030503@cisco.com> Date: Wed, 20 Sep 2006 07:03:33 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417 FreeBSD/i386 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <44F35A65.3080605@cisco.com> <20060828224452.GK37035@funkthat.com> <44F45A2A.8030405@freebsd.org> <20060902081043.J32527@mp2.macomnet.net> <44F9386A.30804@freebsd.org> In-Reply-To: <44F9386A.30804@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Sep 2006 11:03:27.0166 (UTC) FILETIME=[660F3DE0:01C6DCA4] DKIM-Signature: a=rsa-sha1; q=dns; l=1740; t=1158750212; x=1159614212; c=relaxed/simple; s=sjdkim5002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:Randall=20Stewart=20 |Subject:Re=3A=20Problem=20with=20uipc_mbuf.c; X=v=3Dcisco.com=3B=20h=3DGX4otkzfuvQkPAK8JGkm7Q3VVZc=3D; b=TW14su0hkmSv1b/+S/zGXY/e/sxtA4uwQrqgZ4CMn5uwEsbSQqfKnEaGyAKwruuoYi2RBDL7 NUnvIv6Isu5uijMEuuNB0OTdfgay3UEf0A8ZerKbGF2vgZxmwXaAK5y4; Authentication-Results: sj-dkim-5.cisco.com; header.From=rrs@cisco.com; dkim=pass ( sig from cisco.com verified; ); Cc: freebsd-net@freebsd.org Subject: Re: Problem with uipc_mbuf.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: Wed, 20 Sep 2006 11:03:37 -0000 Andre Oppermann wrote: > Maxim Konovalov wrote: > >> On Tue, 29 Aug 2006, 17:15+0200, Andre Oppermann wrote: >> >>> John-Mark Gurney wrote: >>> >>>> Randall Stewart wrote this message on Mon, Aug 28, 2006 at 17:04 -0400: >>>> >>>>> atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { >>>> >>>> ^ >>>> >>>> This should be 1 not 0.. as apparently fetchadd_int returns the >>>> old value (at least that's what atomic(9) says), which means that >>>> if we ever race on this comparision, we won't free though we >>>> should of... >>>> >>>> if we look at refcount.h, it does: >>>> return (atomic_fetchadd_int(count, -1) == 1); >>>> >>>> which release a reference and apparently returns true if it needs to >>>> be free'd... >>>> >>>> Though the wierd part is that andre, "fixed" it to be 0 in 1.157: >>>> Fix a logic error introduced with mandatory mbuf cluster >>>> refcounting and freeing of mbufs+clusters back to the packet zone. >>> >>> Honestly I'm a bit confused myself now and have to dig up things from >>> when I did the change. However I'm certain there was a problem and the >>> commit fixed it in some way (not necessarily the correct way). Before >>> the 'fix' there were some larger leaks going on. >> >> >> So what's the conclusion? Perhaps it's worth to add an XXX comment in >> meantime. > > > Please give me until Thursday to resolve this issue. > Andre: It is long past Thursday.... any status on this? I have not seen a commit from you on this... When I commit the SCTP code (some day soon) then we will have an mbuf leak unless we change the 0 to a 1.... R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 815-342-5222 (cell) From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 11:54: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 7C29E16A412; Wed, 20 Sep 2006 11:54:01 +0000 (UTC) (envelope-from dcwkszpevbmzh@wp.pl) Received: from 17.19.185.60.broad.qz.zj.dynamic.cndata.com (17.19.185.60.broad.qz.zj.dynamic.cndata.com [60.185.19.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DD5B43D97; Wed, 20 Sep 2006 11:53:41 +0000 (GMT) (envelope-from dcwkszpevbmzh@wp.pl) Received: from dns8.kataweb.it ([249.187.3.108]) by 60.185.19.17 with Microsoft SMTPSVC(5.0.2195.6824); Wed, 20 Sep 2006 17:25:15 +0400 Message-ID: X-Mailer: dietz headstrong Date: Wed, 20 Sep 2006 11:32:15 -0200 From: "Keri" To: freebsd-net@freebsd.org Organization: dietz headstrong Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1251; boundary="=====6907871694092=_" Subject: =?iso-8859-1?q?=CF=CE_=CF=CE=C2=CE=C4=D3_=C3=C0=D1=D2=D0=CE=CB?= =?iso-8859-1?q?=C5=C9?= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Keri List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 11:54:02 -0000 ÏÐÅÄËÀÃÀÅÌ ÎÐÃÀÍÈÇÀÖÈÞ ÃÀÑÒÐÎËÅÉ: Ãðóïïà "Ðåâîëüâåðñ" - îò 1 000$ Íàòàëè - îò 1 500$ Íàòàëüÿ Øòóðì - îò 1 500$ "Ôàáðèêà çâåçä" - îò 1 500$ Ïðîõîð Øàëÿïèí - îò 3 000$ Þëèàí - îò 3 000$ Âàëåíòèíà Òîëêóíîâà - îò 3 000$ Íàäåæäà Øàâðèíà - îò 3 000$ Ãðóïïà "Ëèöåé" - îò 4 000$ Òàòüÿíà Áóëàíîâà - îò 5 000$ Ãðóïïà "Hi - Fi" - îò 5 000$ Ãðóïïà "Ñëèâêè" - îò 6 000$ Ãðóïïà "Íå ïàðà" -îò 6 000$ Àíàñòàñèÿ Ñòîöêàÿ - îò 7 000$ Íàäåæäà Áàáêèíà - îò 8 000$ Ôèëèïï Êèðêîðîâ - îò 40 000$ ÐÀÁÎÒÀÅÌ ÍÀ ÐÛÍÊÅ 8 ËÅÒ! Òåë.:(495)792 77 31 (Áåç âûõîäíûõ!) From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 12:05:53 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 BF05616A4A7; Wed, 20 Sep 2006 12:05:53 +0000 (UTC) (envelope-from folllv@freudich.ch) Received: from ppp83-237-126-10.pppoe.mtu-net.ru (ppp83-237-126-10.pppoe.mtu-net.ru [83.237.126.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 061F043D73; Wed, 20 Sep 2006 12:05:40 +0000 (GMT) (envelope-from folllv@freudich.ch) Received: from [83.237.126.10] by n69.mail.aml.bradpittfan.com with NNFMP; Wed, 20 Sep 2006 07:05:35 -0600 Received: from [66.218.80.619] by a1.mail.kqi.bradpittfan.com with NNFMP; Wed, 20 Sep 2006 07:05:35 -0600 Date: Wed, 20 Sep 2006 07:05:35 -0600 Received: from [127.0.0.1] by mmapi3.mail.dth.bradpittfan.com with NNFMP; Wed, 20 Sep 2006 07:05:35 -0600 Domainkey-Signature: a=bbp-gjv1; q=dns; c=ouuis; s=s5859; d=z2c.net; b=in7PlxTzxLq8PAX3wgkUbgZ5uL0Da45q4nIjKfXiQCXFKSRhkl/hthOYwumRUlPpRIC1iASyhuJn52VaGpNtVTK0kIdWlm9ttlukHwmeBRa25FwVBVz4jC0E4+tXxRBj5ZYk2jpgsWYMqSUQbT7H0rkN= From: "Fred Addison" To: ume@freebsd.org Content-Class: urn:content-classes:message X-BPS1: 68910 Errors-To: folllv@freudich.ch Content-Type: text/plain Mime-Version: 1.0 Message-Id: <20060920120540.061F043D73@mx1.FreeBSD.org> Cc: freebsd-config@freebsd.org, freebsd-net@freebsd.org, freebsd-rave@freebsd.org, java-port@freebsd.org, nyan@freebsd.org, mb@freebsd.org Subject: baldybowl amusement X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: folllv@freudich.ch List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 12:05:53 -0000 Perfect Gift for your spouse and family - Handbags and Purses - Rolex and Luxury Watches - Tiffany and Jewellery You Name It, We have It all at 9O% Price Reduction C lick below... http://051.universalfull.com complete comb http://051.universalfull.com/rm/ From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 12:23: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 1D99C16A416 for ; Wed, 20 Sep 2006 12:23:16 +0000 (UTC) (envelope-from chuckwelv@retirementplanners.com) Received: from dslb-082-083-064-226.pools.arcor-ip.net (dslb-082-083-064-226.pools.arcor-ip.net [82.83.64.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 0D96343D62 for ; Wed, 20 Sep 2006 12:23:11 +0000 (GMT) (envelope-from chuckwelv@retirementplanners.com) Received: from mail.retirementplanners.com by dslb-082-083-064-226.pools.arcor-ip.net (Postfix) with ESMTP id 54111F4EC2 for ; Thu, 21 Sep 2006 03:28:07 -0400 Received: from zmcqtzzpanup (HELO pgxgwaoenftnc) ([177.203.189.87]) by mail.retirementplanners.com with ESMTP for ; Thu, 21 Sep 2006 03:28:07 -0400 From: "Hector Barnes" Message-ID: <7912256069.5106868433@retirementplanners.com> Date: Thu, 21 Sep 2006 03:28:07 -0400 To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Russsian congenial Slut here doing top-quality . X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hector Barnes List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 12:23:16 -0000 graceful Eighteens suckking oldman cock! http://ugadnascertbe.com From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 13:24:31 2006 Return-Path: X-Original-To: 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 F0B2616A492 for ; Wed, 20 Sep 2006 13:24:31 +0000 (UTC) (envelope-from litoeg@bacs-net.hu) Received: from fibhost-158-26.fibernet.bacs-net.hu (fibhost-158-26.fibernet.bacs-net.hu [85.66.158.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AB4D43D53 for ; Wed, 20 Sep 2006 13:24:24 +0000 (GMT) (envelope-from litoeg@bacs-net.hu) Message-ID: <001101c6dcb8$134e0050$1a9e4255@home> From: "to" To: net@freebsd.org Date: Wed, 20 Sep 2006 15:24:18 -0200 MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_000D_01C6DCC8.D6D6D050" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: new group About Searched 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, 20 Sep 2006 13:24:32 -0000 ------=_NextPart_000_000D_01C6DCC8.D6D6D050 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Create new group About Searched all groups Your search did not match any = Make sure words are spelled Try different keywords. general fewer your = on can try Answers for expert help with search. Get the latest messages Sign in Web Images VideoNew News Maps more raquo Advanced Search = Members: users: Join Alerts Create new group About Searched all groups Help Sign in Web Images VideoNew News Maps more raquo Advanced Search = Members: users: Join Alerts Create new group About Searched all groups = Your search did not match any Make sure words are spelled Try different = keywords. general fewer your on Images VideoNew News Maps more raquo Advanced Search Members: users: = Join Alerts Create new group About Searched all groups Your search did = not match any Make sure words are spelled Try different keywords. = general fewer your on can try Answers for expert help with search. Get = the latest messages emailed to Alerts. Terms of Service Privacy oogle Groups Home Help Sign in Web Images VideoNew News Maps more raquo = Advanced Search Members: users: Join Alerts Create new group About = Searched all groups Your search did not match any Make sure words are = spelled Try different keywords. general fewer your on can try Answers = for expert help with search. Get the latest messages emailed to Alerts. = Terms of Service Privacy Policy Images VideoNew News Maps more raquo Advanced Search Members: users: = Join Alerts Create new group About all groups Your search did not match any Make sure words are spelled Try = different keywords. general fewer your on can try Answers for expert = help with search. ------=_NextPart_000_000D_01C6DCC8.D6D6D050-- From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 13:36:25 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BF3716A733 for ; Wed, 20 Sep 2006 13:36:25 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5159843DB8 for ; Wed, 20 Sep 2006 13:34:56 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (bmtuhk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8KDYdbK051834; Wed, 20 Sep 2006 15:34:45 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8KDYbYd051833; Wed, 20 Sep 2006 15:34:37 +0200 (CEST) (envelope-from olli) Date: Wed, 20 Sep 2006 15:34:37 +0200 (CEST) Message-Id: <200609201334.k8KDYbYd051833@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG, steph@gabswave.net In-Reply-To: <00ee01c6d5a3$ed86ae50$1800060a@STEPHANFCN56VN> X-Newsgroups: list.freebsd-net User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 20 Sep 2006 15:34:45 +0200 (CEST) Cc: Subject: Re: Network Card problems in FreeBSD 4.9 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG, steph@gabswave.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 13:36:25 -0000 Hi, Nobody has answered to this so far, so I give it a try. First of all, FreeBSD 4.9 is pretty old. It's possible that it doesn't support your NICs (network interface cards) properly. At the very least, you should update to 4-stable (RELENG_4). But the official support for the FreeBSD 4 series ends at the end of January 2007, which means that you won't get security patches anymore. Therefore I recommend that you update to FreeBSD 6. The latest release is 6.1, but 6.2 is currently in the works and is scheduled to be released in about 6 weeks. Steph wrote: > I've recompiled my kernel since I needed to add a new Driver for some > bandwidth management software I'm running and for some reason when I > reboot the box with the new kernel it doesn't show my Network Interfaces > when doing an ifconfig -a. > > The one device is a Dual Intel Pro/1000 Adaptor and the other is a Dual > Broadcom I think. I've compiled the drivers for these devices directly > into the kernel without any errors. They do show up when doing a pciconf > -lv. I'm new to FreeBSD so the chances that I've screwed something up > somewhere is quite good :-) Is there anything else I should be looking > out for? If everything else fails, you can simply try loading the various NIC drivers (kernel modules), one after another, and watch dmesg (console output) for any messages. If one of the drivers attaches, then you know which driver you need. :-) On FreeBSD 4.x, the kernel modules are located in /modules, and on FreeBSD 5.x/6.x they're in /boot/kernel. The NIC drivers alls start with "if_", so the following command will list all of them: # ls /modules/if_* # FreeBSD 4.x # ls /boot/kernel/if_* # FreeBSD 5.x/6.x To load a module, use this command (as root, of course): # kldload if_bge That will load the "bge" driver (for Broadcom gigabit NICs). You can remove unneeded modules with kldunload, and list all currently loaded modules with kldstat. Please refer to their manual pages for details. Note that every NIC driver has a manual page, which lists all chips that are supported. For example, look at the bge manual page. Another possibility is to compile a new kernel which has all of the NIC drivers statically included. Then reboot and check which of the drivers attached to your NICs. Then remove all the others from their kernel (or just keep them, unless you're concerned about wasting some RAM). > none3@pci2:1:0: class=0x020000 card=0x00291374 chip=0x00291374 > none4@pci2:1:1: class=0x020000 card=0x00291374 chip=0x00291374 That doesn't look like an intel adaptor. You can lookup the chip ID here: http://pci-ids.ucw.cz/iii/?i=1374 It lists the device as "Silicom Dual port Copper Giga Ethernet 546GB Bypass Server Adapter". To be honest, I have never heard of such a thing before, and I think it is not supported by FreeBSD. (Someone please correct me if I'm wrong.) > none5@pci4:0:0: class=0x020000 card=0x02c615d9 chip=0x165914e4 > none6@pci5:0:0: class=0x020000 card=0x02c615d9 chip=0x165914e4 That's the "NetXtreme BCM5721 Gigabit Ethernet PCI Express". The last four characters of the "chip" ID are the vendor code (in this case, 14e4 is Broadcom) and the preceding four characters are the model code (here: 1659). See this page: http://pci-ids.ucw.cz/iii/?i=14e4 In FreeBSD 6, the bge(4) manual page says that the BCM5721 is supported by this driver. However, I'm not sure that 4.9 supports it, because it's very old. You probably must update to a more recent version of FreeBSD. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot)." -- Terry Lambert, FreeBSD-hackers mailing list. From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 18:31: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 BBA7C16A40F for ; Wed, 20 Sep 2006 18:31:31 +0000 (UTC) (envelope-from rsf@ns.live555.com) Received: from ns.live555.com (ns.live555.com [66.80.62.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5763B43D6A for ; Wed, 20 Sep 2006 18:31:31 +0000 (GMT) (envelope-from rsf@ns.live555.com) Received: from ns.live555.com (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.13.6/8.13.6) with ESMTP id k8KIVUWf000840 for ; Wed, 20 Sep 2006 11:31:30 -0700 (PDT) (envelope-from rsf@ns.live555.com) Received: (from rsf@localhost) by ns.live555.com (8.13.6/8.13.6/Submit) id k8KIVUli000839; Wed, 20 Sep 2006 11:31:30 -0700 (PDT) (envelope-from rsf) Mime-Version: 1.0 Message-Id: Date: Wed, 20 Sep 2006 11:30:11 -0700 To: freebsd-net@freebsd.org From: Ross Finlayson Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: Spam on this mailing list 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, 20 Sep 2006 18:31:31 -0000 Folks, I think it's time to reconfigure this mailing list so that only subscribers can post to it. (Frankly, I was suprised that this isn't already done; most mailing lists these day so this.) Ross. From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 18:43:54 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54DC316A40F for ; Wed, 20 Sep 2006 18:43:54 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5820C43D5A for ; Wed, 20 Sep 2006 18:43:45 +0000 (GMT) (envelope-from rrs@cisco.com) Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-5.cisco.com with ESMTP; 20 Sep 2006 11:43:46 -0700 X-IronPort-AV: i="4.09,192,1157353200"; d="scan'208"; a="323361412:sNHT32276600" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k8KIhjuD021950 for ; Wed, 20 Sep 2006 11:43:45 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k8KIhjML004982 for ; Wed, 20 Sep 2006 11:43:45 -0700 (PDT) Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Sep 2006 11:43:44 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Sep 2006 11:43:44 -0700 Message-ID: <451153A5.3000309@cisco.com> Date: Wed, 20 Sep 2006 10:43:49 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Sep 2006 18:43:44.0774 (UTC) FILETIME=[B36FCA60:01C6DCE4] DKIM-Signature: a=rsa-sha1; q=dns; l=808; t=1158777825; x=1159641825; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:Randall=20Stewart=20 |Subject:Updated=20SCTP=20patch/tar; X=v=3Dcisco.com=3B=20h=3DCUQTTvnokJK7CXDg1je+nQpM1PU=3D; b=q7zTPuI3n52qEc07bbcWyqcr2Xcwebt+T0ocgzojR8Pfurq6laMeKL2gkQPc0gAtxTXVlDAQ VTFGHsF6PO/sVfdMPowbKzNw6dn9BLYOBnSa3eAuxueVafW5sERs4mVH; Authentication-Results: sj-dkim-6.cisco.com; header.From=rrs@cisco.com; dkim=pass ( sig from cisco.com verified; ); Subject: Updated SCTP patch/tar 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, 20 Sep 2006 18:43:54 -0000 Hello all: Well, life goes on.. I have once again put up on the sctp.org web site an updated patch for 7.0 and a new tarball for 6.0/6.1 for SCTP. You can find these at: http://www.sctp.org/download.html (or go to www.sctp.org and pick the download tab)... For those on 7.0 please pick the 9/20 patch. For those on 6.0 or 6.1 use the tarball-5 dated 9/20... Note this is getting pretty close to the code we will commit to FreeBSD soon (probably October).. the patch also holds the update for uipc_mbuf.c that fixes the contention memory leak bug.. This will be committed shortly to HEAD.. but for those wanting the patch... this will save you the trouble :-D Happy SCTPing R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 815-342-5222 (cell) From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 18:53: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 01F5516A407 for ; Wed, 20 Sep 2006 18:53:33 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED71943D76 for ; Wed, 20 Sep 2006 18:53:21 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20060920185315m9200do5kce>; Wed, 20 Sep 2006 18:53:15 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.6/8.13.6) with ESMTP id k8KIr7vQ066750; Wed, 20 Sep 2006 13:53:07 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.6/8.13.6/Submit) id k8KIr6FV066747; Wed, 20 Sep 2006 13:53:06 -0500 (CDT) (envelope-from brooks) Date: Wed, 20 Sep 2006 13:53:06 -0500 From: Brooks Davis To: Ross Finlayson Message-ID: <20060920185306.GA66712@lor.one-eyed-alien.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Cc: freebsd-net@freebsd.org Subject: Re: Spam on this mailing list 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, 20 Sep 2006 18:53:33 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 20, 2006 at 11:30:11AM -0700, Ross Finlayson wrote: > Folks, I think it's time to reconfigure this mailing list so that=20 > only subscribers can post to it. (Frankly, I was suprised that this=20 > isn't already done; most mailing lists these day so this.) The spam filter was temporarily broken and has been fixed. -- Brooks --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFEY4RXY6L6fI4GtQRAoBQAKDFV2bwAO38lgmxpd8WeXidz7mwJwCeKOU6 J2UIrk2SNNp8+7SOO2aahVw= =ONJW -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-net@FreeBSD.ORG Wed Sep 20 21:59: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 BA05F16A417 for ; Wed, 20 Sep 2006 21:59:16 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1C4243D46 for ; Wed, 20 Sep 2006 21:59:14 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 29349 invoked from network); 20 Sep 2006 22:02:05 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 20 Sep 2006 22:02:05 -0000 Message-ID: <4511B9B1.2000903@freebsd.org> Date: Wed, 20 Sep 2006 23:59:13 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, tegge@freebsd.org, gallatin@cs.duke.edu Subject: Much improved sendfile(2) kernel implementation 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, 20 Sep 2006 21:59:16 -0000 The recent addition of TSO (TCP Segmentation Offload) has highlighted some shortcommings in our sendfile(2) kernel implementation. The current code simply loops over the file, turns each 4K page into an mbuf and sends it off. This has the effect that TSO can only generate 2 packets per send instead of up to 44 at its maximum of 64K. I have rewritten kern_sendfile() to work in two loops, the inner which turns as many pages into mbufs as it can up to the free send socket buffer space. The outer loop then drops the whole mbuf chain into the send socket buffer, calls tcp_output() on it and then waits until 50% of the socket buffer are free again to repeat the cycle. This way tcp_output() gets the full amount of data to work with and can issue up to 64K sends for TSO to chop up in the network adapter without using any CPU cycles. Thus it gets very efficient especially with the readahead the VM and I/O system do. Looking at the benchmarks we see some very nice improvements (95% confidence): 45% less cpu (or 1.81 times better) with new sendfile vs. old sendfile (non-TSO) 83% less cpu (or 5.7 times better) with new sendfile vs. old sendfile (TSO) The sender is an AMD Opteron 852 (2.6GHz) with em(4) PCI-X-133 interface and the receiver is a DELL Poweredge SC1425 P-IV Xeon 3.2GHz with em(4) LOM connected back to back at 1000Base-TX full duplex. The patch is available here: http://people.freebsd.org/~andre/sendfile-20060920.diff Any testing and heavy (code) beating and reviews welcome. -- Andre Here are the raw numbers (netperf at 95% confidence, +-2.5% error margin, the cpu load reported by netperf is different from the one reported by time(1), all performance references are made based on time(1) output, netperf 2.4.2 used): a) is old sendfile(2) kernel implementation b) is new sendfile(2) kernel implementation 1) time ./netperf -H192.168.2.2,4 -tTCP_STREAM -C -c -F 6.2-BETA1-i386-disc1.iso -- -s32K -S32K [non-TSO] 2) time ./netperf -H192.168.2.2,4 -tTCP_STREAM -C -c -F 6.2-BETA1-i386-disc1.iso -- -s32K -S32K [TSO] 3) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s32K -S32K [non-TSO] 4) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s32K -S32K [TSO] 5) time ./netperf -H192.168.2.2,4 -tTCP_STREAM -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K [non-TSO] 6) time ./netperf -H192.168.2.2,4 -tTCP_STREAM -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K [TSO] 7) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K [non-TSO] 8) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K [TSO] 9) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K -m1M [non-TSO] 10) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K -m1M [TSO] 11) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K -m2M [non-TSO] 12) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K -m2M [TSO] 13) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K -m5M [non-TSO] 14) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s64K -S64K -m5M [TSO] 15) time ./netperf -H192.168.2.2,4 -tTCP_STREAM -C -c -F 6.2-BETA1-i386-disc1.iso -- -s128K -S128K [non-TSO] 16) time ./netperf -H192.168.2.2,4 -tTCP_STREAM -C -c -F 6.2-BETA1-i386-disc1.iso -- -s128K -S128K [TSO] 17) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s128K -S128K [non-TSO] 18) time ./netperf -H192.168.2.2,4 -tTCP_SENDFILE -C -c -F 6.2-BETA1-i386-disc1.iso -- -s128K -S128K [TSO] Recv Send Send Utilization Service Demand Socket Socket Message Elapsed Send Recv Send Recv Size Size Size Time Throughput local remote local remote bytes bytes bytes secs. 10^6bits/s % C % C us/KB us/KB 1) 32768 32768 32768 10.00 921.16 28.27 31.88 2.514 2.835 0.000u 1.703s 0:10.00 17.0% 94+5091k 0+0io 0pf+0w 2) 32768 32768 32768 10.00 897.91 23.83 38.65 2.175 3.526 0.000u 1.310s 0:10.02 13.0% 91+4925k 0+0io 0pf+0w 3) 32768 32768 32768 10.00 767.31 20.98 29.92 2.240 3.195 0.013u 0.969s 0:10.00 9.7% 109+5855k 0+0io 1pf+0w 4a) 32768 32768 32768 10.00 911.66 15.71 33.61 1.412 3.020 0.000u 0.651s 0:10.00 6.5% 93+4993k 0+0io 0pf+0w 4b) 32768 32768 32768 10.00 759.08 11.13 30.70 1.201 3.313 0.007u 0.266s 0:10.00 2.6% 108+5796k 0+0io 0pf+0w ---- 5) 65536 65536 65536 10.00 941.59 29.17 31.73 2.538 2.760 0.000u 1.759s 0:10.01 17.4% 93+5012k 3+0io 0pf+0w 6) 65536 65536 65536 10.00 921.97 26.47 38.80 2.352 3.447 0.000u 1.401s 0:10.00 14.0% 97+5216k 0+0io 0pf+0w 7a) 65536 65536 65536 10.00 941.59 23.08 33.23 2.008 2.891 0.000u 1.178s 0:10.00 11.7% 92+4986k 0+0io 0pf+0w 7b) 65536 65536 65536 10.00 940.76 23.68 31.43 2.062 2.737 0.000u 1.202s 0:10.00 12.0% 90+4862k 0+0io 0pf+0w 8a) 65536 65536 65536 10.00 936.75 16.62 33.08 1.453 2.893 0.000u 0.611s 0:10.00 6.1% 99+5320k 0+0io 0pf+0w 8b) 65536 65536 65536 10.00 938.99 12.11 33.08 1.056 2.886 0.006u 0.245s 0:10.00 2.4% 117+6279k 0+0io 0pf+0w ---- 9a) 65536 65536 1048576 10.00 941.59 23.61 32.53 2.054 2.830 0.000u 1.147s 0:10.00 11.4% 97+5253k 0+0io 0pf+0w 9b) 65536 65536 1048576 10.00 940.43 20.68 32.63 1.801 2.843 0.000u 1.149s 0:10.00 11.4% 93+5016k 0+0io 0pf+0w 10a) 65536 65536 1048576 10.00 931.96 16.47 35.31 1.447 3.104 0.000u 0.631s 0:10.00 6.3% 91+4906k 23+0io 0pf+0w 10b) 65536 65536 1048576 10.00 929.90 11.58 34.94 1.020 3.078 0.000u 0.201s 0:10.00 2.0% 126+6762k 0+0io 0pf+0w 11a) 65536 65536 2097152 10.00 941.59 23.29 32.26 2.026 2.806 0.000u 1.153s 0:10.00 11.5% 95+5107k 0+0io 0pf+0w 11b) 65536 65536 2097152 10.00 940.38 21.88 31.86 1.906 2.775 0.000u 1.157s 0:10.00 11.5% 94+5073k 0+0io 0pf+0w 12a) 65536 65536 2097152 10.00 936.75 16.92 33.31 1.479 2.913 0.000u 0.651s 0:10.00 6.5% 100+5409k 0+0io 0pf+0w 12b) 65536 65536 2097152 10.00 935.48 10.97 32.03 0.961 2.805 0.000u 0.201s 0:10.00 2.0% 97+5216k 20+0io 0pf+0w 13a) 65536 65536 5242880 10.00 941.58 23.68 31.13 2.061 2.708 0.000u 1.168s 0:10.00 11.6% 101+5462k 0+0io 0pf+0w 13b) 65536 65536 5242880 10.00 940.22 20.68 33.46 1.802 2.915 0.000u 1.163s 0:10.00 11.6% 91+4896k 0+0io 0pf+0w 14a) 65536 65536 5242880 10.00 923.40 17.44 33.66 1.548 2.986 0.000u 0.656s 0:10.00 6.5% 103+5528k 84+0io 0pf+0w 14b) 65536 65536 5242880 10.00 928.56 10.90 33.23 0.962 2.932 0.000u 0.206s 0:10.00 2.0% 115+6182k 64+0io 0pf+0w ---- 15) 131072 131072 131072 10.00 941.62 33.98 31.95 2.957 2.780 0.000u 2.098s 0:10.00 20.9% 95+5102k 1+0io 0pf+0w 16) 131072 131072 131072 10.00 922.41 28.42 39.25 2.524 3.486 0.007u 1.646s 0:10.00 16.4% 91+4924k 0+0io 0pf+0w 17) 131072 131072 131072 10.00 941.61 21.88 32.68 1.904 2.843 0.000u 1.204s 0:10.00 12.0% 96+5152k 0+0io 0pf+0w 18) [the em(4) interface wedged in TSO] From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 07:59: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 8796916A415; Thu, 21 Sep 2006 07:59:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail29.syd.optusnet.com.au (mail29.syd.optusnet.com.au [211.29.132.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D3C443D5A; Thu, 21 Sep 2006 07:59:06 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail29.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k8L7x30a014406 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Sep 2006 17:59:04 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id k8L7x3ob001188; Thu, 21 Sep 2006 17:59:03 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id k8L7x3fu001187; Thu, 21 Sep 2006 17:59:03 +1000 (EST) (envelope-from peter) Date: Thu, 21 Sep 2006 17:59:03 +1000 From: Peter Jeremy To: Andre Oppermann Message-ID: <20060921075903.GD960@turion.vk2pj.dyndns.org> References: <4511B9B1.2000903@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pk6IbRAofICFmK5e" Content-Disposition: inline In-Reply-To: <4511B9B1.2000903@freebsd.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 07:59:10 -0000 --Pk6IbRAofICFmK5e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 2006-Sep-20 23:59:13 +0200, Andre Oppermann wrote: >I have rewritten kern_sendfile() to work in two loops, the inner which tur= ns >as many pages into mbufs as it can up to the free send socket buffer space. The 64K blocks sounds good but how does this interact with TCP slow start? Is there the possibility that a couple (for some reasonably large value of 'couple') of TCP connections slowly accepting a file could eat all the mbuf space? --=20 Peter Jeremy --Pk6IbRAofICFmK5e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFEkZH/opHv/APuIcRAhDiAJ9him08wniFTAjcmVqdhFvVpAN5GgCfYtE5 +6i5j8cghQVlzSOqu+LjT0I= =TCn6 -----END PGP SIGNATURE----- --Pk6IbRAofICFmK5e-- From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 10:30:32 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4449716A518 for ; Thu, 21 Sep 2006 10:30:32 +0000 (UTC) (envelope-from cjeker@diehard.n-r-g.com) Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7C8743D49 for ; Thu, 21 Sep 2006 10:30:31 +0000 (GMT) (envelope-from cjeker@diehard.n-r-g.com) Received: (qmail 21584 invoked by uid 1001); 21 Sep 2006 10:30:30 -0000 Date: Thu, 21 Sep 2006 12:30:30 +0200 From: Claudio Jeker To: freebsd-net@freebsd.org Message-ID: <20060921103030.GA30890@diehard.n-r-g.com> Mail-Followup-To: Claudio Jeker , freebsd-net@freebsd.org References: <4511B9B1.2000903@freebsd.org> <20060921075903.GD960@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060921075903.GD960@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.5.12-2006-07-14 Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 10:30:32 -0000 On Thu, Sep 21, 2006 at 05:59:03PM +1000, Peter Jeremy wrote: > On Wed, 2006-Sep-20 23:59:13 +0200, Andre Oppermann wrote: > >I have rewritten kern_sendfile() to work in two loops, the inner which turns > >as many pages into mbufs as it can up to the free send socket buffer space. > > The 64K blocks sounds good but how does this interact with TCP slow > start? Is there the possibility that a couple (for some reasonably > large value of 'couple') of TCP connections slowly accepting a file > could eat all the mbuf space? > You always have this issue no matter if you use sendfile or not. This is why the socket buffers are limited and why sometimes having large sendbuffers is bad -- especially on busy servers. -- :wq Claudio From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 10:32:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFC8816A47B for ; Thu, 21 Sep 2006 10:32:58 +0000 (UTC) (envelope-from slawek.zak@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id B497343D55 for ; Thu, 21 Sep 2006 10:32:57 +0000 (GMT) (envelope-from slawek.zak@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so101660uge for ; Thu, 21 Sep 2006 03:32:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Bw+FDkXGvHIKET16TnoGOBd8THlKkaFk4aLRUvbb9oy9m7XeQr5IDP0bmYWAliQzM9RgPJvLphZs05MwJ6SkNu4mXmmIcF8BikPEjRNLjKgcEUeyyR6ew0JO7CiClj4SXr3qMl7s/H0V8NOlBRpQCjihPmk7ZJGzz7sPoTKL47s= Received: by 10.66.244.10 with SMTP id r10mr9085124ugh; Thu, 21 Sep 2006 03:32:56 -0700 (PDT) Received: by 10.66.234.18 with HTTP; Thu, 21 Sep 2006 03:32:56 -0700 (PDT) Message-ID: <787bbe1c0609210332p759e22dah8601313436754458@mail.gmail.com> Date: Thu, 21 Sep 2006 12:32:56 +0200 From: "Slawek Zak" To: "Gleb Smirnoff" , "Slawek Zak" , freebsd-net@freebsd.org In-Reply-To: <20060915141710.GR27667@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <787bbe1c0609130609l33fb29dawc465b7bcfb2f430e@mail.gmail.com> <20060915141710.GR27667@FreeBSD.org> Cc: Subject: Re: Rapid link state changes on bge(4) interface 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, 21 Sep 2006 10:32:59 -0000 T24gOS8xNS8wNiwgR2xlYiBTbWlybm9mZiA8Z2xlYml1c0BmcmVlYnNkLm9yZz4gd3JvdGU6Cj4g T24gV2VkLCBTZXAgMTMsIDIwMDYgYXQgMDM6MDk6NTZQTSArMDIwMCwgU2xhd2VrIFphayB3cm90 ZToKPiBTPiBJJ20gdGVzdGluZyBuZXR3b3JrIGZhaWxvdmVyIG9uIElCTSBCbGFkZUNlbnRlciBy dW5uaW5nIEZyZWVCU0QgNi4xCj4gUz4gU1RBQkxFIGZvciBTZXAgNnRoLgo+IFM+Cj4gUz4gSSBz dXNwZWN0IGEgcHJvYmxlbSB3aXRoIGxpbmsgc3RhdGUgY2hhbmdlIGRldGVjdGlvbiBpbiBiZ2Ug Y29kZS4gV2hlbgo+IFM+IEkgZGlzYWJsZSBpbnRlcm5hbCBwb3J0IG9uIGNoYXNzaXMgYnVpbHQt aW4gZXRoZXJuZXQgc3dpdGNoLCBrZXJuZWwKPiBTPiBmbG9vZHMgc3lzbG9nIHdpdGggbWVzc2Fn ZXMgYWJvdXQgbGluayBzdGF0ZSBjaGFuZ2VzIGFuZCBjb2FsZXNjaW5nCj4gUz4gdGhlbS4gTG9n IHNuaXBwZXQgZm9sbG93czoKPiBTPgo+IFM+IFNlcCAxMyAxNDo1ODoyOCB3My02IGtlcm5lbDog YmdlMTogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIERPV04KPiBTPiBTZXAgMTMgMTQ6NTg6MjggdzMt NiBrZXJuZWw6IGJnZTE6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBVUAo+IFM+IFNlcCAxMyAxNDo1 ODoyOSB3My02IGtlcm5lbDogYmdlMTogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIERPV04KPiBTPiBT ZXAgMTMgMTQ6NTg6MjkgdzMtNiBrZXJuZWw6IGJnZTE6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBV UAo+IFM+IFNlcCAxMyAxNDo1ODoyOSB3My02IGtlcm5lbDogYmdlMTogbGluayBzdGF0ZSBjaGFu Z2VkIHRvIERPV04KPiBTPiBTZXAgMTMgMTQ6NTg6MjkgdzMtNiBrZXJuZWw6IGJnZTE6IDQgbGlu ayBzdGF0ZXMgY29hbGVzY2VkCj4gUz4gU2VwIDEzIDE0OjU4OjI5IHczLTYga2VybmVsOiBiZ2Ux OiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gRE9XTgo+IFM+IFNlcCAxMyAxNDo1ODoyOSB3My02IGtl cm5lbDogYmdlMTogMTEgbGluayBzdGF0ZXMgY29hbGVzY2VkCj4gUz4gU2VwIDEzIDE0OjU4OjI5 IHczLTYga2VybmVsOiBiZ2UxOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gVVAKPiBTPiBTZXAgMTMg MTQ6NTg6MzAgdzMtNiBrZXJuZWw6IGJnZTE6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBET1dOCj4g Uz4gU2VwIDEzIDE0OjU4OjMwIHczLTYga2VybmVsOiBiZ2UxOiAzIGxpbmsgc3RhdGVzIGNvYWxl c2NlZAo+IFM+IFNlcCAxMyAxNDo1ODozMCB3My02IGtlcm5lbDogYmdlMTogbGluayBzdGF0ZSBj aGFuZ2VkIHRvIFVQCj4gUz4gU2VwIDEzIDE0OjU4OjMwIHczLTYga2VybmVsOiBiZ2UxOiA3IGxp bmsgc3RhdGVzIGNvYWxlc2NlZAo+IFM+IFNlcCAxMyAxNDo1ODozMCB3My02IGtlcm5lbDogYmdl MTogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIERPV04KPiBTPiBTZXAgMTMgMTQ6NTg6MzAgdzMtNiBr ZXJuZWw6IGJnZTE6IDQgbGluayBzdGF0ZXMgY29hbGVzY2VkCj4gUz4gU2VwIDEzIDE0OjU4OjMw IHczLTYga2VybmVsOiBiZ2UxOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gRE9XTgo+IFM+IFNlcCAx MyAxNDo1ODozMCB3My02IGtlcm5lbDogYmdlMTogMiBsaW5rIHN0YXRlcyBjb2FsZXNjZWQKPiBT Pgo+IFM+IEFzIHlvdSBjYW4gc2VlLCBtZXNzYWdlcyBhcmUgZ2VuZXJhdGVkIGluIHJhcGlkIHN1 Y2Nlc3Npb24gYW5kCj4gUz4gdGhlcmVmb3JlIGFueSBwcm9iaW5nIG9mIGxpbmsgc3RhdGUgY2hh bmdlIGJ5IG5nX29uZTJtYW55IGZvcgo+IFM+IGludGVyZmFjZSBmYWlsb3ZlciBpcyBtZWFuaW5n bGVzcy4gRXRoZXJuZXQgc3dpdGNoIGRvZXNuJ3QgcmVnaXN0ZXIKPiBTPiBhbmQgbG9nIGFueSBp bnRlcmZhY2Ugc3RhdGUgY2hhbmdlcyBhZnRlciBkaXNhYmxpbmcgdGhpcyBwb3J0LiBMUzIwCj4g Uz4gYmxhZGVzIHVzZSBjaGlwc2V0IDg4NTAuIE15IGZpcm13YXJlIGlzIDMuMzgsIGZ1bGwgY2hh bmdlbG9nLCBpZiBpdCBpcwo+IFM+IG9mIGFueSBoZWxwLCBpcyBoZXJlOgo+IFM+Cj4gUz4gaHR0 cDovL3d3dy0zMDcuaWJtLmNvbS9wYy9zdXBwb3J0L3NpdGUud3NzL2xpY2Vuc2UuZG8/ZmlsZW5h bWU9cGNfc2VydmVycy9icmNtX2Z3X25pY18xMjAyMV9hbnlvc19hbnljcHUuY2hnCj4gUz4KPiBT PiBBbnkgaWRlYXMgd2hhdCBtaWdodCBiZSB3cm9uZz8KPgo+IFBsZWFzZSB0cnkgdG8gYWRkIGh3 LmJnZS5mYWtlX2F1dG9uZWc9MSB0byAvYm9vdC9sb2FkZXIuY29uZi4gTWF5IGJlCj4gdGhpcyB3 aWxsIGhlbHAuCgpJIGRpZCBpdCwgYnV0IHN5c2N0bCBkb2Vzbid0IHNob3cgdGhlIHZhbHVlLgoK dzMtNiMgc3lzY3RsIGh3LmJnZQpzeXNjdGw6IHVua25vd24gb2lkICdody5iZ2UnCgpUaGlzIHN5 c2N0bCBzZWVtcyB0byBiZSBkZWZpbmVkIGluIGlmX2JnZS5jIHRob3VnaDoKCnN0YXRpYyBpbnQg YmdlX2Zha2VfYXV0b25lZyA9IDA7ClRVTkFCTEVfSU5UKCJody5iZ2UuZmFrZV9hdXRvbmVnIiwg JmJnZV9mYWtlX2F1dG9uZWcpOwoKL1MKLS0gClOzYXdlayCvYWsgLyBVTklYIFN5c3RlbXMgQWRt aW5pc3RyYXRvcgo= From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 11:44:44 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 CD41C16A40F; Thu, 21 Sep 2006 11:44:44 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7D4243D69; Thu, 21 Sep 2006 11:44:43 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k8LBiVpc024095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Sep 2006 15:44:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k8LBiV5U024094; Thu, 21 Sep 2006 15:44:31 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 21 Sep 2006 15:44:31 +0400 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20060921114431.GF27667@FreeBSD.org> Mail-Followup-To: Gleb Smirnoff , Andre Oppermann , freebsd-current@freebsd.org, freebsd-net@freebsd.org, alc@freebsd.org, tegge@freebsd.org, gallatin@cs.duke.edu References: <4511B9B1.2000903@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4511B9B1.2000903@freebsd.org> User-Agent: Mutt/1.5.6i Cc: alc@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-current@FreeBSD.org, tegge@FreeBSD.org, gallatin@cs.duke.edu Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 11:44:44 -0000 Andre, On Wed, Sep 20, 2006 at 11:59:13PM +0200, Andre Oppermann wrote: A> I have rewritten kern_sendfile() to work in two loops, the inner which turns A> as many pages into mbufs as it can up to the free send socket buffer space. A> The outer loop then drops the whole mbuf chain into the send socket buffer, A> calls tcp_output() on it and then waits until 50% of the socket buffer are A> free again to repeat the cycle. This way tcp_output() gets the full amount A> of data to work with and can issue up to 64K sends for TSO to chop up in the A> network adapter without using any CPU cycles. Thus it gets very efficient A> especially with the readahead the VM and I/O system do. A> A> The patch is available here: A> http://people.freebsd.org/~andre/sendfile-20060920.diff I see that mbuf allocations are done in different way depending on the SS_NBIO flag on socket. This isn't true for the current code, so your patch isn't only opmization, but is also changing the semantics of the syscall. This should be avoided in single change/commit. The non-blocking IO definition is related to the blocking on the socket buffer. It isn't related to blocking on memory, so this change is incorrect: - m_header = m_uiotombuf(hdr_uio, M_DONTWAIT, 0, 0); - if (m_header == NULL) + m = m_uiotombuf(hdr_uio, (nbio ? M_NOWAIT : M_WAITOK), + 0, 0); + if (m == NULL) { + error = nbio ? EAGAIN : ENOBUFS; There should be unconditional M_NOWAIT. Oops, the M_DONTWAIT in the current code is incorrect. It is present since rev. 1.171. If the m_uiotombuf() fails the current code returns from syscall without error! Before rev. 1.171, there wasn't m_uiotombuf(), the mbuf header was allocated below, with correct wait argument. The wait argument for m_uiotombuf() should be changed to M_WAITOK, but in a separate commit. And this one: + m0 = m_get((nbio ? M_NOWAIT : M_WAITOK), MT_DATA); + if (m0 == NULL) { + error = (nbio ? EAGAIN : ENOBUFS); + sf_buf_mext((void *)sf_buf_kva(sf), sf); + break; + } This one should be M_WAITOK always. It is M_TRYWAIT (equal to M_WAITOK) in the current code. Is there RELENG_6 version of your patch. If there is one, we can test it quite extensively. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 11:46: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 400DD16A415 for ; Thu, 21 Sep 2006 11:46:09 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E80243D6B for ; Thu, 21 Sep 2006 11:46:04 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k8LBk2SJ024117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Sep 2006 15:46:03 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k8LBk291024116; Thu, 21 Sep 2006 15:46:02 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 21 Sep 2006 15:46:02 +0400 From: Gleb Smirnoff To: Slawek Zak Message-ID: <20060921114602.GG27667@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Slawek Zak , freebsd-net@freebsd.org References: <787bbe1c0609130609l33fb29dawc465b7bcfb2f430e@mail.gmail.com> <20060915141710.GR27667@FreeBSD.org> <787bbe1c0609210332p759e22dah8601313436754458@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <787bbe1c0609210332p759e22dah8601313436754458@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: Rapid link state changes on bge(4) interface 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, 21 Sep 2006 11:46:09 -0000 On Thu, Sep 21, 2006 at 12:32:56PM +0200, Slawek Zak wrote: S> >Please try to add hw.bge.fake_autoneg=1 to /boot/loader.conf. May be S> >this will help. S> S> I did it, but sysctl doesn't show the value. S> S> w3-6# sysctl hw.bge S> sysctl: unknown oid 'hw.bge' S> S> This sysctl seems to be defined in if_bge.c though: S> S> static int bge_fake_autoneg = 0; S> TUNABLE_INT("hw.bge.fake_autoneg", &bge_fake_autoneg); Not all tunables are exposed to the sysctl tree. Did the tunable help you? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 12:26: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 58DFA16A412 for ; Thu, 21 Sep 2006 12:26:52 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29E8043D5A for ; Thu, 21 Sep 2006 12:26:50 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 38422 invoked from network); 21 Sep 2006 12:29:34 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Sep 2006 12:29:34 -0000 Message-ID: <4512850A.5000107@freebsd.org> Date: Thu, 21 Sep 2006 14:26:50 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Gleb Smirnoff , Andre Oppermann , freebsd-current@freebsd.org, freebsd-net@freebsd.org, alc@freebsd.org, tegge@freebsd.org, gallatin@cs.duke.edu References: <4511B9B1.2000903@freebsd.org> <20060921114431.GF27667@FreeBSD.org> In-Reply-To: <20060921114431.GF27667@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 12:26:52 -0000 Gleb Smirnoff wrote: > Andre, > > On Wed, Sep 20, 2006 at 11:59:13PM +0200, Andre Oppermann wrote: > A> I have rewritten kern_sendfile() to work in two loops, the inner which turns > A> as many pages into mbufs as it can up to the free send socket buffer space. > A> The outer loop then drops the whole mbuf chain into the send socket buffer, > A> calls tcp_output() on it and then waits until 50% of the socket buffer are > A> free again to repeat the cycle. This way tcp_output() gets the full amount > A> of data to work with and can issue up to 64K sends for TSO to chop up in the > A> network adapter without using any CPU cycles. Thus it gets very efficient > A> especially with the readahead the VM and I/O system do. > A> > A> The patch is available here: > A> http://people.freebsd.org/~andre/sendfile-20060920.diff > > I see that mbuf allocations are done in different way depending on the SS_NBIO > flag on socket. This isn't true for the current code, so your patch isn't > only opmization, but is also changing the semantics of the syscall. This should > be avoided in single change/commit. IMO this goes hand in hand. > The non-blocking IO definition is related to the blocking on the socket buffer. > It isn't related to blocking on memory, so this change is incorrect: > > - m_header = m_uiotombuf(hdr_uio, M_DONTWAIT, 0, 0); > - if (m_header == NULL) > + m = m_uiotombuf(hdr_uio, (nbio ? M_NOWAIT : M_WAITOK), > + 0, 0); > + if (m == NULL) { > + error = nbio ? EAGAIN : ENOBUFS; > > There should be unconditional M_NOWAIT. Oops, the M_DONTWAIT in the current > code is incorrect. It is present since rev. 1.171. If the m_uiotombuf() fails > the current code returns from syscall without error! Before rev. 1.171, there > wasn't m_uiotombuf(), the mbuf header was allocated below, with correct wait > argument. > > The wait argument for m_uiotombuf() should be changed to M_WAITOK, but in > a separate commit. > > And this one: > > + m0 = m_get((nbio ? M_NOWAIT : M_WAITOK), MT_DATA); > + if (m0 == NULL) { > + error = (nbio ? EAGAIN : ENOBUFS); > + sf_buf_mext((void *)sf_buf_kva(sf), sf); > + break; > + } > > This one should be M_WAITOK always. It is M_TRYWAIT (equal to M_WAITOK) in > the current code. The reason why I changed the mbuf allocations with SS_NBIO is the rationale of sendfile() and the performance evaluation that was done by alc@ students. sendfile() has two flags which control its blocking behavior. Non blocking socket (SS_NBIO) and SF_NODISKIO. The latter is necessary because file reads or writes are normally not considered to be blocking. The most optimal sendfile() is usage is with a single process doing accept(), parsing and then sendfile that should never ever block on anything. This way the main process then can use kqueue for all the socket stuff and it can transfer all sends that require disk I/O to a child process or thread to provide a context for the read. Meanwhile the main process is free to accept further connections and to continue serving existing connections. Having sendfile() block in mbuf allocation for the header, on sfbufs or anything else is not desirable and must be avoided. I know I'm extending the traditional definition of SS_NBIO a bit but it's fully in line with the semantics and desired operational behavior of sendfile(). The paper by alc@'s students clearly identifies this as the main property of a sendfile implementation besides its zero copy nature. > Is there RELENG_6 version of your patch. If there is one, we can test it > quite extensively. This patch does not fully apply to RELENG_6 as there are some small changes and a bit locking differences. It shouldn't be too hard to adapt it. You won't get TSO speedups though and we can't MFC TSO because it changes the ABI+API for network drivers. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 12:29: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 B526C16A407 for ; Thu, 21 Sep 2006 12:29:34 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBAA943D53 for ; Thu, 21 Sep 2006 12:29:33 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 38463 invoked from network); 21 Sep 2006 12:32:18 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Sep 2006 12:32:18 -0000 Message-ID: <451285AE.5030900@freebsd.org> Date: Thu, 21 Sep 2006 14:29:34 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Peter Jeremy References: <4511B9B1.2000903@freebsd.org> <20060921075903.GD960@turion.vk2pj.dyndns.org> In-Reply-To: <20060921075903.GD960@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 12:29:34 -0000 Peter Jeremy wrote: > On Wed, 2006-Sep-20 23:59:13 +0200, Andre Oppermann wrote: >> I have rewritten kern_sendfile() to work in two loops, the inner which turns >> as many pages into mbufs as it can up to the free send socket buffer space. > > The 64K blocks sounds good but how does this interact with TCP slow > start? Is there the possibility that a couple (for some reasonably > large value of 'couple') of TCP connections slowly accepting a file > could eat all the mbuf space? This danger is and has been always present. This normal socket behavior and happens no matter which method (write or sendfile) you use. Even the current sendfile(2) fills the socket buffer when the connection is in slow start. It just spends more CPU once the connection is going and getting throughput (and it doesn't make much use of TSO there). -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 13:59: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 E3DDD16A403; Thu, 21 Sep 2006 13:59:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 676B543D46; Thu, 21 Sep 2006 13:59:09 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F31DC46CAE; Thu, 21 Sep 2006 09:59:07 -0400 (EDT) Date: Thu, 21 Sep 2006 14:59:07 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andre Oppermann In-Reply-To: <4512850A.5000107@freebsd.org> Message-ID: <20060921145002.K37863@fledge.watson.org> References: <4511B9B1.2000903@freebsd.org> <20060921114431.GF27667@FreeBSD.org> <4512850A.5000107@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: gallatin@cs.duke.edu, freebsd-current@freebsd.org, alc@freebsd.org, freebsd-net@freebsd.org, Gleb Smirnoff , tegge@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 13:59:11 -0000 On Thu, 21 Sep 2006, Andre Oppermann wrote: >> There should be unconditional M_NOWAIT. Oops, the M_DONTWAIT in the current >> code is incorrect. It is present since rev. 1.171. If the m_uiotombuf() >> fails the current code returns from syscall without error! Before rev. >> 1.171, there wasn't m_uiotombuf(), the mbuf header was allocated below, >> with correct wait argument. >> >> The wait argument for m_uiotombuf() should be changed to M_WAITOK, but in a >> separate commit. >> This one should be M_WAITOK always. It is M_TRYWAIT (equal to M_WAITOK) in >> the current code. > > The reason why I changed the mbuf allocations with SS_NBIO is the rationale > of sendfile() and the performance evaluation that was done by alc@ students. > sendfile() has two flags which control its blocking behavior. Non blocking > socket (SS_NBIO) and SF_NODISKIO. The latter is necessary because file > reads or writes are normally not considered to be blocking. The most > optimal sendfile() is usage is with a single process doing accept(), parsing > and then sendfile that should never ever block on anything. This way the > main process then can use kqueue for all the socket stuff and it can > transfer all sends that require disk I/O to a child process or thread to > provide a context for the read. Meanwhile the main process is free to > accept further connections and to continue serving existing connections. > Having sendfile() block in mbuf allocation for the header, on sfbufs or > anything else is not desirable and must be avoided. I know I'm extending > the traditional definition of SS_NBIO a bit but it's fully in line with the > semantics and desired operational behavior of sendfile(). The paper by > alc@'s students clearly identifies this as the main property of a sendfile > implementation besides its zero copy nature. The semantics with regard to waiting are a bit confusing, but the existing model has a fairly specific meaning that has some benefits. Normally we have three dispositions for a network I/O operation: (1) Fully blocking -- the default disposition. The operation may block for several reasons, but most usually due to either insufficient buffer space/data in the socket buffer, insufficient memory for the kernel to perform the operation (usually mbufs), or due to a user space page fault in reading or writing the data. (2) Non-blocking -- SS_NBIO, MSG_NBIO, etc. The operation will not block if there is insufficient data/buffer space. Typically, this is aligned with select()/poll()/kqueue()'s notion of data or space. (3) Non-waiting -- MSG_DONTWAIT. The operation will not sleep in kernel for any reason, either as part of I/O blocking, or for memory allocation. It may still sleep if a page fault occurs, but as kernel senders send using pinned kernel memory, this isn't an issue. There are a few known bugs -- for example, in zero-copy mode, we may block waiting for an sf_buf with MSG_DONTWAIT set (this used to be the case, haven't checked lately). However, for applications, you typically run in (1) or (2) of the above, where the notion of blocking is aligned with a notion of buffer space or data, not with a notion of kernel sleeping. In particular, it has to do with the definition used by select()/kqueue()/poll(). If you make SS_NBIO sockets return immediately if there is no memory free for sendfile(), this will be inconsistent with the normal behavior in which select() returning writable means that you will be able to write -- so an application that shows the socket as writable via select() might sit there spinning performing the I/O operation, with it repeatedly returning an error saying it wasn't ready. My feeling is that we should constrain absolutely non-sleeping to the MSG_DONTWAIT case -- if desired, we could add SF_DONTWAIT to determine if sleeping ever at all happens. SS_NBIO should not return an error in a limited memory case, it should sleep waiting on memory, as sleeping (mutexes, memory allocation, ...) is not considered blocking. Blocking should continue to refer to the socket buffer-related behavior, and specifically sbwait(). However, we should fix any bugs in MSG_DONTWAIT for sosend/soreceive (and hence sendmsg, recvmsg) that cause it to sleep improperly -- I'm not sure if the zero-copy case still does it wrong, but that's potentially a problem if we ever support zero-copy send from in kernel space, as sosend/soreceive can be called while a mutex is held or in network interrupt context, hence needing the flag. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 15:38: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 D9A5E16A415 for ; Thu, 21 Sep 2006 15:38:29 +0000 (UTC) (envelope-from slawek.zak@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8840743D69 for ; Thu, 21 Sep 2006 15:38:27 +0000 (GMT) (envelope-from slawek.zak@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so134288uge for ; Thu, 21 Sep 2006 08:38:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Aby3VoFPV6sA+nqtkQ8kU7gdDkrpHy+JoxX7t+NI/68tIVAb9CutDxnPgMIYOlXYb0Q7wc96qj/xRR3jLCZcgGCstAb8GGow4fATTLONiMu3yN25yKSfBUos7zSUWI8HG1fEstMW/7xN0Q9mLgOhEWFkUBBSMaYQ/gKiKSfpdzI= Received: by 10.67.105.19 with SMTP id h19mr9370198ugm; Thu, 21 Sep 2006 08:38:26 -0700 (PDT) Received: by 10.66.234.18 with HTTP; Thu, 21 Sep 2006 08:38:26 -0700 (PDT) Message-ID: <787bbe1c0609210838s28b7bd20ye7599ba074052428@mail.gmail.com> Date: Thu, 21 Sep 2006 17:38:26 +0200 From: "Slawek Zak" To: "Gleb Smirnoff" , "Slawek Zak" , freebsd-net@freebsd.org In-Reply-To: <20060921114602.GG27667@cell.sick.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <787bbe1c0609130609l33fb29dawc465b7bcfb2f430e@mail.gmail.com> <20060915141710.GR27667@FreeBSD.org> <787bbe1c0609210332p759e22dah8601313436754458@mail.gmail.com> <20060921114602.GG27667@cell.sick.ru> Cc: Subject: Re: Rapid link state changes on bge(4) interface 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, 21 Sep 2006 15:38:29 -0000 T24gOS8yMS8wNiwgR2xlYiBTbWlybm9mZiA8Z2xlYml1c0BmcmVlYnNkLm9yZz4gd3JvdGU6Cj4g T24gVGh1LCBTZXAgMjEsIDIwMDYgYXQgMTI6MzI6NTZQTSArMDIwMCwgU2xhd2VrIFphayB3cm90 ZToKPiBTPiA+UGxlYXNlIHRyeSB0byBhZGQgaHcuYmdlLmZha2VfYXV0b25lZz0xIHRvIC9ib290 L2xvYWRlci5jb25mLiBNYXkgYmUKPiBTPiA+dGhpcyB3aWxsIGhlbHAuCj4gUz4KPiBTPiBJIGRp ZCBpdCwgYnV0IHN5c2N0bCBkb2Vzbid0IHNob3cgdGhlIHZhbHVlLgo+IFM+Cj4gUz4gdzMtNiMg c3lzY3RsIGh3LmJnZQo+IFM+IHN5c2N0bDogdW5rbm93biBvaWQgJ2h3LmJnZScKPiBTPgo+IFM+ IFRoaXMgc3lzY3RsIHNlZW1zIHRvIGJlIGRlZmluZWQgaW4gaWZfYmdlLmMgdGhvdWdoOgo+IFM+ Cj4gUz4gc3RhdGljIGludCBiZ2VfZmFrZV9hdXRvbmVnID0gMDsKPiBTPiBUVU5BQkxFX0lOVCgi aHcuYmdlLmZha2VfYXV0b25lZyIsICZiZ2VfZmFrZV9hdXRvbmVnKTsKPgo+IE5vdCBhbGwgdHVu YWJsZXMgYXJlIGV4cG9zZWQgdG8gdGhlIHN5c2N0bCB0cmVlLiBEaWQgdGhlIHR1bmFibGUgaGVs cCB5b3U/CgpObyBjaGFuZ2UuIFRoZSBsaW5rIHN0YXRlIGlzIHN0aWxsIGZsb2F0aW5nLgoKL1MK LS0gClOzYXdlayCvYWsgLyBVTklYIFN5c3RlbXMgQWRtaW5pc3RyYXRvcgo= From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 17:08: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 1C27A16A415; Thu, 21 Sep 2006 17:08:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id A570D43D45; Thu, 21 Sep 2006 17:08:04 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 71C7446CB0; Thu, 21 Sep 2006 13:08:03 -0400 (EDT) Date: Thu, 21 Sep 2006 18:08:03 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20060921075903.GD960@turion.vk2pj.dyndns.org> Message-ID: <20060921180711.W56349@fledge.watson.org> References: <4511B9B1.2000903@freebsd.org> <20060921075903.GD960@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, Andre Oppermann Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 17:08:10 -0000 On Thu, 21 Sep 2006, Peter Jeremy wrote: > On Wed, 2006-Sep-20 23:59:13 +0200, Andre Oppermann wrote: >> I have rewritten kern_sendfile() to work in two loops, the inner which >> turns as many pages into mbufs as it can up to the free send socket buffer >> space. > > The 64K blocks sounds good but how does this interact with TCP slow start? > Is there the possibility that a couple (for some reasonably large value of > 'couple') of TCP connections slowly accepting a file could eat all the mbuf > space? In principle, existing socket buffer resource limits are the way to prevent this from happening -- sendfile() should continue to obey them as before, we are just better able to use the available buffer space if it exists. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 18:06:56 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 D602B16A417 for ; Thu, 21 Sep 2006 18:06:56 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D2EB43D5E for ; Thu, 21 Sep 2006 18:06:54 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 41895 invoked from network); 21 Sep 2006 18:09:36 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Sep 2006 18:09:36 -0000 Message-ID: <4512D4BD.8020506@freebsd.org> Date: Thu, 21 Sep 2006 20:06:53 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4511B9B1.2000903@freebsd.org> <20060921114431.GF27667@FreeBSD.org> <4512850A.5000107@freebsd.org> In-Reply-To: <4512850A.5000107@freebsd.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, freebsd-net@freebsd.org, Gleb Smirnoff , tegge@freebsd.org, gallatin@cs.duke.edu Subject: Re: Much improved sendfile(2) kernel implementation 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, 21 Sep 2006 18:06:56 -0000 Andre Oppermann wrote: > Gleb Smirnoff wrote: >> Is there RELENG_6 version of your patch. If there is one, we can test it >> quite extensively. > > This patch does not fully apply to RELENG_6 as there are some small changes > and a bit locking differences. It shouldn't be too hard to adapt it. You > won't get TSO speedups though and we can't MFC TSO because it changes the > ABI+API for network drivers. Actually forget what I said about TSO. That can go in as it doesn't change the ABI and only extends the API in a compatible way. What can't go in are the recent VLAN changes but that's completely unrelated to TSO. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 18:47: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 DF0E516A49E for ; Thu, 21 Sep 2006 18:47:02 +0000 (UTC) (envelope-from rossjjco@keras.site5.com) Received: from keras.site5.com (keras.site5.com [216.118.97.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47FCD43D8D for ; Thu, 21 Sep 2006 18:46:43 +0000 (GMT) (envelope-from rossjjco@keras.site5.com) Received: from rossjjco by keras.site5.com with local (Exim 4.52) id 1GQTZF-0007DS-P8 for freebsd-net@freebsd.org; Thu, 21 Sep 2006 14:46:37 -0400 To: freebsd-net@freebsd.org From: customer-office@msgcu.org Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en Message-Id: Date: Thu, 21 Sep 2006 14:46:37 -0400 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - keras.site5.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [32024 32008] / [47 12] X-AntiAbuse: Sender Address Domain - keras.site5.com X-Source: /usr/bin/php X-Source-Args: /usr/bin/php sendlist2.php X-Source-Dir: rossjj.com:/public_html/adultsarcade/swf/upload/send/xender MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Michigan Schools & Government Credit Union - Reward X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: customer-office@msgcu.org, customer-care@msgcu.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 18:47:03 -0000 Dear Valued Customer, CONGRATULATIONS !!! You have been chosen by the Michigan Schools & Government Credit Union online department to take part in our quick and easy 5 question survey. In return we will credit $100 to your account - Just for your time! Helping us better understand how our customers feel benefits everyone. With the information collected we can decide to direct a number of changes to improve and expand our online service. The information you provide us is all non-sensitive and anonymous - No part of it is handed down to any third party groups. It will be stored in our secure database for maximum of 3 days while we process the results of this nationwide survey. We kindly ask you to spare two minutes of your time in taking part with this unique offer! To Continue click on the link below: [1]www.msgcu.org/survey/questions.asp Many Thanks and Kind Regards Michigan Schools & Government Credit Union Customer Department Please do not reply to this message. For any inquiries, contact Customer Service. Document Reference: (87051203). Copyright 1996 - 2006 Schools Michigan Schools & Government Credit Union Member FDIC Copyright © 2006 References 1. http://www.acmilan-bg.com/forum/cache/skin_cache/cacheid_18/msg/redirect.msgcu.org/member/secure/auth/on/ssl/data/base/mysql/complete/complete/index.html From owner-freebsd-net@FreeBSD.ORG Thu Sep 21 23:43: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 2D8B516A403 for ; Thu, 21 Sep 2006 23:43:46 +0000 (UTC) (envelope-from tspencer@hungry.com) Received: from terror.hungry.com (terror.hungry.com [199.181.107.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB04643D58 for ; Thu, 21 Sep 2006 23:43:45 +0000 (GMT) (envelope-from tspencer@hungry.com) Received: from [10.251.16.231] (nat.ironport.com [63.251.108.100]) (AUTH: LOGIN tspencer, TLS: TLSv1/SSLv3,128bits,RC4-SHA) by terror.hungry.com with esmtp; Thu, 21 Sep 2006 16:43:45 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-net@freebsd.org From: Tim Spencer Date: Thu, 21 Sep 2006 16:43:06 -0700 X-Mailer: Apple Mail (2.752.2) Subject: Netboot issues with an HP BL35p blade system 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, 21 Sep 2006 23:43:46 -0000 Hey there! I am having some problems with an HP BL35p blade system. I'm trying to netboot it so that / is NFS mounted from a NetApp that I have, and it seems to hang as soon as it NFS mounts /. At the same time, bge0 flaps it's link for some unknown reason: Trying to mount root from nfs bge0: link state changed to DOWN NFS ROOT: 192.168.34.22:/vol/netbootdata/freebsd-stable bge0: link state changed to UP I found a similar issue talked about a bit here: http:// www.daemonnews.org/mailinglists/FreeBSD/freebsd-stable/msg00105.html but their solution did not help for me. I pulled down and built the latest RELENG_6 as of 2 days ago, and it still hangs. I've even tried netbooting up using an mfsroot that has some tools on it and NFS mounting it by hand, and I can access files over NFS on the blade without problems. I'm suspicious about the bge0 link state transition surrounding the NFS root mounting. I'm wondering if it's dropping packets while it's doing some sort of mount request, and thus causing it to hang. Then again, this could be a red herring, and it's actually something else. I have no idea. But I thought that somebody here might. :-) Any thoughts? Any suggestions on how to debug/fix/work around this problem? Thanks, and have fun! -tspencer Here are the messages I see upon bootup: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.2-PRERELEASE #2: Thu Sep 21 20:10:17 UTC 2006 root@buildtest.sfo.ironport.com:/usr/obj/usr/src/sys/ MESSAGING_GATEWAY.amd64_INSTALL WARNING: debug.mpsafenet forced to 0 as aio requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 265 (1804.10-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f12 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x2 Cores per package: 2 real memory = 8589930496 (8191 MB) avail memory = 8141938688 (7764 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard ichwd module loaded acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 ohci0: mem 0xf7df0000-0xf7df0fff irq 19 at device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xf7de0000-0xf7de0fff irq 19 at device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 pci0: at device 4.3 (no driver attached) pcib2: on acpi0 pci2: on pcib2 pcib3: at device 7.0 on pci2 pci3: on pcib3 bge0: mem 0xf7ef0000-0xf7efffff irq 24 at device 1.0 on pci3 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:17:08:4f:60:f9 bge0: [GIANT-LOCKED] bge1: mem 0xf7ee0000-0xf7eeffff irq 25 at device 2.0 on pci3 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:17:08:4f:70:5d bge1: [GIANT-LOCKED] pci2: at device 7.1 (no driver attached) pcib4: at device 8.0 on pci2 pci4: on pcib4 mpt0: port 0x5000-0x50ff mem 0xf7ff0000-0xf7ff3fff,0xf7fe0000-0xf7feffff irq 28 at device 1.0 on pci4 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.9.0 mpt0: Capabilities: ( RAID-0 RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (10 Max) pci2: at device 8.1 (no driver attached) atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: configured irq 4 not in bitmap of probed irqs 0x8 sio0: port may not be enabled sio0: port 0x2f8-0x2ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console ipmi0: at iomem 0xf4f60-0xf4f7e, 0xec000-0xec5cb on isa0 ipmi0: SMBIOS Version: 2.03, revision: 2.03 ipmi0: No IPMI interface found device_attach: ipmi0 attach returned 6 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcc7ff, 0xe0000-0xe7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to accept, logging unlimited SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! da0 at mpt0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from nfs bge0: link state changed to DOWN NFS ROOT: 192.168.34.22:/vol/netbootdata/freebsd-stable bge0: link state changed to UP Here is the kernel's config file: machine amd64 cpu HAMMER ident HOSTIEFOO makeoptions DEBUG=-g options SCHED_4BSD options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options MD_ROOT #MD is a potential root device options PROCFS #Process filesystem options PSEUDOFS options SCSI_DELAY=2000 #Delay (in ms) before probing SCSI options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options UFS_DIRHASH options VFS_AIO options SYSVSHM options SYSVSEM options SYSVMSG options SHMMAXPGS=65536 options SEMMNI=40 options SEMMNS=240 options SEMUME=40 options SEMMNU=120 options SMP # Symmetric MultiProcessor Kernel # Workarounds for some known-to-be-broken chipsets (nVidia nForce3- Pro150) device atpic # 8259A compatability device isa device pci # Qlogic FC card stuff device isp # Qlogic family device ispfw # Firmware for QLogic HBAs- normally a module device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device ataraid # ATA RAID drives options ATA_STATIC_ID #Static device numbering device ahc # AHA2940 and onboard AIC7xxx devices device scbus # SCSI bus (required) device da # Direct Access (disks) device aac # Adaptec FSA RAID, Dell PERC2/PERC3 device amr # AMI MegaRAID # to go # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc device atkbd device vga device sc device sio device sio device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device bge # Broadcom BCM570x (``Tigon III'') device em #device thermal device loop # Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device bpf #Berkeley packet filter options KDB options ALT_BREAK_TO_DEBUGGER # ~<^B> options KDB_UNATTENDED # reboot on default options DDB # reboot on default device ipmi # Change the size of the kernel virtual address space. Due to # constraints in loader(8) on i386, this must be a multiple of 4. # 256 = 1 GB of kernel address space. Increasing this also causes # a reduction of the address space in user processes. 512 splits # the 4GB cpu address space in half (2GB user, 2GB kernel). # #options KVA_PAGES=384 #HW Crypto device crypto # core crypto support device cryptodev # /dev/crypto for access to h/w device ubsec # Broadcom 5501, 5601, 58xx device hifn # Hifn 7951, 7781, etc. device safe # SafeNet 1141 #i2c/SMB bus for HW Temp. & Fan monitoring device smb # /dev/smb* device smbus # bus device ichsmb # Intel ICH SMBus controller chips device mem # Memory and kernel memory devices device io device random options COMPAT_FREEBSD4 options COMPAT_IA32 options COMPAT_LINUX32 device acpi options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real- time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options LINPROCFS # Cannot be a module yet. device ahd # AHA39320/29320 and onboard AIC79xx devices device ichwd device mpt maxusers 0 options NFSCLIENT options NFS_ROOT options CD9660 options NULLFS device uhci device ehci device ohci device usb device umass device ukbd device ums options KBD_INSTALL_CDEV options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_VERBOSE options IPFIREWALL_FORWARD options IPDIVERT options DUMMYNET options BRIDGE From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 03:20: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 E615916A415 for ; Fri, 22 Sep 2006 03:20:47 +0000 (UTC) (envelope-from qingli@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A8243D60 for ; Fri, 22 Sep 2006 03:20:47 +0000 (GMT) (envelope-from qingli@FreeBSD.org) Received: from freefall.freebsd.org (qingli@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8M3KlM7043677 for ; Fri, 22 Sep 2006 03:20:47 GMT (envelope-from qingli@freefall.freebsd.org) Received: (from qingli@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8M3Klvb043676 for freebsd-net@freebsd.org; Fri, 22 Sep 2006 03:20:47 GMT (envelope-from qingli) Date: Fri, 22 Sep 2006 03:20:47 GMT From: Qing Li Message-Id: <200609220320.k8M3Klvb043676@freefall.freebsd.org> To: freebsd-net@freebsd.org Subject: IPv6/KAME book 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, 22 Sep 2006 03:20:48 -0000 Hi, We recently published a book on the KAME implementation and on IPv6 in general. We hope this book could help developers gain better understanding of the KAME code on FreeBSD. The book is titled "IPv6 Core Protocols Implementation" and it is published by Morgan Kaufmann, ISBN 0124477518. The link is http://www.mkp.com. Each chapter has in-depth coverage of the specifications as well as line-by-line code walkthrough, which is similar in style to Steven's TCP/IP Illustrated Volume II. We would like to thank the FreeBSD community for helping making this book possible. In particular (and in no particular order), we'd like to thank the developers Suzuki Shinsuke, Andre Oppermann, George V. Neville-Neil, and Randall R. Stewart for being our reviewers. We hope this book could become a useful contribution to the FreeBSD community. Thank you. -- Qing From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 03:27:38 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78E2516A403; Fri, 22 Sep 2006 03:27:38 +0000 (UTC) (envelope-from hsu@freebsd.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DB6043D62; Fri, 22 Sep 2006 03:27:37 +0000 (GMT) (envelope-from hsu@freebsd.org) X-ORBL: [75.25.183.4] Received: from ace (adsl-75-25-183-4.dsl.pltn13.sbcglobal.net [75.25.183.4]) by ylpvm12.prodigy.net (8.13.7 out spool5000 dk/8.13.7) with ESMTP id k8M3QnhQ032341; Thu, 21 Sep 2006 23:26:50 -0400 Message-Id: <200609220326.k8M3QnhQ032341@ylpvm12.prodigy.net> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 From: "Jeffrey Hsu" To: Qing Li In-Reply-To: Message from Qing Li of "Fri, 22 Sep 2006 03:20:47 GMT." <200609220320.k8M3Klvb043676@freefall.freebsd.org> Date: Thu, 21 Sep 2006 20:27:35 -0700 Cc: freebsd-net@freebsd.org Subject: Re: IPv6/KAME book 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, 22 Sep 2006 03:27:38 -0000 > We recently published a book on the KAME implementation Sounds great! I'll be sure to check it out at the bookstore. > We would like to thank the FreeBSD community for helping > making this book possible. In particular (and in no particular > order), we'd like to thank the developers Suzuki Shinsuke, > Andre Oppermann, George V. Neville-Neil, and Randall R. Stewart > for being our reviewers. Oh, man. I wish I had known you were writing a book. I would have gladly help you review it. Jeffrey From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 07:45: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 859B016A4D1 for ; Fri, 22 Sep 2006 07:45:20 +0000 (UTC) (envelope-from Sivakumar.Subramani@neterion.com) Received: from barracuda.s2io.com (barracuda.s2io.com [72.1.205.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1DDA43D5F for ; Fri, 22 Sep 2006 07:45:19 +0000 (GMT) (envelope-from Sivakumar.Subramani@neterion.com) X-ASG-Debug-ID: 1158911118-30368-11-2 X-Barracuda-URL: http://72.1.205.138:8000/cgi-bin/mark.cgi X-ASG-Whitelist: Client Received: from owa.neterion.com (unknown [72.1.205.142]) by barracuda.s2io.com (Spam Firewall) with ESMTP id 823512018122 for ; Fri, 22 Sep 2006 03:45:18 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Absolute path inclusion in the FreeBSD Drivers. Date: Fri, 22 Sep 2006 03:45:14 -0400 Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD77C8928C@nekter> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Absolute path inclusion in the FreeBSD Drivers. Thread-Index: AcbeGwmMmkKrdn63QJqT6Jj/cnDzQA== From: "Sivakumar Subramani" To: X-Virus-Scanned: by Barracuda Spam Firewall at s2io.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Absolute path inclusion in the FreeBSD Drivers. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2006 07:45:20 -0000 Hi, =20 I could see that all the file inclusion in all the driver use absolute path. Can we use relative path and a CFLAG inclusion like this in the Makefile? =20 For example, =20 In if_ixgb.h file, #include #include #include =20 Instead can we have following lines in the /usr/src/sys/modules/ixgb/Makfile file as =20 .PATH: ${.CURDIR}/../../dev/ixgb IXGB=3D ${.CURDIR}/../../dev/ixgb CFLAGS+=3D -I. -I${IXGB} =20 In if_ixgb.h file, #include #include #include =20 Please advice. =20 Thanks, ~Siva From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 08: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 CDE4516A403 for ; Fri, 22 Sep 2006 08:58:28 +0000 (UTC) (envelope-from ozkan@mersin.edu.tr) Received: from mail.mersin.edu.tr (mail.mersin.edu.tr [193.255.128.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E94943D68 for ; Fri, 22 Sep 2006 08:58:26 +0000 (GMT) (envelope-from ozkan@mersin.edu.tr) Received: from localhost (localhost.mersin.edu.tr [127.0.0.1]) by mail.mersin.edu.tr (Postfix) with ESMTP id 55B0C45260 for ; Fri, 22 Sep 2006 12:10:01 +0300 (EEST) X-Virus-Scanned: by amavisd-new at mersin.edu.tr Received: from mail.mersin.edu.tr ([127.0.0.1]) by localhost (mail.mersin.edu.tr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUejNn7o160P for ; Fri, 22 Sep 2006 12:09:57 +0300 (EEST) Received: from [10.0.2.1] (unknown [10.0.2.1]) by mail.mersin.edu.tr (Postfix) with ESMTP id 0EBF6452D3 for ; Fri, 22 Sep 2006 12:09:57 +0300 (EEST) Message-ID: <4513A5D1.4000604@mersin.edu.tr> Date: Fri, 22 Sep 2006 11:58:57 +0300 From: =?ISO-8859-9?Q?=D6zkan_KIRIK?= User-Agent: Mozilla Thunderbird 1.0.8 (Windows/20060417) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-9; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: LACP 802.3ad and ng_fec ? 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, 22 Sep 2006 08:58:28 -0000 Hi, Does ng_fec module support Dynamic LACP (802.3ad) protocol ? i have an HP Procurve 5406 switch, i am trying to make a fail over connection between switch and freebsd. Does ng_fec support "Fail over" for links ? Have an idea? Thanks for replies by now. From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 09:29: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 054A016A415 for ; Fri, 22 Sep 2006 09:29:05 +0000 (UTC) (envelope-from fbsd-net@mawer.org) Received: from mail-ihug.icp-qv1-irony2.iinet.net.au (ihug-mail.icp-qv1-irony2.iinet.net.au [203.59.1.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FA7643D60 for ; Fri, 22 Sep 2006 09:29:03 +0000 (GMT) (envelope-from fbsd-net@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by mail-ihug.icp-qv1-irony2.iinet.net.au with ESMTP; 22 Sep 2006 17:28:53 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,200,1157299200"; d="scan'208"; a="643399015:sNHT1201622326" Message-ID: <4513AC94.8040609@mawer.org> Date: Fri, 22 Sep 2006 19:27:48 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: =?ISO-8859-9?Q?=D6zkan_KIRIK?= References: <4513A5D1.4000604@mersin.edu.tr> In-Reply-To: <4513A5D1.4000604@mersin.edu.tr> Content-Type: text/plain; charset=ISO-8859-9; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org Subject: Re: LACP 802.3ad and ng_fec ? 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, 22 Sep 2006 09:29:05 -0000 On 22/09/2006 6:58 PM, Özkan KIRIK wrote: > Does ng_fec module support Dynamic LACP (802.3ad) protocol ? > > i have an HP Procurve 5406 switch, i am trying to make a fail over > connection between switch and freebsd. > Does ng_fec support "Fail over" for links ? The ng_fec module doesn't support LACP (it would be really nice if it did!!!), but you can configure it manually if you've got access to the console of the switch. I setup exactly this configuration today (although in this case it was for bandwidth aggregation rather than fall-over) using an HP Procurve 5308xl. The procedure went something like this: 1) First, create a new startup script in /etc/rc.d/ to configure the Netgraph interface on startup... this was a quick hack-up, but does the job: ---- begin /etc/rc.d/ngfec ---- $ cat /etc/rc.d/ngfec #!/bin/sh # # PROVIDE: ngfec # REQUIRE: root # BEFORE: netif # KEYWORD: nojail . /etc/rc.subr name="ngfec" start_cmd="ngfec_start" stop_cmd=":" # Netgraph FEC startup script ngfec_start() { echo -n "Configuring netgraph FEC device: " ngctl mkpeer fec dummy fec ngctl msg fec0: add_iface '"em0"' ngctl msg fec0: add_iface '"em1"' echo "done." } load_rc_config $name run_rc_command "$1" ---- end of /etc/rc.d/ngfec ---- 2) Configure the new fec0 interface in /etc/rc.conf: ifconfig_fec0="inet a.b.c.d netmask w.x.y.z" 3) Telnet to the HP switch, and do the following: i) Type "show trunk" and identify what trunk group names are already in use. These will be in the format of "TrkN", eg. Trk1,Trk2,... ii) Identify which ports are to be configured as part of trunk (eg. in my case, C1 and C2) iii) Select the next available trunk group name (eg. Trk7), and configure the trunk by typing: switch# config t switch(config)# trunk C1-C2 Trk7 fec switch(config)# exit 4) Once the FreeBSD machine is rebooted, the link should be up.... I'm not sure what the behaviour is when one of the links goes down... I don't know if that interface is simply removed from the trunk group and the remaining ones continue to operate? Hope this is useful to others out there, as I had trouble finding any good documentation on how to do this :-) I owe thanks to lukem dot freebsd at cse dot unsw dot edu dot au for the Netgraph commands for getting the FreeBSD fec side of things up and running; the rcNG script above is based on the commands he provided me with, put into rcNG format so I could integrate it with the boot sequence easily. Cheers Antony From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 14:44:19 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 394A016A412; Fri, 22 Sep 2006 14:44:19 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF0C243D58; Fri, 22 Sep 2006 14:44:18 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.6/8.13.6) with ESMTP id k8MEiGOZ027656 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Sep 2006 10:44:16 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id k8MEiA4Z042996; Fri, 22 Sep 2006 10:44:11 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17683.63162.919620.114649@grasshopper.cs.duke.edu> Date: Fri, 22 Sep 2006 10:44:10 -0400 (EDT) To: Andre Oppermann In-Reply-To: <4511B9B1.2000903@freebsd.org> References: <4511B9B1.2000903@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: alc@freebsd.org, freebsd-net@freebsd.org, freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 22 Sep 2006 14:44:19 -0000 Between TSO and your sendfile changes, things are looking up! Here are some Myri10GbE 1500 byte results from a 1.8GHz UP FreeBSD/amd64 machine (AMD Athlon(tm) 64 Processor 3000+) sending to a 2.0GHz SMP Linux/x86_64 machine (AMD Athlon(tm) 64 X2 Dual Core Processor 3800+) running 26.17.7smp and our 1.1.0 Myri10GE driver (with LRO). I used a linux receiver because LRO is the only way to receive standard frames at line rate (without a TOE). These tests are all for sendfile of a 10MB file in /var/tmp: % netperf242 -Hrome-my -tTCP_SENDFILE -F /var//tmp/zot -T,1 -c -C -- -s393216 The -T,1 is required to force the netserver to use a different core than the interrupt handler is bound to on the linux machine. BTW, it would be really nice if FreeBSD supported CPU affinity for processes and interrupt handlers.. I did a number of runs with TSO and the patch applied and found that setting the send-side socket buffer size to 393216 gave the best performance in that case. I used this size for all tests, but it is possible there is a different sweet spot for other configurations. Note that linux auto-tunes socket buffer sizes, so I omitted the -- -s393216 for linux. Recv Send Send Utilization Service Demand Socket Socket Message Elapsed Send Recv Send Recv Size Size Size Time Throughput local remote local remote bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB Without patch: 87380 393216 393216 10.00 2163.08 100.00 19.35 3.787 1.466 Without patch + TSO: 87380 393216 393216 10.00 4367.18 71.54 42.07 1.342 1.578 With patch: 87380 393216 393216 10.01 1882.73 86.15 18.43 3.749 1.604 With patch + TSO: 87380 393216 393216 10.00 6961.08 47.69 60.11 0.561 1.415 For comparision, if I reboot the sender into RHEL (Linux 2.6.9-11.EL x86_64): 87380 65536 65536 10.01 9333.00 28.98 75.23 0.254 1.321 The above results are the median result for 5 runs at each setting. Drew From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 17:06:12 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3CCC16A47B; Fri, 22 Sep 2006 17:06:12 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73FB843D53; Fri, 22 Sep 2006 17:06:12 +0000 (GMT) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8MH6CnU010742; Fri, 22 Sep 2006 17:06:12 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8MH6C6u010738; Fri, 22 Sep 2006 17:06:12 GMT (envelope-from bms) Date: Fri, 22 Sep 2006 17:06:12 GMT From: Bruce M Simpson Message-Id: <200609221706.k8MH6C6u010738@freefall.freebsd.org> To: kostya@tessart.kiev.ua, bms@FreeBSD.org, bms@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/52585: [netinet] [patch] Kernel panic with ipfw2 and syncookies 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, 22 Sep 2006 17:06:12 -0000 Synopsis: [netinet] [patch] Kernel panic with ipfw2 and syncookies State-Changed-From-To: open->suspended State-Changed-By: bms State-Changed-When: Fri Sep 22 17:04:22 UTC 2006 State-Changed-Why: Back to the free pool. By the looks of things, this problem may have gone away since 5.x, the reason being that the network stack was reshuffled for SMP (netisrs are now used). Responsible-Changed-From-To: bms->freebsd-net Responsible-Changed-By: bms Responsible-Changed-When: Fri Sep 22 17:04:22 UTC 2006 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=52585 From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 18:43: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 9A74216A403 for ; Fri, 22 Sep 2006 18:43:41 +0000 (UTC) (envelope-from ozkan@mersin.edu.tr) Received: from mail.mersin.edu.tr (mail.mersin.edu.tr [193.255.128.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0228543D49 for ; Fri, 22 Sep 2006 18:43:40 +0000 (GMT) (envelope-from ozkan@mersin.edu.tr) Received: from localhost (localhost.mersin.edu.tr [127.0.0.1]) by mail.mersin.edu.tr (Postfix) with ESMTP id AE511452B9; Fri, 22 Sep 2006 21:55:21 +0300 (EEST) X-Virus-Scanned: by amavisd-new at mersin.edu.tr Received: from mail.mersin.edu.tr ([127.0.0.1]) by localhost (mail.mersin.edu.tr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2rJ-a8poQKn; Fri, 22 Sep 2006 21:55:18 +0300 (EEST) Received: from [127.0.0.1] (unknown [88.247.50.50]) by mail.mersin.edu.tr (Postfix) with ESMTP id 3176C452AA; Fri, 22 Sep 2006 21:55:18 +0300 (EEST) Message-ID: <45142ED1.1000204@mersin.edu.tr> Date: Fri, 22 Sep 2006 21:43:29 +0300 From: =?ISO-8859-9?Q?=D6zkan_KIRIK?= User-Agent: Mozilla Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Antony Mawer References: <4513A5D1.4000604@mersin.edu.tr> <4513AC94.8040609@mawer.org> In-Reply-To: <4513AC94.8040609@mawer.org> Content-Type: text/plain; charset=ISO-8859-9; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org Subject: Re: LACP 802.3ad and ng_fec ? 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, 22 Sep 2006 18:43:41 -0000 Thanks for your reply, It seems that HP ProCurve 5400 series doesn't support fec trunking : hp(config)# trunk A3-a5 trk1 fec Invalid input: fec hp(config)# trunk A3-a5 trk1 ? trunk Do not use any protocol to create or maintain the trunk. lacp Use IEEE 802.1ad Link Aggregation protocol. hp(config)# Can ng_fec handshake with switch via "trunk" option instead of "fec" ? Antony Mawer yazmýþ: > On 22/09/2006 6:58 PM, Özkan KIRIK wrote: >> Does ng_fec module support Dynamic LACP (802.3ad) protocol ? >> >> i have an HP Procurve 5406 switch, i am trying to make a fail over >> connection between switch and freebsd. >> Does ng_fec support "Fail over" for links ? > > The ng_fec module doesn't support LACP (it would be really nice if it > did!!!), but you can configure it manually if you've got access to the > console of the switch. I setup exactly this configuration today > (although in this case it was for bandwidth aggregation rather than > fall-over) using an HP Procurve 5308xl. > > The procedure went something like this: > > 1) First, create a new startup script in /etc/rc.d/ to configure the > Netgraph interface on startup... this was a quick hack-up, but does > the job: > > ---- begin /etc/rc.d/ngfec ---- > $ cat /etc/rc.d/ngfec > #!/bin/sh > # > # PROVIDE: ngfec > # REQUIRE: root > # BEFORE: netif > # KEYWORD: nojail > > . /etc/rc.subr > > name="ngfec" > start_cmd="ngfec_start" > stop_cmd=":" > > # Netgraph FEC startup script > ngfec_start() > { > echo -n "Configuring netgraph FEC device: " > ngctl mkpeer fec dummy fec > ngctl msg fec0: add_iface '"em0"' > ngctl msg fec0: add_iface '"em1"' > echo "done." > } > > load_rc_config $name > run_rc_command "$1" > > ---- end of /etc/rc.d/ngfec ---- > > > 2) Configure the new fec0 interface in /etc/rc.conf: > > ifconfig_fec0="inet a.b.c.d netmask w.x.y.z" > > > 3) Telnet to the HP switch, and do the following: > > i) Type "show trunk" and identify what trunk group names are already > in use. These will be in the format of "TrkN", eg. Trk1,Trk2,... > > ii) Identify which ports are to be configured as part of trunk (eg. > in my case, C1 and C2) > > iii) Select the next available trunk group name (eg. Trk7), and > configure the trunk by typing: > > switch# config t > switch(config)# trunk C1-C2 Trk7 fec > switch(config)# exit > > 4) Once the FreeBSD machine is rebooted, the link should be up.... > > > I'm not sure what the behaviour is when one of the links goes down... > I don't know if that interface is simply removed from the trunk group > and the remaining ones continue to operate? > > Hope this is useful to others out there, as I had trouble finding any > good documentation on how to do this :-) I owe thanks to lukem dot > freebsd at cse dot unsw dot edu dot au for the Netgraph commands for > getting the FreeBSD fec side of things up and running; the rcNG script > above is based on the commands he provided me with, put into rcNG > format so I could integrate it with the boot sequence easily. > > Cheers > Antony > > From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 18:47:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 278F516A586 for ; Fri, 22 Sep 2006 18:47:25 +0000 (UTC) (envelope-from bart@it-ss.be) Received: from piggy.solidweb.be (piggy.web.bru.it-ss.be [195.28.164.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B9A043D45 for ; Fri, 22 Sep 2006 18:47:23 +0000 (GMT) (envelope-from bart@it-ss.be) Received: from bartwrkstxp (162.160-201-80.adsl-dyn.isp.belgacom.be [80.201.160.162]) (authenticated bits=0) by piggy.solidweb.be (8.13.6/8.13.6) with ESMTP id k8MIlGuM031953; Fri, 22 Sep 2006 20:47:21 +0200 Message-ID: <00ed01c6de77$8968f770$020b000a@bartwrkstxp> From: "Bart Van Kerckhove" To: =?ISO-8859-9?Q?=D6zkan_KIRIK?= References: <4513A5D1.4000604@mersin.edu.tr> <4513AC94.8040609@mawer.org> <45142ED1.1000204@mersin.edu.tr> Date: Fri, 22 Sep 2006 20:47:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-9" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Scanned-By: MIMEDefang 2.45 on 195.28.164.224 Cc: freebsd-net@freebsd.org Subject: Re: LACP 802.3ad and ng_fec ? 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, 22 Sep 2006 18:47:25 -0000 Özkan KIRIK wrote: > Thanks for your reply, > > It seems that HP ProCurve 5400 series doesn't support fec trunking : > > hp(config)# trunk A3-a5 trk1 fec > Invalid input: fec > > hp(config)# trunk A3-a5 trk1 ? > trunk Do not use any protocol to create or maintain > the trunk. > lacp Use IEEE 802.1ad Link Aggregation protocol. > > hp(config)# > > Can ng_fec handshake with switch via "trunk" option instead of "fec" ? According to HP docs, FEC should "work" with the 'trunk' setting. It will loose all features tough, and just become a 'dumb' bonding-style thing, with no redundancy and other features. Met vriendelijke groet / With kind regards, Bart Van Kerckhove bart@it-ss.be http://www.it-ss.be - "Solid Solutions for your IT needs" "There are 10 kinds of ppl; those who read binary and those who don't" > > Antony Mawer yazmýþ: >> On 22/09/2006 6:58 PM, Özkan KIRIK wrote: >>> Does ng_fec module support Dynamic LACP (802.3ad) protocol ? >>> >>> i have an HP Procurve 5406 switch, i am trying to make a fail over >>> connection between switch and freebsd. >>> Does ng_fec support "Fail over" for links ? >> >> The ng_fec module doesn't support LACP (it would be really nice if it >> did!!!), but you can configure it manually if you've got access to >> the console of the switch. I setup exactly this configuration today >> (although in this case it was for bandwidth aggregation rather than >> fall-over) using an HP Procurve 5308xl. >> >> The procedure went something like this: >> >> 1) First, create a new startup script in /etc/rc.d/ to configure the >> Netgraph interface on startup... this was a quick hack-up, but does >> the job: >> >> ---- begin /etc/rc.d/ngfec ---- >> $ cat /etc/rc.d/ngfec >> #!/bin/sh >> # >> # PROVIDE: ngfec >> # REQUIRE: root >> # BEFORE: netif >> # KEYWORD: nojail >> >> . /etc/rc.subr >> >> name="ngfec" >> start_cmd="ngfec_start" >> stop_cmd=":" >> >> # Netgraph FEC startup script >> ngfec_start() >> { >> echo -n "Configuring netgraph FEC device: " >> ngctl mkpeer fec dummy fec >> ngctl msg fec0: add_iface '"em0"' >> ngctl msg fec0: add_iface '"em1"' >> echo "done." >> } >> >> load_rc_config $name >> run_rc_command "$1" >> >> ---- end of /etc/rc.d/ngfec ---- >> >> >> 2) Configure the new fec0 interface in /etc/rc.conf: >> >> ifconfig_fec0="inet a.b.c.d netmask w.x.y.z" >> >> >> 3) Telnet to the HP switch, and do the following: >> >> i) Type "show trunk" and identify what trunk group names are >> already in use. These will be in the format of "TrkN", eg. >> Trk1,Trk2,... >> >> ii) Identify which ports are to be configured as part of trunk >> (eg. in my case, C1 and C2) >> >> iii) Select the next available trunk group name (eg. Trk7), and >> configure the trunk by typing: >> >> switch# config t >> switch(config)# trunk C1-C2 Trk7 fec >> switch(config)# exit >> >> 4) Once the FreeBSD machine is rebooted, the link should be up.... >> >> >> I'm not sure what the behaviour is when one of the links goes down... >> I don't know if that interface is simply removed from the trunk group >> and the remaining ones continue to operate? >> >> Hope this is useful to others out there, as I had trouble finding any >> good documentation on how to do this :-) I owe thanks to lukem dot >> freebsd at cse dot unsw dot edu dot au for the Netgraph commands for >> getting the FreeBSD fec side of things up and running; the rcNG >> script above is based on the commands he provided me with, put into >> rcNG format so I could integrate it with the boot sequence easily. >> >> Cheers >> Antony >> >> > _______________________________________________ > 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 Fri Sep 22 22:09:37 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 B12FF16A4A0 for ; Fri, 22 Sep 2006 22:09:37 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9777643D45 for ; Fri, 22 Sep 2006 22:09:35 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 57412 invoked from network); 22 Sep 2006 22:12:03 -0000 Received: from opi.flirtbox.ch (HELO [127.0.0.1]) ([62.48.0.50]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 22 Sep 2006 22:12:03 -0000 Message-ID: <45145F1D.8020005@freebsd.org> Date: Sat, 23 Sep 2006 00:09:33 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Andrew Gallatin References: <4511B9B1.2000903@freebsd.org> <17683.63162.919620.114649@grasshopper.cs.duke.edu> In-Reply-To: <17683.63162.919620.114649@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, freebsd-net@freebsd.org, freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 22 Sep 2006 22:09:37 -0000 Andrew Gallatin wrote: > > Between TSO and your sendfile changes, things are looking up! > > Here are some Myri10GbE 1500 byte results from a 1.8GHz UP > FreeBSD/amd64 machine (AMD Athlon(tm) 64 Processor 3000+) sending to a > 2.0GHz SMP Linux/x86_64 machine (AMD Athlon(tm) 64 X2 Dual Core Processor > 3800+) running 26.17.7smp and our 1.1.0 Myri10GE driver (with LRO). > I used a linux receiver because LRO is the only way to receive > standard frames at line rate (without a TOE). > > These tests are all for sendfile of a 10MB file in /var/tmp: > > % netperf242 -Hrome-my -tTCP_SENDFILE -F /var//tmp/zot -T,1 -c -C -- -s393216 You should use -m5M as well. netperf is kinda dumb and does only socket buffer sized sendfile calls whereas sendfile really works best (especially new-sendfile) when it chew on a really big chunk of file without having to return to userland for every ~380k in this case. > The -T,1 is required to force the netserver to use a different core > than the interrupt handler is bound to on the linux machine. BTW, > it would be really nice if FreeBSD supported CPU affinity for processes > and interrupt handlers.. I have a gross version of that in my tree. The kernel itself supports it but it's not yet exposed to userland for manual intervention. > I did a number of runs with TSO and the patch applied and found that > setting the send-side socket buffer size to 393216 gave the best > performance in that case. I used this size for all tests, but it is > possible there is a different sweet spot for other configurations. > Note that linux auto-tunes socket buffer sizes, so I omitted the -- > -s393216 for linux. We're getting there too. First for the send buffer. Again some gross code in my tree. Not really tested yet though. > > Recv Send Send Utilization Service Demand > Socket Socket Message Elapsed Send Recv Send Recv > Size Size Size Time Throughput local remote local remote > bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB > > Without patch: > 87380 393216 393216 10.00 2163.08 100.00 19.35 3.787 1.466 > Without patch + TSO: > 87380 393216 393216 10.00 4367.18 71.54 42.07 1.342 1.578 > With patch: > 87380 393216 393216 10.01 1882.73 86.15 18.43 3.749 1.604 > With patch + TSO: > 87380 393216 393216 10.00 6961.08 47.69 60.11 0.561 1.415 Be a bit careful with the CPU usage figures. The numbers netperf reports differ quite a bit from those reported by time(1) on the high side. And there are some differences in the approach how FreeBSD and Linux do their statistical measurements of user and system time. This doesn't change the throughput number though. But see the -m5M option. New sendfile is really optimized to chew on a large file (larger than the socket buffer size) as it normally happens in reality. > For comparision, if I reboot the sender into RHEL (Linux 2.6.9-11.EL x86_64): > 87380 65536 65536 10.01 9333.00 28.98 75.23 0.254 1.321 > > > The above results are the median result for 5 runs at each setting. How large is the variance between the runs? -- Andre From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 22:48:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0037216A412; Fri, 22 Sep 2006 22:48:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AFD243D55; Fri, 22 Sep 2006 22:48:24 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A7D5646C87; Fri, 22 Sep 2006 18:48:23 -0400 (EDT) Date: Fri, 22 Sep 2006 23:48:23 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andre Oppermann In-Reply-To: <45145F1D.8020005@freebsd.org> Message-ID: <20060922234708.V11343@fledge.watson.org> References: <4511B9B1.2000903@freebsd.org> <17683.63162.919620.114649@grasshopper.cs.duke.edu> <45145F1D.8020005@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: alc@freebsd.org, freebsd-net@freebsd.org, freebsd-current@freebsd.org, tegge@freebsd.org, Andrew Gallatin Subject: Re: Much improved sendfile(2) kernel implementation 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, 22 Sep 2006 22:48:25 -0000 On Sat, 23 Sep 2006, Andre Oppermann wrote: >> Without patch: >> 87380 393216 393216 10.00 2163.08 100.00 19.35 3.787 >> 1.466 Without patch + TSO: >> 87380 393216 393216 10.00 4367.18 71.54 42.07 1.342 >> 1.578 With patch: >> 87380 393216 393216 10.01 1882.73 86.15 18.43 3.749 >> 1.604 With patch + TSO: >> 87380 393216 393216 10.00 6961.08 47.69 60.11 0.561 >> 1.415 The impact of TSO is clearly dramatic, especially when combined with the patch, but I'm a bit concerned by the drop in performance in the patched non-TSO case. For network cards which will always have TSO enabled, this isn't an issue, but do we see a similar affect for drivers without TSO? What can we put this drop down to? Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 23:21:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FAB516A40F for ; Fri, 22 Sep 2006 23:21:18 +0000 (UTC) (envelope-from fbsd-net@mawer.org) Received: from mail-ihug.icp-qv1-irony4.iinet.net.au (ihug-mail.icp-qv1-irony4.iinet.net.au [203.59.1.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 338E943D4C for ; Fri, 22 Sep 2006 23:21:16 +0000 (GMT) (envelope-from fbsd-net@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by mail-ihug.icp-qv1-irony4.iinet.net.au with ESMTP; 23 Sep 2006 07:21:16 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,205,1157299200"; d="scan'208"; a="908085103:sNHT27649978" Message-ID: <45146FA2.8070208@mawer.org> Date: Sat, 23 Sep 2006 09:20:02 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Bart Van Kerckhove References: <4513A5D1.4000604@mersin.edu.tr> <4513AC94.8040609@mawer.org> <45142ED1.1000204@mersin.edu.tr> <00ed01c6de77$8968f770$020b000a@bartwrkstxp> In-Reply-To: <00ed01c6de77$8968f770$020b000a@bartwrkstxp> Content-Type: text/plain; charset=ISO-8859-9; format=flowed Content-Transfer-Encoding: 8bit Cc: =?ISO-8859-9?Q?=D6zkan_KIRIK?= , freebsd-net@freebsd.org Subject: Re: LACP 802.3ad and ng_fec ? 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, 22 Sep 2006 23:21:18 -0000 On 23/09/2006 4:47 AM, Bart Van Kerckhove wrote: > Özkan KIRIK wrote: >> Thanks for your reply, >> >> It seems that HP ProCurve 5400 series doesn't support fec trunking : >> >> hp(config)# trunk A3-a5 trk1 fec >> Invalid input: fec >> >> hp(config)# trunk A3-a5 trk1 ? >> trunk Do not use any protocol to create or maintain >> the trunk. >> lacp Use IEEE 802.1ad Link Aggregation protocol. >> >> hp(config)# >> >> Can ng_fec handshake with switch via "trunk" option instead of "fec" ? > According to HP docs, FEC should "work" with the 'trunk' setting. > It will loose all features tough, and just become a 'dumb' bonding-style > thing, with no redundancy and other features. Yes, I was reading some HP docs yesterday and they implied that they were removing FEC on newer switches in favour of using the IEEE standards-based methods of trunking. I wonder how dissimilar FEC and IEEE LACP are from one another? ie. how much of the code from ng_fec could be used to implement an ng_lacp... --Antony From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 23:36:19 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 42D0B16A40F for ; Fri, 22 Sep 2006 23:36:19 +0000 (UTC) (envelope-from bart@it-ss.be) Received: from piggy.solidweb.be (piggy.web.bru.it-ss.be [195.28.164.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 789EA43D49 for ; Fri, 22 Sep 2006 23:36:18 +0000 (GMT) (envelope-from bart@it-ss.be) Received: from mobilexp (162.160-201-80.adsl-dyn.isp.belgacom.be [80.201.160.162]) (authenticated bits=0) by piggy.solidweb.be (8.13.6/8.13.6) with ESMTP id k8MNaBIi031275; Sat, 23 Sep 2006 01:36:16 +0200 Message-ID: <000c01c6de9f$e5b79d60$de0b000a@mobilexp> From: "Bart Van Kerckhove - mobile" To: "Antony Mawer" References: <4513A5D1.4000604@mersin.edu.tr><4513AC94.8040609@mawer.org> <45142ED1.1000204@mersin.edu.tr><00ed01c6de77$8968f770$020b000a@bartwrkstxp> <45146FA2.8070208@mawer.org> Date: Sat, 23 Sep 2006 01:36:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-9"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Scanned-By: MIMEDefang 2.45 on 195.28.164.224 Cc: freebsd-net@freebsd.org Subject: Re: LACP 802.3ad and ng_fec ? 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, 22 Sep 2006 23:36:19 -0000 >>> Thanks for your reply, >>> >>> It seems that HP ProCurve 5400 series doesn't support fec trunking : >>> >>> hp(config)# trunk A3-a5 trk1 fec >>> Invalid input: fec >>> >>> hp(config)# trunk A3-a5 trk1 ? >>> trunk Do not use any protocol to create or maintain >>> the trunk. >>> lacp Use IEEE 802.1ad Link Aggregation protocol. >>> >>> hp(config)# >>> >>> Can ng_fec handshake with switch via "trunk" option instead of "fec" ? >> According to HP docs, FEC should "work" with the 'trunk' setting. >> It will loose all features tough, and just become a 'dumb' bonding-style >> thing, with no redundancy and other features. > > Yes, I was reading some HP docs yesterday and they implied that they were > removing FEC on newer switches in favour of using the IEEE standards-based > methods of trunking. I can NOT resist taking the bait here: HP has supported these standards for ages. In fact, the cisco-protocols were used to market their stuff as cisco-replacements. They ripped out functionality. IEEE Standards were already supported. Same for their SFP's. Vendor lock-in is a bitch, especially when that means you can't get stuff that was previously possible. (think cwdm gbics, etc) > > I wonder how dissimilar FEC and IEEE LACP are from one another? ie. how > much of the code from ng_fec could be used to implement an ng_lacp... I honestly don't know :-/ I'm very interested in the whole topic though, as we're an all-HP (as in procurve) shop. I do know that will only last 'till the next boxes we buy, HP has let us down the past few years. -Bart (sorry for the ranting) From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 00:28: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 E3FED16A407 for ; Sat, 23 Sep 2006 00:28:41 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 288D243D58 for ; Sat, 23 Sep 2006 00:28:40 +0000 (GMT) (envelope-from jyavenard@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so1365093nfc for ; Fri, 22 Sep 2006 17:28:39 -0700 (PDT) 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=OKY1d7UC5sVmPy9kgR7CFoZ2SexCPFm4mUbjwMo1Wwe4SDqM7mgfmTZq1l3vxMLw4fTF3e9LtzjdvhbADQdoov/dsUFTIj/gYdl5PAIn6amlPplSrmoeEIntA8YooNWmzSLXs27BNf3C9bP45x49351ZkVbq7W6VWJ5b6L2TM3I= Received: by 10.49.41.18 with SMTP id t18mr2729131nfj; Fri, 22 Sep 2006 17:28:39 -0700 (PDT) Received: by 10.49.80.17 with HTTP; Fri, 22 Sep 2006 17:28:39 -0700 (PDT) Message-ID: Date: Sat, 23 Sep 2006 10:28:39 +1000 From: "Jean-Yves Avenard" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Issue with IPFW forward 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, 23 Sep 2006 00:28:42 -0000 Hello I apologize in advance if this is not the right place to ask, in which case could you point me where would be the right place ? I've been trying to use two ADSL connection on the same machine, and that it will answer traffic using the same connection it went through Unfortunately, I can't get it to work. A more accurate description of my system: FreeBSD 6.1 two PPPoE link ifconfig: tun1: flags=3D8051 mtu 1492 inet 1.1.1.1 --> 10.10.10.10 netmask 0xffffffff tun2: flags=3D8051 mtu 1492 inet 2.2.2.2 --> 20.20.20.20 netmask 0xffffffff netstat -rn would give me: Destination Gateway Flags Refs Use Netif Expire default 10.10.10.10 UGS 0 4344 tun1 20.20.20.20 2.2.2.2 UH 0 6 tun2 I then added: ipfw add 10 fwd 20.20.20.20 log ip from 2.2.2.2 to any ipfw add 20 allow ip from any to any if on a remote machine I do: ping 2.2.2.2, nothing comes back however, I can see the IPFW counter increasing while the ping command is running. If I try to ssh to 2.2.2.2, In the log I see: Sep 22 19:08:32 gateway kernel: ipfw: 10 Forward to 20.20.20.20 TCP 2.2.2.2:22 203.214.80.131:38069 out via tun1 As you can see, it is still trying to go through tun1 when I believe it should go through tun2 ! I can ping 20.20.20.20 without issues from the freebsd server, so I believe the static route there is okay. Have I missed something obvious? Thanks for helping me out JY From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 01:05: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 9BDDF16A403 for ; Sat, 23 Sep 2006 01:05:27 +0000 (UTC) (envelope-from prvs=julian=4143c6dd0@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DAEE43D49 for ; Sat, 23 Sep 2006 01:05:27 +0000 (GMT) (envelope-from prvs=julian=4143c6dd0@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 22 Sep 2006 18:05:25 -0700 Message-ID: <45148856.8020109@elischer.org> Date: Fri, 22 Sep 2006 18:05:26 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jean-Yves Avenard References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: Issue with IPFW forward 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, 23 Sep 2006 01:05:27 -0000 Jean-Yves Avenard wrote: > Hello > > I apologize in advance if this is not the right place to ask, in which > case could you point me where would be the right place ? > > > I've been trying to use two ADSL connection on the same machine, and > that it will answer traffic using the same connection it went through > > Unfortunately, I can't get it to work. > > A more accurate description of my system: > > FreeBSD 6.1 > two PPPoE link > > ifconfig: > tun1: flags=8051 mtu 1492 > inet 1.1.1.1 --> 10.10.10.10 netmask 0xffffffff > tun2: flags=8051 mtu 1492 > inet 2.2.2.2 --> 20.20.20.20 netmask 0xffffffff > > netstat -rn would give me: > > Destination Gateway Flags Refs Use Netif Expire > default 10.10.10.10 UGS 0 4344 tun1 > 20.20.20.20 2.2.2.2 UH 0 6 tun2 > > I then added: > ipfw add 10 fwd 20.20.20.20 log ip from 2.2.2.2 to any > ipfw add 20 allow ip from any to any > > if on a remote machine I do: > ping 2.2.2.2, nothing comes back > however, I can see the IPFW counter increasing while the ping command > is running. > > If I try to ssh to 2.2.2.2, In the log I see: > Sep 22 19:08:32 gateway kernel: ipfw: 10 Forward to 20.20.20.20 TCP > 2.2.2.2:22 203.214.80.131:38069 out via tun1 > > As you can see, it is still trying to go through tun1 when I believe > it should go through tun2 ! > > I can ping 20.20.20.20 without issues from the freebsd server, so I > believe the static route there is okay. > > Have I missed something obvious? > Thanks for helping me out there is a stupid option in 6.1 (that I have removed in 6.2) called IPFIREWALL_FORWARD_EXTENDED (check the spelling) if you don't have it you can not forward any packet that has a local address as either the source or destination... See if setting it fixes your problem, in 6.2 you shouldn't have to worry about it (certainly in 7.0) julian > JY > _______________________________________________ > 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 Sat Sep 23 01:47:39 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AA0716A403; Sat, 23 Sep 2006 01:47:39 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04C7C43D45; Sat, 23 Sep 2006 01:47:38 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.6/8.13.6) with ESMTP id k8N1lbVl012325 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Sep 2006 21:47:37 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id k8N1lWQl043880; Fri, 22 Sep 2006 21:47:32 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17684.37427.990749.849229@grasshopper.cs.duke.edu> Date: Fri, 22 Sep 2006 21:47:31 -0400 (EDT) To: Andre Oppermann In-Reply-To: <45145F1D.8020005@freebsd.org> References: <4511B9B1.2000903@freebsd.org> <17683.63162.919620.114649@grasshopper.cs.duke.edu> <45145F1D.8020005@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: alc@freebsd.org, freebsd-net@freebsd.org, freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 23 Sep 2006 01:47:39 -0000 Andre Oppermann writes: > Andrew Gallatin wrote: > > > > Between TSO and your sendfile changes, things are looking up! > > > > Here are some Myri10GbE 1500 byte results from a 1.8GHz UP > > FreeBSD/amd64 machine (AMD Athlon(tm) 64 Processor 3000+) sending to a > > 2.0GHz SMP Linux/x86_64 machine (AMD Athlon(tm) 64 X2 Dual Core Processor > > 3800+) running 26.17.7smp and our 1.1.0 Myri10GE driver (with LRO). > > I used a linux receiver because LRO is the only way to receive > > standard frames at line rate (without a TOE). > > > > These tests are all for sendfile of a 10MB file in /var/tmp: > > > > % netperf242 -Hrome-my -tTCP_SENDFILE -F /var//tmp/zot -T,1 -c -C -- -s393216 > > You should use -m5M as well. netperf is kinda dumb and does only I will try this. > > The -T,1 is required to force the netserver to use a different core > > than the interrupt handler is bound to on the linux machine. BTW, > > it would be really nice if FreeBSD supported CPU affinity for processes > > and interrupt handlers.. > > I have a gross version of that in my tree. The kernel itself supports > it but it's not yet exposed to userland for manual intervention. Sweet. > Be a bit careful with the CPU usage figures. The numbers netperf reports > differ quite a bit from those reported by time(1) on the high side. And > there are some differences in the approach how FreeBSD and Linux do their > statistical measurements of user and system time. This doesn't change the Netperf essentially subtracts idle time from all other time. The numbers I see reported from netperf have historically matched what vmstat says. BTW, I use netperf from svn. I don't use the FreeBSD port. > throughput number though. But see the -m5M option. New sendfile is really > optimized to chew on a large file (larger than the socket buffer size) as > it normally happens in reality. > > > For comparision, if I reboot the sender into RHEL (Linux 2.6.9-11.EL x86_64): > > 87380 65536 65536 10.01 9333.00 28.98 75.23 0.254 1.321 > > > > > > The above results are the median result for 5 runs at each setting. > > How large is the variance between the runs? Much bigger for FreeBSD than for Linux. I think I had one 9.1 and 4 9.3s for linux. I had a 6.2 a 6.5 and 3 around 6.9 for FreeBSD, Drew From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 02:19: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 2283816A40F for ; Sat, 23 Sep 2006 02:19:47 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 706FA43D46 for ; Sat, 23 Sep 2006 02:19:46 +0000 (GMT) (envelope-from jyavenard@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so1375158nfc for ; Fri, 22 Sep 2006 19:19:45 -0700 (PDT) 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=KGpYV3xWV9iJJugtU6Rlemqvxp3XpTboFIrw9VXAfiFX7Zc1vif4tR8HOu8iDrr0p/0SfnnzXelfLQfH9x57QA2s5bMnTTFg/vtzsqelHWbjiFWUArKF+RFrm2doBKz6qt47IJxx63OiIBQxcSTtyOdA9eCXKo2T81Xu/+1AIy0= Received: by 10.49.55.13 with SMTP id h13mr2828150nfk; Fri, 22 Sep 2006 19:19:45 -0700 (PDT) Received: by 10.49.80.17 with HTTP; Fri, 22 Sep 2006 19:19:44 -0700 (PDT) Message-ID: Date: Sat, 23 Sep 2006 12:19:44 +1000 From: "Jean-Yves Avenard" To: "Julian Elischer" In-Reply-To: <45148856.8020109@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45148856.8020109@elischer.org> Cc: freebsd-net@freebsd.org Subject: Re: Issue with IPFW forward 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, 23 Sep 2006 02:19:47 -0000 Hi On 9/23/06, Julian Elischer wrote: > there is a stupid option in 6.1 (that I have removed in 6.2) > called IPFIREWALL_FORWARD_EXTENDED > (check the spelling) > if you don't have it you can not forward any packet that has a local > address as either > the source or destination... See if setting it fixes your problem, > in 6.2 you shouldn't have to worry about it (certainly in 7.0) Thanks, I will try this immediately. Will let you know if that fixes the problem Jean-Yves From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 02:29:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA5FF16A47B for ; Sat, 23 Sep 2006 02:29:25 +0000 (UTC) (envelope-from brad@comstyle.com) Received: from mail.comstyle.com (toronto-hs-216-138-195-228.s-ip.magma.ca [216.138.195.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B55343D45 for ; Sat, 23 Sep 2006 02:29:25 +0000 (GMT) (envelope-from brad@comstyle.com) Received: from blar.home.comstyle.com (blar.home.comstyle.com [IPv6:2001:4830:1216:1::3]) by fubar.home.comstyle.com (Postfix) with ESMTP id 7B7DCA2E73 for ; Fri, 22 Sep 2006 22:29:24 -0400 (EDT) Received: by blar.home.comstyle.com (Postfix, from userid 1000) id F111AD35F0; Fri, 22 Sep 2006 22:29:23 -0400 (EDT) Date: Fri, 22 Sep 2006 22:29:23 -0400 From: Brad To: freebsd-net@freebsd.org Message-ID: <20060923022923.GA20553@blar.home.comstyle.com> References: <4513A5D1.4000604@mersin.edu.tr> <4513AC94.8040609@mawer.org> <45142ED1.1000204@mersin.edu.tr> <00ed01c6de77$8968f770$020b000a@bartwrkstxp> <45146FA2.8070208@mawer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45146FA2.8070208@mawer.org> User-Agent: Mutt/1.4.2.2i Subject: Re: LACP 802.3ad and ng_fec ? 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, 23 Sep 2006 02:29:26 -0000 On Sat, Sep 23, 2006 at 09:20:02AM +1000, Antony Mawer wrote: > On 23/09/2006 4:47 AM, Bart Van Kerckhove wrote: > >?zkan KIRIK wrote: > >>Thanks for your reply, > >> > >>It seems that HP ProCurve 5400 series doesn't support fec trunking : > >> > >>hp(config)# trunk A3-a5 trk1 fec > >>Invalid input: fec > >> > >>hp(config)# trunk A3-a5 trk1 ? > >> trunk Do not use any protocol to create or maintain > >>the trunk. > >> lacp Use IEEE 802.1ad Link Aggregation protocol. > >> > >>hp(config)# > >> > >>Can ng_fec handshake with switch via "trunk" option instead of "fec" ? > >According to HP docs, FEC should "work" with the 'trunk' setting. > >It will loose all features tough, and just become a 'dumb' bonding-style > >thing, with no redundancy and other features. > > Yes, I was reading some HP docs yesterday and they implied that they > were removing FEC on newer switches in favour of using the IEEE > standards-based methods of trunking. even Cisco doesn't support FEC on their own switches with some of the newer gear. From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 07:38:38 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4679716A40F; Sat, 23 Sep 2006 07:38:38 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id A0BE543D45; Sat, 23 Sep 2006 07:38:36 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 23 Sep 2006 08:38:35 +0100 (BST) Date: Sat, 23 Sep 2006 08:38:33 +0100 From: David Malone To: Robert Watson Message-ID: <20060923073833.GA10269@walton.maths.tcd.ie> References: <4511B9B1.2000903@freebsd.org> <17683.63162.919620.114649@grasshopper.cs.duke.edu> <45145F1D.8020005@freebsd.org> <20060922234708.V11343@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060922234708.V11343@fledge.watson.org> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: Andre Oppermann , Andrew Gallatin , alc@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-current@FreeBSD.org, tegge@FreeBSD.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 23 Sep 2006 07:38:38 -0000 On Fri, Sep 22, 2006 at 11:48:23PM +0100, Robert Watson wrote: > The impact of TSO is clearly dramatic, especially when combined with the > patch, but I'm a bit concerned by the drop in performance in the patched > non-TSO case. For network cards which will always have TSO enabled, this > isn't an issue, but do we see a similar affect for drivers without TSO? > What can we put this drop down to? We probably also need to make sure that any performance increase in TSO isn't due to us getting TCP congestion control wrong. I think in Linux they had problems when they first introduced TSO because TCP was advancing the congestion window by a TSO-sized chunk instead of a wire packet. OTOH, I think Andre and Drew's tests are low-latency, so congestion control isn't likely to be playing a big role, so the improvements are unlikely to be due to this. David. From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 09:16:24 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7B2616A8FC for ; Sat, 23 Sep 2006 09:16:24 +0000 (UTC) (envelope-from ezzjqijguql@est.it) Received: from est.it (cjm79.neoplus.adsl.tpnet.pl [83.31.62.79]) by mx1.FreeBSD.org (Postfix) with SMTP id DD69E43D5C for ; Sat, 23 Sep 2006 09:16:23 +0000 (GMT) (envelope-from ezzjqijguql@est.it) Date: Sat, 23 Sep 2006 11:16:23 +0100 From: "travis marijn" To: Cc: Message-Id: <9017012741.USRpET-491028-413344@est.it> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Subject: your pr man is back 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, 23 Sep 2006 09:16:24 -0000 Company- A L L I A N C E E N T E R P R I S E Symbol - A E T R (Pink Sheets) C u r r e n t P r i c e: $ 0.48 Estimated Target - $ 2.00 + S T R O N G B U Y AE TR is undergoing a massive promotion and NOW is the time to get in. Add this Gem to your Watch list. Watch it Start a run monday About A L L I A N C E E N T E R P R I S E (.TaeCorp.) TaeCorp's vision is to be the recognized leader in providing Aerial Detection Systems including global de-mining, clearing a path to a safer planet for all humankind. TaeCorp's mission is to reclaim lands around the globe embedded with landmines that victimize countries and their stakeholders. N E W S TaeCorp Appoints TAM Oilfield Services as Representative in Sudan The A L L I A N C E E N T E R P R I S E Corporation ("TaeCorp") (AETR - News) is pleased to announce that it has appointed TAM Oilfield Services ("TAM"), of Khartoum, the capital of Sudan, as its representative to introduce and establish business relationships with oil and related companies interested in TaeCorp's unique landmine detection, location, mapping and removal systems and services. TAM Oilfield Services, established in 2001 under the laws and regulations of the Sudan government, has forged strong relationships with the leading petroleum companies that operate in the Sudan. "TAM's experience in the petroleum field, both with government and operating companies, will allow TaeCorp to 0ffer its services more efficiently and effectively and we are very pleased to have TAM join our team," says Ralph Proceviat, CFO of TaeCorp. Read more A C T N O W on this great news and get in before the move starts. Where man is not nature is barren. Still waters run deep. Sitting on the fence. Spring rain, Fall gold. Shit end of the stick. Put off the scent. You throw filth on the living and flowers on the dead.Pin a rose on your nose. When you get lemons, make lemonade.(When life gives you scraps make quilts.) Sly as a fox. Watered down. She's a mother hen. Raking it in. What on earth? You can lead a horse to water but you can't make him drink. Put that in your pipe and smoke it. You can't teach an old dog new tricks. Stand your ground. Spring to mind. From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 10:13: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 4CCC116A403 for ; Sat, 23 Sep 2006 10:13:00 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E68DB43D5A for ; Sat, 23 Sep 2006 10:12:57 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 61869 invoked from network); 23 Sep 2006 10:15:20 -0000 Received: from opi.flirtbox.ch (HELO [127.0.0.1]) ([62.48.0.50]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 23 Sep 2006 10:15:20 -0000 Message-ID: <451508A7.8020209@freebsd.org> Date: Sat, 23 Sep 2006 12:12:55 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Robert Watson References: <4511B9B1.2000903@freebsd.org> <17683.63162.919620.114649@grasshopper.cs.duke.edu> <45145F1D.8020005@freebsd.org> <20060922234708.V11343@fledge.watson.org> In-Reply-To: <20060922234708.V11343@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, freebsd-net@freebsd.org, freebsd-current@freebsd.org, tegge@freebsd.org, Andrew Gallatin Subject: Re: Much improved sendfile(2) kernel implementation 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, 23 Sep 2006 10:13:00 -0000 Robert Watson wrote: > > On Sat, 23 Sep 2006, Andre Oppermann wrote: > >>> Without patch: >>> 87380 393216 393216 10.00 2163.08 100.00 19.35 3.787 >>> 1.466 Without patch + TSO: >>> 87380 393216 393216 10.00 4367.18 71.54 42.07 1.342 >>> 1.578 With patch: >>> 87380 393216 393216 10.01 1882.73 86.15 18.43 3.749 >>> 1.604 With patch + TSO: >>> 87380 393216 393216 10.00 6961.08 47.69 60.11 0.561 >>> 1.415 > > The impact of TSO is clearly dramatic, especially when combined with the > patch, but I'm a bit concerned by the drop in performance in the patched > non-TSO case. For network cards which will always have TSO enabled, > this isn't an issue, but do we see a similar affect for drivers without > TSO? What can we put this drop down to? If you look at my GigE numbers there is no drop for the new-sendfile w/o TSO case. In this 10Gig test the drop is really and artifact of how the whole setup and the way netperf makes use of the sendfile call. Internally new-sendfile waits until 50% of the socket buffer are free to be bulk filled again. This value can be modified by setting a low watermark on the send socket buffer. Netperf does buffer sized sendfile invocations and this is very timing critical with 10G. Which gives this picture: call sendfile(380K) -> fill socket buffer -> wait -> fill rest -> return -> call sendfile(380K) ... Not to mention all the additional work tcp_output() has to do w/o TSO. Especially with large buffers it has to loop over the mbuf chain for each packet to find out where to start copying. And besides there is no point in having a non-TSO capable interface at above 1-2Gbit. Not even Linux can keep up there. -- Andre From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 10:20: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 0A93D16A415 for ; Sat, 23 Sep 2006 10:20:03 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A5DE43D77 for ; Sat, 23 Sep 2006 10:20:02 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 62209 invoked from network); 23 Sep 2006 10:22:25 -0000 Received: from opi.flirtbox.ch (HELO [127.0.0.1]) ([62.48.0.50]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 23 Sep 2006 10:22:25 -0000 Message-ID: <45150A51.8080501@freebsd.org> Date: Sat, 23 Sep 2006 12:20:01 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: David Malone References: <4511B9B1.2000903@freebsd.org> <17683.63162.919620.114649@grasshopper.cs.duke.edu> <45145F1D.8020005@freebsd.org> <20060922234708.V11343@fledge.watson.org> <20060923073833.GA10269@walton.maths.tcd.ie> In-Reply-To: <20060923073833.GA10269@walton.maths.tcd.ie> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Gallatin , alc@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-current@FreeBSD.org, Robert Watson , tegge@FreeBSD.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 23 Sep 2006 10:20:04 -0000 David Malone wrote: > On Fri, Sep 22, 2006 at 11:48:23PM +0100, Robert Watson wrote: >> The impact of TSO is clearly dramatic, especially when combined with the >> patch, but I'm a bit concerned by the drop in performance in the patched >> non-TSO case. For network cards which will always have TSO enabled, this >> isn't an issue, but do we see a similar affect for drivers without TSO? >> What can we put this drop down to? > > We probably also need to make sure that any performance increase > in TSO isn't due to us getting TCP congestion control wrong. I think > in Linux they had problems when they first introduced TSO because > TCP was advancing the congestion window by a TSO-sized chunk instead > of a wire packet. OTOH, I think Andre and Drew's tests are low-latency, > so congestion control isn't likely to be playing a big role, so the > improvements are unlikely to be due to this. The congestion window is increased based on the ACK's received. TSO is only done on the send side and only up to the current congestion window. I have been careful not to get any changes in congestion control behavior with TSO. (Which does not mean that there may be other bugs lurking in our congestion control.) -- Andre From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 14:28:44 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 7005616A403; Sat, 23 Sep 2006 14:28:44 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id BF77B43D7E; Sat, 23 Sep 2006 14:28:42 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 23 Sep 2006 15:28:41 +0100 (BST) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by walton.maths.tcd.ie with SMTP id ; 23 Sep 2006 15:28:37 +0100 (BST) To: Andre Oppermann In-reply-to: Your message of "Sat, 23 Sep 2006 12:20:01 +0200." <45150A51.8080501@freebsd.org> X-Request-Do: Date: Sat, 23 Sep 2006 15:28:36 +0100 From: David Malone Message-ID: <200609231528.aa12963@walton.maths.tcd.ie> Cc: Andrew Gallatin , alc@freebsd.org, freebsd-net@freebsd.org, freebsd-current@freebsd.org, Robert Watson , tegge@freebsd.org Subject: Re: Much improved sendfile(2) kernel implementation 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, 23 Sep 2006 14:28:44 -0000 > The congestion window is increased based on the ACK's received. TSO > is only done on the send side and only up to the current congestion > window. I have been careful not to get any changes in congestion > control behavior with TSO. (Which does not mean that there may be > other bugs lurking in our congestion control.) I think the reason this happened in Linux was because thw congestion window is counted in segments, which were now TSO sized. You'd send 1 TSO sized segment, get back (say) 10 ACKs because of segmentation and increase the window size by 10*TSO_SEG_SIZE/cwnd insead of 10*REAL_MSS/cwnd. We're unlikely to have exactly the same bug, because we count cwnd in bytes, but it doesn't rule out haveing other unexpected/subtle interactions (like higher varience of RTT esitmation - I guess all packets in a TSO segment are now sent with the same timestamp?). David. From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 15:02:25 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5864716A407; Sat, 23 Sep 2006 15:02:25 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14DB643D53; Sat, 23 Sep 2006 15:02:25 +0000 (GMT) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8NF2OLn032229; Sat, 23 Sep 2006 15:02:24 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8NF2O5g032225; Sat, 23 Sep 2006 15:02:24 GMT (envelope-from bms) Date: Sat, 23 Sep 2006 15:02:24 GMT From: Bruce M Simpson Message-Id: <200609231502.k8NF2O5g032225@freefall.freebsd.org> To: delphij@163.com, bms@FreeBSD.org, bms@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: bin/41647: ifconfig(8) doesn't accept lladdr along with inet address family 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, 23 Sep 2006 15:02:25 -0000 Synopsis: ifconfig(8) doesn't accept lladdr along with inet address family State-Changed-From-To: analyzed->suspended State-Changed-By: bms State-Changed-When: Sat Sep 23 15:00:03 UTC 2006 State-Changed-Why: Not a serious problem. These limitations can be worked around e.g. by using /etc/start_if. scripts to set the ethernet addresses. Responsible-Changed-From-To: bms->freebsd-net Responsible-Changed-By: bms Responsible-Changed-When: Sat Sep 23 15:00:03 UTC 2006 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=41647 From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 16:29:08 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 218B816A403; Sat, 23 Sep 2006 16:29:08 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB8D843D5E; Sat, 23 Sep 2006 16:29:07 +0000 (GMT) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8NGT7tr038482; Sat, 23 Sep 2006 16:29:07 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8NGT7Gl038478; Sat, 23 Sep 2006 16:29:07 GMT (envelope-from bms) Date: Sat, 23 Sep 2006 16:29:07 GMT From: Bruce M Simpson Message-Id: <200609231629.k8NGT7Gl038478@freefall.freebsd.org> To: bms@FreeBSD.org, bms@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/56233: IPsec tunnel (ESP) over IPv6: MTU computation is wrong 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, 23 Sep 2006 16:29:08 -0000 Synopsis: IPsec tunnel (ESP) over IPv6: MTU computation is wrong Responsible-Changed-From-To: bms->freebsd-net Responsible-Changed-By: bms Responsible-Changed-When: Sat Sep 23 16:28:40 UTC 2006 Responsible-Changed-Why: I must focus on more specific areas. http://www.freebsd.org/cgi/query-pr.cgi?pr=56233 From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 16:29:31 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AC1416A412; Sat, 23 Sep 2006 16:29:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E98143D66; Sat, 23 Sep 2006 16:29:30 +0000 (GMT) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8NGTUJl038557; Sat, 23 Sep 2006 16:29:30 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8NGTTIp038553; Sat, 23 Sep 2006 16:29:29 GMT (envelope-from bms) Date: Sat, 23 Sep 2006 16:29:29 GMT From: Bruce M Simpson Message-Id: <200609231629.k8NGTTIp038553@freefall.freebsd.org> To: bms@FreeBSD.org, bms@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/65616: IPSEC can't detunnel GRE packets after real ESP encryption 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, 23 Sep 2006 16:29:31 -0000 Synopsis: IPSEC can't detunnel GRE packets after real ESP encryption Responsible-Changed-From-To: bms->freebsd-net Responsible-Changed-By: bms Responsible-Changed-When: Sat Sep 23 16:29:17 UTC 2006 Responsible-Changed-Why: I must focus on more specific areas. http://www.freebsd.org/cgi/query-pr.cgi?pr=65616 From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 17:37:26 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EF7016A577; Sat, 23 Sep 2006 17:37:26 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8A3743D4C; Sat, 23 Sep 2006 17:37:25 +0000 (GMT) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8NHbPKT046674; Sat, 23 Sep 2006 17:37:25 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8NHbPkF046670; Sat, 23 Sep 2006 17:37:25 GMT (envelope-from bms) Date: Sat, 23 Sep 2006 17:37:25 GMT From: Bruce M Simpson Message-Id: <200609231737.k8NHbPkF046670@freefall.freebsd.org> To: bms@FreeBSD.org, bms@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/38554: changing interface ipaddress doesn't seem to work 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, 23 Sep 2006 17:37:26 -0000 Synopsis: changing interface ipaddress doesn't seem to work Responsible-Changed-From-To: bms->freebsd-net Responsible-Changed-By: bms Responsible-Changed-When: Sat Sep 23 17:36:57 UTC 2006 Responsible-Changed-Why: Back to the world for you, but not after actually doing some work on it... http://www.freebsd.org/cgi/query-pr.cgi?pr=38554 From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 17:39:06 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 568DD16A407; Sat, 23 Sep 2006 17:39:06 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13E5443D53; Sat, 23 Sep 2006 17:39:06 +0000 (GMT) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8NHd52c046809; Sat, 23 Sep 2006 17:39:05 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8NHd5Rg046805; Sat, 23 Sep 2006 17:39:05 GMT (envelope-from bms) Date: Sat, 23 Sep 2006 17:39:05 GMT From: Bruce M Simpson Message-Id: <200609231739.k8NHd5Rg046805@freefall.freebsd.org> To: cwasser@shaw.ca, bms@FreeBSD.org, bms@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/39937: ipstealth issue 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, 23 Sep 2006 17:39:06 -0000 Synopsis: ipstealth issue State-Changed-From-To: analyzed->suspended State-Changed-By: bms State-Changed-When: Sat Sep 23 17:38:49 UTC 2006 State-Changed-Why: Back to the free pool for you. Responsible-Changed-From-To: bms->freebsd-net Responsible-Changed-By: bms Responsible-Changed-When: Sat Sep 23 17:38:49 UTC 2006 Responsible-Changed-Why: Back to the free pool for you. http://www.freebsd.org/cgi/query-pr.cgi?pr=39937 From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 17:40:25 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B206416A403 for ; Sat, 23 Sep 2006 17:40:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E45043D45 for ; Sat, 23 Sep 2006 17:40:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8NHeOSA046883 for ; Sat, 23 Sep 2006 17:40:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8NHeOX0046882; Sat, 23 Sep 2006 17:40:24 GMT (envelope-from gnats) Date: Sat, 23 Sep 2006 17:40:24 GMT Message-Id: <200609231740.k8NHeOX0046882@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Bruce M Simpson Cc: Subject: Re: kern/38554: changing interface ipaddress doesn't seem to work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce M Simpson List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Sep 2006 17:40:25 -0000 The following reply was made to PR kern/38554; it has been noted by GNATS. From: Bruce M Simpson To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/38554: changing interface ipaddress doesn't seem to work Date: Sat, 23 Sep 2006 18:35:50 +0100 This is a multi-part message in MIME format. --------------030000070707080504040106 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Before I suspend my work on this PR, here's a diff I pulled from trying to port the changes to today's CURRENT. The patch doesn't work but haven't tested exhaustively. Need to focus on other things. --------------030000070707080504040106 Content-Type: text/x-patch; name="archie-locia-20060923.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="archie-locia-20060923.diff" ==== //depot/user/bms/nethead/sys/netinet/in.c#1 - /home/bms/fp4/nethead/sys/netinet/in.c ==== --- /tmp/tmp.23928.0 Sat Sep 23 18:32:59 2006 +++ /home/bms/fp4/nethead/sys/netinet/in.c Sat Sep 23 17:37:13 2006 @@ -459,6 +459,11 @@ * a routing process they will come back. */ in_ifadown(&ia->ia_ifa, 1); + /* + * Mark the interface address as no longer valid. + * Sockets that are bound to it should notice. + */ + ia->ia_ifa.ifa_flags |= RTF_REJECT; EVENTHANDLER_INVOKE(ifaddr_event, ifp); error = 0; break; ==== //depot/user/bms/nethead/sys/netinet/in_pcb.c#1 - /home/bms/fp4/nethead/sys/netinet/in_pcb.c ==== --- /tmp/tmp.23928.1 Sat Sep 23 18:32:59 2006 +++ /home/bms/fp4/nethead/sys/netinet/in_pcb.c Sat Sep 23 18:02:08 2006 @@ -238,14 +238,17 @@ anonport = inp->inp_lport == 0 && (nam == NULL || ((struct sockaddr_in *)nam)->sin_port == 0); error = in_pcbbind_setup(inp, nam, &inp->inp_laddr.s_addr, - &inp->inp_lport, cred); + &inp->inp_lport, &inp->inp_locia, cred); if (error) return (error); if (in_pcbinshash(inp) != 0) { inp->inp_laddr.s_addr = INADDR_ANY; inp->inp_lport = 0; + inp->inp_locia = NULL; return (EAGAIN); } + if (inp->inp_locia != NULL) + IFAREF(&inp->inp_locia->ia_ifa); if (anonport) inp->inp_flags |= INP_ANONPORT; return (0); @@ -262,12 +265,13 @@ */ int in_pcbbind_setup(struct inpcb *inp, struct sockaddr *nam, in_addr_t *laddrp, - u_short *lportp, struct ucred *cred) + u_short *lportp, struct in_ifaddr **iap, struct ucred *cred) { struct socket *so = inp->inp_socket; unsigned short *lastport; struct sockaddr_in *sin; struct inpcbinfo *pcbinfo = inp->inp_pcbinfo; + struct in_ifaddr *ia = NULL; struct in_addr laddr; u_short lport = 0; int wild = 0, reuseport = (so->so_options & SO_REUSEPORT); @@ -319,7 +323,8 @@ } else if (sin->sin_addr.s_addr != INADDR_ANY) { sin->sin_port = 0; /* yech... */ bzero(&sin->sin_zero, sizeof(sin->sin_zero)); - if (ifa_ifwithaddr((struct sockaddr *)sin) == 0) + if ((ia = (struct in_ifaddr *)ifa_ifwithaddr( + (struct sockaddr *)sin)) == 0) return (EADDRNOTAVAIL); } laddr = sin->sin_addr; @@ -478,6 +483,8 @@ return (EINVAL); *laddrp = laddr.s_addr; *lportp = lport; + if (iap != NULL) + *iap = ia; return (0); } @@ -490,6 +497,7 @@ int in_pcbconnect(struct inpcb *inp, struct sockaddr *nam, struct ucred *cred) { + struct in_ifaddr *locia; u_short lport, fport; in_addr_t laddr, faddr; int anonport, error; @@ -501,7 +509,7 @@ laddr = inp->inp_laddr.s_addr; anonport = (lport == 0); error = in_pcbconnect_setup(inp, nam, &laddr, &lport, &faddr, &fport, - NULL, cred); + NULL, &locia, cred); if (error) return (error); @@ -519,6 +527,9 @@ /* Commit the remaining changes. */ inp->inp_lport = lport; inp->inp_laddr.s_addr = laddr; + inp->inp_locia = locia; + if (inp->inp_locia != NULL) + IFAREF(&inp->inp_locia->ia_ifa); inp->inp_faddr.s_addr = faddr; inp->inp_fport = fport; in_pcbrehash(inp); @@ -536,7 +547,9 @@ * On entry, *laddrp and *lportp should contain the current local * address and port for the PCB; these are updated to the values * that should be placed in inp_laddr and inp_lport to complete - * the connect. + * the connect. If iap is not NULL, *iap is set to the interface + * address corresponding to *laddrp, if any, but no new reference + * to it has been added. * * On success, *faddrp and *fportp will be set to the remote address * and port. These are not updated in the error case. @@ -549,7 +562,7 @@ int in_pcbconnect_setup(struct inpcb *inp, struct sockaddr *nam, in_addr_t *laddrp, u_short *lportp, in_addr_t *faddrp, u_short *fportp, - struct inpcb **oinpp, struct ucred *cred) + struct inpcb **oinpp, struct in_ifaddr **iap, struct ucred *cred) { struct sockaddr_in *sin = (struct sockaddr_in *)nam; struct in_ifaddr *ia; @@ -560,6 +573,7 @@ u_short lport, fport; int error; + ia = NULL; INP_INFO_WLOCK_ASSERT(inp->inp_pcbinfo); INP_LOCK_ASSERT(inp); @@ -582,7 +596,7 @@ sa.sin_len = sizeof(sa); sa.sin_family = AF_INET; error = in_pcbbind_setup(inp, (struct sockaddr *)&sa, - &laddr.s_addr, &lport, cred); + &laddr.s_addr, &lport, &ia, cred); if (error) return (error); } @@ -664,7 +678,7 @@ } if (lport == 0) { error = in_pcbbind_setup(inp, NULL, &laddr.s_addr, &lport, - cred); + &ia, cred); if (error) return (error); } @@ -672,6 +686,8 @@ *lportp = lport; *faddrp = faddr.s_addr; *fportp = fport; + if (iap != NULL) + *iap = ia; return (0); } @@ -720,6 +736,8 @@ #endif /*IPSEC*/ inp->inp_gencnt = ++ipi->ipi_gencnt; in_pcbremlists(inp); + if (inp->inp_locia != NULL) + IFAFREE(&inp->inp_locia->ia_ifa); if (inp->inp_options) (void)m_free(inp->inp_options); ip_freemoptions(inp->inp_moptions); ==== //depot/user/bms/nethead/sys/netinet/in_pcb.h#1 - /home/bms/fp4/nethead/sys/netinet/in_pcb.h ==== --- /tmp/tmp.23928.2 Sat Sep 23 18:32:59 2006 +++ /home/bms/fp4/nethead/sys/netinet/in_pcb.h Sat Sep 23 17:46:41 2006 @@ -71,6 +71,7 @@ struct in_endpoints { u_int16_t ie_fport; /* foreign port */ u_int16_t ie_lport; /* local port */ + struct in_ifaddr *ie_locia; /* locally bound address */ /* protocol dependent part, local and foreign addr */ union { /* foreign host table entry */ @@ -102,6 +103,7 @@ #define inc_isipv6 inc_flags /* temp compatability */ #define inc_fport inc_ie.ie_fport #define inc_lport inc_ie.ie_lport +#define inc_locia inc_ie.ie_locia #define inc_faddr inc_ie.ie_faddr #define inc_laddr inc_ie.ie_laddr #define inc6_faddr inc_ie.ie6_faddr @@ -145,6 +147,7 @@ } inp_depend4; #define inp_fport inp_inc.inc_fport #define inp_lport inp_inc.inc_lport +#define inp_locia inp_inc.inc_locia #define inp_faddr inp_inc.inc_faddr #define inp_laddr inp_inc.inc_laddr #define inp_ip_tos inp_depend4.inp4_ip_tos @@ -332,6 +335,8 @@ #define INP_CHECK_SOCKAF(so, af) (INP_SOCKAF(so) == af) #ifdef _KERNEL +struct in_ifaddr; + extern int ipport_reservedhigh; extern int ipport_reservedlow; extern int ipport_lowfirstauto; @@ -346,11 +351,11 @@ int in_pcballoc(struct socket *, struct inpcbinfo *); int in_pcbbind(struct inpcb *, struct sockaddr *, struct ucred *); int in_pcbbind_setup(struct inpcb *, struct sockaddr *, in_addr_t *, - u_short *, struct ucred *); + u_short *, struct in_ifaddr **, struct ucred *); int in_pcbconnect(struct inpcb *, struct sockaddr *, struct ucred *); int in_pcbconnect_setup(struct inpcb *, struct sockaddr *, in_addr_t *, u_short *, in_addr_t *, u_short *, struct inpcb **, - struct ucred *); + struct in_ifaddr **, struct ucred *); void in_pcbdetach(struct inpcb *); void in_pcbdisconnect(struct inpcb *); void in_pcbdrop(struct inpcb *); ==== //depot/user/bms/nethead/sys/netinet/tcp_output.c#1 - /home/bms/fp4/nethead/sys/netinet/tcp_output.c ==== --- /tmp/tmp.23928.3 Sat Sep 23 18:32:59 2006 +++ /home/bms/fp4/nethead/sys/netinet/tcp_output.c Sat Sep 23 17:47:35 2006 @@ -51,12 +51,15 @@ #include #include +#include +#include #include #include #include #include #include +#include #include #ifdef INET6 #include @@ -872,6 +875,16 @@ ipov = (struct ipovly *)ip; th = (struct tcphdr *)(ip + 1); tcpip_fillheaders(tp->t_inpcb, ip, th); + } + + /* + * Check that our local (source) IP address is still valid. + */ + if (tp->t_inpcb->inp_locia != NULL + && (tp->t_inpcb->inp_locia->ia_ifa.ifa_flags & RTF_REJECT) != 0) { + error = EADDRNOTAVAIL; + m_freem(m); + goto out; } /* ==== //depot/user/bms/nethead/sys/netinet/tcp_usrreq.c#1 - /home/bms/fp4/nethead/sys/netinet/tcp_usrreq.c ==== --- /tmp/tmp.23928.4 Sat Sep 23 18:33:00 2006 +++ /home/bms/fp4/nethead/sys/netinet/tcp_usrreq.c Sat Sep 23 17:53:09 2006 @@ -1102,6 +1102,7 @@ { struct inpcb *inp = tp->t_inpcb, *oinp; struct socket *so = inp->inp_socket; + struct in_ifaddr *locia; struct in_addr laddr; u_short lport; int error; @@ -1122,13 +1123,20 @@ */ laddr = inp->inp_laddr; lport = inp->inp_lport; + locia = inp->inp_locia; error = in_pcbconnect_setup(inp, nam, &laddr.s_addr, &lport, - &inp->inp_faddr.s_addr, &inp->inp_fport, &oinp, td->td_ucred); + &inp->inp_faddr.s_addr, &inp->inp_fport, &oinp, &locia, + td->td_ucred); if (error && oinp == NULL) return error; if (oinp) return EADDRINUSE; inp->inp_laddr = laddr; + if (inp->inp_locia != NULL) + IFAFREE(&inp->inp_locia->ia_ifa); + inp->inp_locia = locia; + if (inp->inp_locia != NULL) + IFAREF(&inp->inp_locia->ia_ifa); in_pcbrehash(inp); /* Compute window scaling to request. */ ==== //depot/user/bms/nethead/sys/netinet/udp_usrreq.c#1 - /home/bms/fp4/nethead/sys/netinet/udp_usrreq.c ==== --- /tmp/tmp.23928.5 Sat Sep 23 18:33:00 2006 +++ /home/bms/fp4/nethead/sys/netinet/udp_usrreq.c Sat Sep 23 17:51:24 2006 @@ -724,6 +724,7 @@ { register struct udpiphdr *ui; register int len = m->m_pkthdr.len; + struct in_ifaddr *locia; struct in_addr faddr, laddr; struct cmsghdr *cm; struct sockaddr_in *sin, src; @@ -809,13 +810,14 @@ laddr = inp->inp_laddr; lport = inp->inp_lport; + locia = inp->inp_locia; if (src.sin_addr.s_addr != INADDR_ANY) { if (lport == 0) { error = EINVAL; goto release; } error = in_pcbbind_setup(inp, (struct sockaddr *)&src, - &laddr.s_addr, &lport, td->td_ucred); + &laddr.s_addr, &lport, &locia, td->td_ucred); if (error) goto release; } @@ -829,7 +831,7 @@ goto release; } error = in_pcbconnect_setup(inp, addr, &laddr.s_addr, &lport, - &faddr.s_addr, &fport, NULL, td->td_ucred); + &faddr.s_addr, &fport, NULL, &locia, td->td_ucred); if (error) goto release; @@ -859,6 +861,14 @@ } /* + * Check that the local (source) IP address is valid. + */ + if (locia != NULL && (locia->ia_ifa.ifa_flags & RTF_REJECT) != 0) { + error = EADDRNOTAVAIL; + goto release; + } + + /* * Calculate data length and get a mbuf for UDP, IP, and possible * link-layer headers. Immediate slide the data pointer back forward * since we won't use that space at this layer. @@ -1088,6 +1098,10 @@ in_pcbdisconnect(inp); inp->inp_laddr.s_addr = INADDR_ANY; + if (inp->inp_locia != NULL) { + IFAFREE(&inp->inp_locia->ia_ifa); + inp->inp_locia = NULL; + } SOCK_LOCK(so); so->so_state &= ~SS_ISCONNECTED; /* XXX */ SOCK_UNLOCK(so); --------------030000070707080504040106-- From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 20:47:38 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5851A16A403 for ; Sat, 23 Sep 2006 20:47:38 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07B6943D78 for ; Sat, 23 Sep 2006 20:47:33 +0000 (GMT) (envelope-from bms@incunabulum.net) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id ADC00DA96B4 for ; Sat, 23 Sep 2006 16:47:31 -0400 (EDT) Received: from heartbeat1.internal ([10.202.2.160]) by frontend3.internal (MEProxy); Sat, 23 Sep 2006 16:47:33 -0400 X-Sasl-enc: D1ahrZSWzUqmmBNrKBfTWgJi+K4sxyQb8+zrh9T3OyEm 1159044453 Received: from [192.168.123.18] (82-35-114-57.cable.ubr07.dals.blueyonder.co.uk [82.35.114.57]) by mail.messagingengine.com (Postfix) with ESMTP id 31518704D for ; Sat, 23 Sep 2006 16:47:33 -0400 (EDT) Message-ID: <45159D63.2090108@incunabulum.net> Date: Sat, 23 Sep 2006 21:47:31 +0100 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.5 (X11/20060825) MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: De-orbitting tcpslice 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, 23 Sep 2006 20:47:38 -0000 We have tcpslice maintained in ports. We have ancient tcpslice in base system. We have PRs about it. I'd like to nuke it in HEAD. How does everyone else feel about that before I go off and do it? BMS From owner-freebsd-net@FreeBSD.ORG Sat Sep 23 21: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 3801616A412 for ; Sat, 23 Sep 2006 21:24:41 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73BF43D4C for ; Sat, 23 Sep 2006 21:24:38 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k8NLObeQ051205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 Sep 2006 14:24:38 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4515A615.1020009@errno.com> Date: Sat, 23 Sep 2006 14:24:37 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: Bruce M Simpson References: <45159D63.2090108@incunabulum.net> In-Reply-To: <45159D63.2090108@incunabulum.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: De-orbitting tcpslice 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, 23 Sep 2006 21:24:41 -0000 Bruce M Simpson wrote: > We have tcpslice maintained in ports. We have ancient tcpslice in base > system. We have PRs about it. > > I'd like to nuke it in HEAD. > > How does everyone else feel about that before I go off and do it? do it