From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 00:17:12 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BFAE1065673; Sun, 9 Mar 2008 00:17:12 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E5EAB8FC19; Sun, 9 Mar 2008 00:17:11 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m290HBAN082411; Sun, 9 Mar 2008 00:17:11 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m290HBZn082407; Sun, 9 Mar 2008 00:17:11 GMT (envelope-from vwe) Date: Sun, 9 Mar 2008 00:17:11 GMT Message-Id: <200803090017.m290HBZn082407@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/121181: [panic] Fatal trap 3: breakpoint instruction fault while in kernel mode, rtfree: NULL rnh 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, 09 Mar 2008 00:17:12 -0000 Synopsis: [panic] Fatal trap 3: breakpoint instruction fault while in kernel mode, rtfree: NULL rnh Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Sun Mar 9 00:16:47 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=121181 From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 06:33:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E55AC1065670; Sun, 9 Mar 2008 06:33:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BC99B8FC1C; Sun, 9 Mar 2008 06:33:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m296X3QH025972; Sun, 9 Mar 2008 06:33:03 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m296X3Fg025968; Sun, 9 Mar 2008 06:33:03 GMT (envelope-from linimon) Date: Sun, 9 Mar 2008 06:33:03 GMT Message-Id: <200803090633.m296X3Fg025968@freefall.freebsd.org> To: linimon@FreeBSD.org, net@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/93378: [tcp] Slow data transfer in Postfix and Cyrus IMAP (workaround known) 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, 09 Mar 2008 06:33:04 -0000 Synopsis: [tcp] Slow data transfer in Postfix and Cyrus IMAP (workaround known) Responsible-Changed-From-To: net->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 9 06:32:55 UTC 2008 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=93378 From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 06:33:03 2008 Return-Path: Delivered-To: net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E55AC1065670; Sun, 9 Mar 2008 06:33:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BC99B8FC1C; Sun, 9 Mar 2008 06:33:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m296X3QH025972; Sun, 9 Mar 2008 06:33:03 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m296X3Fg025968; Sun, 9 Mar 2008 06:33:03 GMT (envelope-from linimon) Date: Sun, 9 Mar 2008 06:33:03 GMT Message-Id: <200803090633.m296X3Fg025968@freefall.freebsd.org> To: linimon@FreeBSD.org, net@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/93378: [tcp] Slow data transfer in Postfix and Cyrus IMAP (workaround known) 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, 09 Mar 2008 06:33:04 -0000 Synopsis: [tcp] Slow data transfer in Postfix and Cyrus IMAP (workaround known) Responsible-Changed-From-To: net->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 9 06:32:55 UTC 2008 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=93378 From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 09:09:55 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D26B8106566B for ; Sun, 9 Mar 2008 09:09:55 +0000 (UTC) (envelope-from rizzojake@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.188]) by mx1.freebsd.org (Postfix) with ESMTP id 9ED798FC28 for ; Sun, 9 Mar 2008 09:09:55 +0000 (UTC) (envelope-from rizzojake@gmail.com) Received: by rv-out-0910.google.com with SMTP id g13so902218rvb.43 for ; Sun, 09 Mar 2008 01:09:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=3GL0lRuSMKvf9+fGmUAZx6CQXq1KXlnhvrELGHLa8dI=; b=D5WUCkKyeOUmBJkq+RCUOXPB5wBaUGS7/efOPta2AGAGuICWdXxVV3o2aOSgMPLInroA5p2rrD2M3miy8ho2v4/1aseN/I86DNNL8Whn/KvzK83bOTxm9kpiP9IuJCv+6wk4YVzIVI8NmGKqDjm6H2zrtMemmkq6RIoNY9BrHoc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LYZ2DD+yt65qQ/7GQe19+TCb6MzAK85nqExQypuWFwyfd0xyysfjw0Iy74Y/H59QiS33OGJ6lwfPKA3h6BfHdaXSz/tWSmMnDe/Bb8edz6noCK2AUp+2YjSeNiGVS0Zmem+i8BODNPu2NRpoVCIjJ3xCmaddN4EPaHMVCHpyPzk= Received: by 10.141.113.6 with SMTP id q6mr2327045rvm.135.1205053795182; Sun, 09 Mar 2008 01:09:55 -0800 (PST) Received: by 10.141.22.11 with HTTP; Sun, 9 Mar 2008 01:09:55 -0800 (PST) Message-ID: Date: Sun, 9 Mar 2008 09:09:55 +0000 From: "Jake Rizzo" To: "Mike Silbersack" In-Reply-To: <20080307185203.J27119@niwun.pair.com> MIME-Version: 1.0 References: <20080307185203.J27119@niwun.pair.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: RELENG-7 tcp connectivity problems with certain clients 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, 09 Mar 2008 09:09:56 -0000 The patch didn't work, but doing this: sysctl net.inet.tcp.tso=0 sysctl net.inet.tcp.sack.enable=0 Allows the client to connect again. Since my ifconfig doesn't show that my nic supports TSO then I presume it's the sack sysctl that's making it work. The machine's a webserver serving almost exclusively dynamic content - with sack disabled is it likely to affect performance much? Thanks, Jake On Fri, Mar 7, 2008 at 11:52 PM, Mike Silbersack wrote: > > On Fri, 7 Mar 2008, Jake Rizzo wrote: > > > Hi, > > > > I had two 6.3-STABLE boxen which have been happily running away for > months > > on end now without any problems. Last week I upgraded (via buildworld) > both > > boxes to 7.0-STABLE. Since then I've had reports of some clients being > > unable to connect via tcp. I've seen this happen first hand on an > affected > > remote machine. Traceroute & ping gets to the machine just fine > > but connecting to an open tcp port on the machine just times out. The > > remote box was a XP machine and so I didn't have the luxury of tcp dump > on > > that end, however I did get a chance to run it at the freebsd end: > > Try this change; it was too late to be put in 7.0, but it will be merged > to 7-stable in a few days: > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_var.h.diff?r1=1.160;r2=1.161 > > -Mike > From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 09:17:25 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83EED106566C for ; Sun, 9 Mar 2008 09:17:25 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id 1573F8FC14 for ; Sun, 9 Mar 2008 09:17:24 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 71850 invoked from network); 9 Mar 2008 09:17:23 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 9 Mar 2008 09:17:23 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 9 Mar 2008 04:17:22 -0500 (CDT) From: Mike Silbersack To: Jake Rizzo In-Reply-To: Message-ID: <20080309041601.X37603@odysseus.silby.com> References: <20080307185203.J27119@niwun.pair.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: RELENG-7 tcp connectivity problems with certain clients 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, 09 Mar 2008 09:17:25 -0000 On Sun, 9 Mar 2008, Jake Rizzo wrote: > The patch didn't work, but doing this: > > sysctl net.inet.tcp.tso=0 > sysctl net.inet.tcp.sack.enable=0 > > Allows the client to connect again. Since my ifconfig doesn't show that my > nic supports TSO then I presume it's the sack sysctl that's making it work. > > The machine's a webserver serving almost exclusively dynamic content - with > sack disabled is it likely to affect performance much? > > Thanks, > Jake SACK makes retransmission more effective in some circumstances when packet loss occurs. So, you're probably not going to notice it being disabled at all. In fact. FreeBSD 4.x didn't have any SACK support whatsoever. -Mike From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 11:29:44 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A70931065675 for ; Sun, 9 Mar 2008 11:29:44 +0000 (UTC) (envelope-from maddog2k@maddog2k.net) Received: from smtp.fiqz.com (smtp.fiqz.com [IPv6:2001:898:2000:8::132]) by mx1.freebsd.org (Postfix) with ESMTP id 3E4B98FC32 for ; Sun, 9 Mar 2008 11:29:44 +0000 (UTC) (envelope-from maddog2k@maddog2k.net) Received: from coredump (maddog2k.xs4all.nl [80.126.100.65]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp.fiqz.com (Postfix) with ESMTP id C79862F8B29 for ; Sun, 9 Mar 2008 12:26:55 +0100 (CET) Message-ID: <006601c881d8$f4908490$6ac8a8c0@lan.dejong.biz> From: "Wouter de Jong" To: Date: Sun, 9 Mar 2008 12:30:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: randomized CARP ip alias order -> breaks CARP (incorrect hash) 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, 09 Mar 2008 11:29:44 -0000 Hi, (Sorry for double posting this to freebsd-questions before, but I think this place might be more appropriate). We have 2 FreeBSD machines running as a firewall in a CARP+pf+pfsync setup. Worked great, however ..... last Friday I noticed something weird. I had to reboot the master machine, and when it came back ... one of the CARP addresses no longer worked. Looking in the logs, I got carp4: incorrect hash And looking at the carp interface .... both machines were running MASTER for this interface. Looking closer, I noticed my primary machine had this configuration : carp4: flags=49 metric 0 mtu 1500 inet 213.206.xx.62 netmask 0xfffffff0 inet 213.206.xx.49 netmask 0xfffffff0 carp: MASTER vhid 4 advbase 1 advskew 100 and my secondary : carp4: flags=49 metric 0 mtu 1500 inet 213.206.xx.49 netmask 0xfffffff0 inet 213.206.xx.62 netmask 0xfffffff0 carp: MASTER vhid 4 advbase 1 advskew 100 It swapped the carp alias alias (213.206.xx.62) to be the first address on the interface. This was the only interface it happened. The config : primary: ############################## defaultrouter="213.206.yy.193" hostname="fw01.xxx.yyy" cloned_interfaces="carp0 carp1 carp2 carp3 carp4 carp5 carp6 carp7 carp8 carp9 carp10 carp11 carp12 carp13 carp14 carp15 carp16 carp17 carp18 carp19 carp20 carp21 carp22 carp23 carp24 carp25 carp26 carp27 carp28" ifconfig_bge0="inet 213.206.yy.194 netmask 255.255.255.240" ifconfig_bge1="inet 213.206.xx.2 netmask 255.255.255.240" ifconfig_bge1_alias0="inet 213.206.xx.18 netmask 255.255.255.240" ifconfig_bge1_alias1="inet 213.206.xx.34 netmask 255.255.255.240" ifconfig_bge1_alias2="inet 213.206.xx.50 netmask 255.255.255.240" ifconfig_bge1_alias3="inet 213.206.xx.66 netmask 255.255.255.240" ifconfig_bge1_alias4="inet 213.206.xx.82 netmask 255.255.255.240" ifconfig_carp0="vhid 255 pass blubVIP0255 213.206.yy.206/28" ifconfig_carp1="vhid 1 pass blubVIP0001 213.206.xx.1/28" ifconfig_carp2="vhid 2 pass blubVIP0002 213.206.xx.17/28" ifconfig_carp2_alias0="vhid 2 pass blubVIP0002 213.206.xx.30/28" ifconfig_carp3="vhid 3 pass blubVIP0003 213.206.xx.33/28" ifconfig_carp4="vhid 4 pass blubVIP0004 213.206.xx.49/28" ifconfig_carp4_alias0="vhid 4 pass blubVIP0004 213.206.xx.62/28" ifconfig_carp5="vhid 5 pass blubVIP0005 213.206.xx.65/28" ifconfig_carp6="vhid 6 pass blubVIP0006 213.206.xx.81/28" ############################## secondary: ############################## defaultrouter="213.206.yy.193" hostname="fw02.xxx.yyy" cloned_interfaces="carp0 carp1 carp2 carp3 carp4 carp5 carp6 carp7 carp8 carp9 carp10 carp11 carp12 carp13 carp14 carp15 carp16 carp17 carp18 carp19 carp20 carp21 carp22 carp23 carp24 carp25 carp26 carp27 carp28" ifconfig_bge0="inet 213.206.yy.195 netmask 255.255.255.240" ifconfig_bge1="inet 213.206.xx.3 netmask 255.255.255.240" ifconfig_bge1_alias0="inet 213.206.xx.19 netmask 255.255.255.240" ifconfig_bge1_alias1="inet 213.206.xx.35 netmask 255.255.255.240" ifconfig_bge1_alias2="inet 213.206.xx.51 netmask 255.255.255.240" ifconfig_bge1_alias3="inet 213.206.xx.67 netmask 255.255.255.240" ifconfig_bge1_alias4="inet 213.206.xx.83 netmask 255.255.255.240" ifconfig_carp0="vhid 255 advskew 100 pass blubVIP0255 213.206.yy.206/28" ifconfig_carp1="vhid 1 advskew 100 pass blubVIP0001 213.206.xx.1/28" ifconfig_carp2="vhid 2 advskew 100 pass blubVIP0002 213.206.xx.17/28" ifconfig_carp2_alias0="vhid 2 advskew 100 pass blubVIP0002 213.206.xx.30/28" ifconfig_carp3="vhid 3 advskew 100 pass blubVIP0003 213.206.xx.33/28" ifconfig_carp4="vhid 4 advskew 100 pass blubVIP0004 213.206.xx.49/28" ifconfig_carp4_alias0="vhid 4 advskew 100 pass blubVIP0004 213.206.xx.62/28" ifconfig_carp5="vhid 5 advskew 100 pass blubVIP0005 213.206.xx.65/28" ifconfig_carp6="vhid 6 advskew 100 pass blubVIP0006 213.206.xx.81/28" ############################## After rebooting the secondary, it still gave me incorrect hash. But, it gave me the same thing on carp2 now. ... however, here the secondary had the carp2_alias0 listed as first, where as the primary had the carp2 as first, and the carp2_alias0 as second address. How can this ever happen ? And what can I do to (manually) prevent this ? Now I'm redundant .... but I must pray that the addresses will come up in the same order. Never had this issue on FreeBSD 6.x, but now I'm running FreeBSD 7.0-RELEASE. Help ! :) At lease one person on freebsd-questions observes the same thing...(both with 6.x and 7.x) Kind regards, Wouter de Jong The Netherlands From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 13:07:37 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4337B1065673; Sun, 9 Mar 2008 13:07:37 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 132A48FC1D; Sun, 9 Mar 2008 13:07:37 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (rwatson@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m29D7aJs074774; Sun, 9 Mar 2008 13:07:36 GMT (envelope-from rwatson@freefall.freebsd.org) Received: (from rwatson@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m29D7aD3074770; Sun, 9 Mar 2008 13:07:36 GMT (envelope-from rwatson) Date: Sun, 9 Mar 2008 13:07:36 GMT Message-Id: <200803091307.m29D7aD3074770@freefall.freebsd.org> To: rwatson@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: rwatson@FreeBSD.org Cc: Subject: Re: bin/112557: [patch] ppp(8) lock file should not use symlink name 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, 09 Mar 2008 13:07:37 -0000 Synopsis: [patch] ppp(8) lock file should not use symlink name Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: rwatson Responsible-Changed-When: Sun Mar 9 13:07:30 UTC 2008 Responsible-Changed-Why: Over to maintainers. http://www.freebsd.org/cgi/query-pr.cgi?pr=112557 From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 16:24:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A63511065673; Sun, 9 Mar 2008 16:24:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7216C8FC1E; Sun, 9 Mar 2008 16:24:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m29GO4TQ091982; Sun, 9 Mar 2008 16:24:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m29GO4ZB091978; Sun, 9 Mar 2008 16:24:04 GMT (envelope-from linimon) Date: Sun, 9 Mar 2008 16:24:04 GMT Message-Id: <200803091624.m29GO4ZB091978@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121518: [wpi] System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 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, 09 Mar 2008 16:24:04 -0000 Old Synopsis: System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 New Synopsis: [wpi] System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 9 16:18:51 UTC 2008 Responsible-Changed-Why: Over to maintainer(s), although as noted this is similar to kern/118897, and thus may not be interface-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=121518 From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 17:50:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1753B1065694 for ; Sun, 9 Mar 2008 17:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E55098FC25 for ; Sun, 9 Mar 2008 17:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m29Ho2Ih099761 for ; Sun, 9 Mar 2008 17:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m29Ho2ts099760; Sun, 9 Mar 2008 17:50:02 GMT (envelope-from gnats) Date: Sun, 9 Mar 2008 17:50:02 GMT Message-Id: <200803091750.m29Ho2ts099760@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Dimitar Peikov Cc: Subject: Re: kern/121518: [wpi] System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dimitar Peikov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 17:50:04 -0000 The following reply was made to PR kern/121518; it has been noted by GNATS. From: Dimitar Peikov To: bug-followup@FreeBSD.org, Dimitar.Peikov@gmail.com Cc: Subject: Re: kern/121518: [wpi] System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 Date: Sun, 09 Mar 2008 19:22:21 +0200 I've forgot to provide backtrace and dump information in PR. Kernel is GENERIC + SCHED_ULE + device wpi. I can provide more information if needed. ----- kdbg ----- Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07864fe stack pointer = 0x28:0xe6b72abc frame pointer = 0x28:0xe6b72adc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 1262 (ifconfig) trap number = 12 panic: page fault cpuid = 0 Uptime: 1h0m5s Physical memory: 1003 MB Dumping 145 MB: 130 114 98 82 66 50 34 (CTRL-C to abort) 18 2 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc07543e7 in boot (howto=260) at ../../../kern/kern_shutdown.c:409 #2 0xc07546a9 in panic (fmt=Variable "fmt" is not available. ) at ../../../kern/kern_shutdown.c:563 #3 0xc0a518bc in trap_fatal (frame=0xe6b72a7c, eva=20) at ../../../i386/i386/trap.c:899 #4 0xc0a5223f in trap (frame=0xe6b72a7c) at ../../../i386/i386/trap.c:280 #5 0xc0a3845b in calltrap () at ../../../i386/i386/exception.s:139 #6 0xc07864fe in propagate_priority (td=0xc429b220) at ../../../kern/subr_turnstile.c:272 #7 0xc0787338 in turnstile_wait (ts=0xc3ec5a00, owner=0xc429b220, queue=Variable "queue" is not available. ) at ../../../kern/subr_turnstile.c:739 #8 0xc0747f5e in _mtx_lock_sleep (m=0xc4077418, tid=3291456032, opts=0, file=0x0, line=0) at ../../../kern/kern_mutex.c:416 #9 0xc0a2fa08 in wpi_ioctl (ifp=0xc4064800, cmd=2149345770, data=0xc4112de0 "wpi0") at ../../../dev/wpi/if_wpi.c:2303 #10 0xc0824922 in in_control (so=0xc4b15630, cmd=2149345770, data=0xc4112de0 "wpi0", ifp=0xc4064800, td=0xc42fa220) at ../../../netinet/in.c:483 #11 0xc07e90dd in ifioctl (so=0xc4b15630, cmd=2149345770, data=0xc4112de0 "wpi0", td=0xc42fa220) at ../../../net/if.c:1888 #12 0xc078fbfa in soo_ioctl (fp=0xc4b4d5e8, cmd=2149345770, data=0xc4112de0, active_cred=0xc48b2e00, td=0xc42fa220) at ../../../kern/sys_socket.c:191 #13 0xc07889f5 in kern_ioctl (td=0xc42fa220, fd=3, com=2149345770, ---Type to continue, or q to quit--- data=0xc4112de0 "wpi0") at file.h:266 #14 0xc0788b54 in ioctl (td=0xc42fa220, uap=0xe6b72cfc) at ../../../kern/sys_generic.c:570 #15 0xc0a51e95 in syscall (frame=0xe6b72d38) at ../../../i386/i386/trap.c:1035 #16 0xc0a384c0 in Xint0x80_syscall () at ../../../i386/i386/exception.s:196 #17 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) ----- kdbg ----- From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 20:46:34 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E48DB106566B; Sun, 9 Mar 2008 20:46:34 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B5DB08FC18; Sun, 9 Mar 2008 20:46:34 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m29KkY0s014527; Sun, 9 Mar 2008 20:46:34 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m29KkYr2014523; Sun, 9 Mar 2008 20:46:34 GMT (envelope-from vwe) Date: Sun, 9 Mar 2008 20:46:34 GMT Message-Id: <200803092046.m29KkYr2014523@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: bin/79228: [patch] extend /sbin/arp to be able to create blackhole records 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, 09 Mar 2008 20:46:35 -0000 Synopsis: [patch] extend /sbin/arp to be able to create blackhole records Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Sun Mar 9 20:46:12 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=79228 From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 21:20:27 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63F0A1065673; Sun, 9 Mar 2008 21:20:27 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 385ED8FC1A; Sun, 9 Mar 2008 21:20:27 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from freefall.freebsd.org (thompsa@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m29LKRbb017040; Sun, 9 Mar 2008 21:20:27 GMT (envelope-from thompsa@freefall.freebsd.org) Received: (from thompsa@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m29LKRXk017036; Sun, 9 Mar 2008 21:20:27 GMT (envelope-from thompsa) Date: Sun, 9 Mar 2008 21:20:27 GMT Message-Id: <200803092120.m29LKRXk017036@freefall.freebsd.org> To: thompsa@FreeBSD.org, freebsd-net@FreeBSD.org, thompsa@FreeBSD.org From: thompsa@FreeBSD.org Cc: Subject: Re: kern/121518: [wpi] System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 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, 09 Mar 2008 21:20:27 -0000 Synopsis: [wpi] System reboot after enabling DHCP on bge0 and assigning static IP on wpi0 Responsible-Changed-From-To: freebsd-net->thompsa Responsible-Changed-By: thompsa Responsible-Changed-When: Sun Mar 9 21:20:07 UTC 2008 Responsible-Changed-Why: I have been working on a wpi patch. http://www.freebsd.org/cgi/query-pr.cgi?pr=121518 From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 02:29:54 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07CD9106566B for ; Mon, 10 Mar 2008 02:29:54 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8F38FC13 for ; Mon, 10 Mar 2008 02:29:53 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-038-140.pools.arcor-ip.net [88.66.38.140]) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis) id 0MKwtQ-1JYXlv2nJi-0003og; Mon, 10 Mar 2008 03:29:52 +0100 Received: (qmail 95890 invoked by uid 80); 10 Mar 2008 02:29:17 -0000 Received: from 192.168.4.151 (SquirrelMail authenticated user mlaier) by router.laiers.local with HTTP; Mon, 10 Mar 2008 03:29:17 +0100 (CET) Message-ID: <34558.192.168.4.151.1205116157.squirrel@router.laiers.local> In-Reply-To: <006601c881d8$f4908490$6ac8a8c0@lan.dejong.biz> References: <006601c881d8$f4908490$6ac8a8c0@lan.dejong.biz> Date: Mon, 10 Mar 2008 03:29:17 +0100 (CET) From: "Max Laier" To: "Wouter de Jong" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Provags-ID: V01U2FsdGVkX1/W42l+hORFD5kdzHRHjH9EeJLk91reArQlpkI 8w6VxGnzpVv2ICy9CzB0YCoGhoxjo3yIK2Lhc7fUz0ArDBOC0f jQ5D+1MgBRO/8xaVC+9Yg== Cc: freebsd-net@freebsd.org Subject: Re: randomized CARP ip alias order -> breaks CARP (incorrect hash) 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, 10 Mar 2008 02:29:54 -0000 Am So, 9.03.2008, 12:30, schrieb Wouter de Jong: > (Sorry for double posting this to freebsd-questions before, but I think > this > place might be more appropriate). indeed it is. > We have 2 FreeBSD machines running as a firewall in a CARP+pf+pfsync > setup. > Worked great, however ..... last Friday I noticed something weird. > > I had to reboot the master machine, and when it came back ... > one of the CARP addresses no longer worked. > > Looking in the logs, I got carp4: incorrect hash > > And looking at the carp interface .... both machines were running MASTER > for > this interface. > > Looking closer, I noticed my primary machine had this configuration : > > carp4: flags=49 metric 0 mtu 1500 > inet 213.206.xx.62 netmask 0xfffffff0 > inet 213.206.xx.49 netmask 0xfffffff0 > carp: MASTER vhid 4 advbase 1 advskew 100 > > and my secondary : > > carp4: flags=49 metric 0 mtu 1500 > inet 213.206.xx.49 netmask 0xfffffff0 > inet 213.206.xx.62 netmask 0xfffffff0 > carp: MASTER vhid 4 advbase 1 advskew 100 > > It swapped the carp alias alias (213.206.xx.62) to be the first address on > the interface. This has already been reported and I will look into it. Could you, however, please file a PR and CC me? Just so I don't forget (again). Thanks. > This was the only interface it happened. > > The config : > > primary: > ############################## > defaultrouter="213.206.yy.193" > hostname="fw01.xxx.yyy" > > cloned_interfaces="carp0 carp1 carp2 carp3 carp4 carp5 carp6 carp7 carp8 > carp9 carp10 carp11 carp12 carp13 carp14 carp15 carp16 carp17 carp18 > carp19 > carp20 carp21 carp22 carp23 carp24 carp25 carp26 carp27 carp28" > > ifconfig_bge0="inet 213.206.yy.194 netmask 255.255.255.240" > ifconfig_bge1="inet 213.206.xx.2 netmask 255.255.255.240" > ifconfig_bge1_alias0="inet 213.206.xx.18 netmask 255.255.255.240" > ifconfig_bge1_alias1="inet 213.206.xx.34 netmask 255.255.255.240" > ifconfig_bge1_alias2="inet 213.206.xx.50 netmask 255.255.255.240" > ifconfig_bge1_alias3="inet 213.206.xx.66 netmask 255.255.255.240" > ifconfig_bge1_alias4="inet 213.206.xx.82 netmask 255.255.255.240" > > ifconfig_carp0="vhid 255 pass blubVIP0255 213.206.yy.206/28" > ifconfig_carp1="vhid 1 pass blubVIP0001 213.206.xx.1/28" > ifconfig_carp2="vhid 2 pass blubVIP0002 213.206.xx.17/28" > ifconfig_carp2_alias0="vhid 2 pass blubVIP0002 213.206.xx.30/28" > ifconfig_carp3="vhid 3 pass blubVIP0003 213.206.xx.33/28" > ifconfig_carp4="vhid 4 pass blubVIP0004 213.206.xx.49/28" > ifconfig_carp4_alias0="vhid 4 pass blubVIP0004 213.206.xx.62/28" > ifconfig_carp5="vhid 5 pass blubVIP0005 213.206.xx.65/28" > ifconfig_carp6="vhid 6 pass blubVIP0006 213.206.xx.81/28" > ############################## > > secondary: > ############################## > defaultrouter="213.206.yy.193" > hostname="fw02.xxx.yyy" > > cloned_interfaces="carp0 carp1 carp2 carp3 carp4 carp5 carp6 carp7 carp8 > carp9 carp10 carp11 carp12 carp13 carp14 carp15 carp16 carp17 carp18 > carp19 > carp20 carp21 carp22 carp23 carp24 carp25 carp26 carp27 carp28" > > ifconfig_bge0="inet 213.206.yy.195 netmask 255.255.255.240" > ifconfig_bge1="inet 213.206.xx.3 netmask 255.255.255.240" > ifconfig_bge1_alias0="inet 213.206.xx.19 netmask 255.255.255.240" > ifconfig_bge1_alias1="inet 213.206.xx.35 netmask 255.255.255.240" > ifconfig_bge1_alias2="inet 213.206.xx.51 netmask 255.255.255.240" > ifconfig_bge1_alias3="inet 213.206.xx.67 netmask 255.255.255.240" > ifconfig_bge1_alias4="inet 213.206.xx.83 netmask 255.255.255.240" > > ifconfig_carp0="vhid 255 advskew 100 pass blubVIP0255 213.206.yy.206/28" > ifconfig_carp1="vhid 1 advskew 100 pass blubVIP0001 213.206.xx.1/28" > ifconfig_carp2="vhid 2 advskew 100 pass blubVIP0002 213.206.xx.17/28" > ifconfig_carp2_alias0="vhid 2 advskew 100 pass blubVIP0002 > 213.206.xx.30/28" > ifconfig_carp3="vhid 3 advskew 100 pass blubVIP0003 213.206.xx.33/28" > ifconfig_carp4="vhid 4 advskew 100 pass blubVIP0004 213.206.xx.49/28" > ifconfig_carp4_alias0="vhid 4 advskew 100 pass blubVIP0004 > 213.206.xx.62/28" > ifconfig_carp5="vhid 5 advskew 100 pass blubVIP0005 213.206.xx.65/28" > ifconfig_carp6="vhid 6 advskew 100 pass blubVIP0006 213.206.xx.81/28" > ############################## > > After rebooting the secondary, it still gave me incorrect hash. > But, it gave me the same thing on carp2 now. ... however, here the > secondary > had the carp2_alias0 listed as first, > where as the primary had the carp2 as first, and the carp2_alias0 as > second > address. > > How can this ever happen ? And what can I do to (manually) prevent this ? > > Now I'm redundant .... but I must pray that the addresses will come up in > the same order. > > Never had this issue on FreeBSD 6.x, but now I'm running FreeBSD > 7.0-RELEASE. > > Help ! :) > > At lease one person on freebsd-questions observes the same thing...(both > with 6.x and 7.x) > > > Kind regards, > > Wouter de Jong > The Netherlands > > _______________________________________________ > 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" > > -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 02:32:53 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E5931065672 for ; Mon, 10 Mar 2008 02:32:53 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: from hal.rescomp.berkeley.edu (hal.Rescomp.Berkeley.EDU [169.229.70.150]) by mx1.freebsd.org (Postfix) with ESMTP id 63E398FC17 for ; Mon, 10 Mar 2008 02:32:53 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: by hal.rescomp.berkeley.edu (Postfix, from userid 1225) id BF27C3C04B6; Sun, 9 Mar 2008 19:32:52 -0700 (PDT) Date: Sun, 9 Mar 2008 19:32:52 -0700 From: Christopher Cowart To: Pyun YongHyeon Message-ID: <20080310023252.GM30324@hal.rescomp.berkeley.edu> Mail-Followup-To: Pyun YongHyeon , freebsd-net@freebsd.org References: <20080225091712.GM88015@hal.rescomp.berkeley.edu> <20080226074355.GD47750@cdnetworks.co.kr> <20080228023840.GR58253@hal.rescomp.berkeley.edu> <20080229060353.GC60623@cdnetworks.co.kr> <20080303035728.GD58253@hal.rescomp.berkeley.edu> <20080307050004.GB92656@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="deSP9Bnrq3taYiYM" Content-Disposition: inline In-Reply-To: <20080307050004.GB92656@cdnetworks.co.kr> Organization: RSSP-IT, UC Berkeley User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-net@freebsd.org Subject: Re: msk driver issues [was: Re: vlan issues with 7.0-RC3] 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, 10 Mar 2008 02:32:53 -0000 --deSP9Bnrq3taYiYM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 07, 2008 at 02:00:04PM +0900, Pyun YongHyeon wrote: >On Sun, Mar 02, 2008 at 07:57:28PM -0800, Christopher Cowart wrote: >> While I have your attention, I am also suffering from a problem that was >> reported to -questions here[1]. About 3 times a day, I'll see the >> watchdog timeout (missed Tx interrupts) message get logged, after which >> point the NIC is useless until I reboot. Any ideas? >>=20 >> [1] http://lists.freebsd.org/pipermail/freebsd-questions/2008-February/1= 69633.html >=20 > I'll have a look. Pyun recommended the following workaround in /boot/loader.conf: hw.msk.msi_disable=3D"1" The NIC has now been working reliably for nearly 3 days.=20 Pyun YongHyeon wrote: | Glad to hear that. The knob exists to work-around hardware bugs | present in some PCI bridges that can't handle MSI correctly. | Normally FreeBSD black-lists known PCI bridges that have this kind | of bugs but the list may/may not complete. I'm not sure whether this | is really a bug in PCI bridge on MacBook but most owners of MacBook=20 | seems to require the knob. Thanks for the help. --=20 Chris Cowart Network Technical Lead Network & Infrastructure Services, RSSP-IT UC Berkeley --deSP9Bnrq3taYiYM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iQIVAwUBR9Sd1CPHEDszU3zYAQLKJxAAvCeWjRW1VTi8CS5ksvceJR7nsir2x0q3 wXOrB8JkTt3m7BLxUWRHs+35xKYfNnxKUdfi0yMhuZbY1QLUwmhBGmqrsME91c0a HkaqWeewZF181NFRsf+Yn9s1Mvd9dLKR9YQnENegFk/XwBv9YKt+ZCLRGEnk4LbN St3TDOqJmHBlpCvcLv+ixYnqwFAdXKhCU94R03uavpfNcJmrE0McCR4Q5KbjbxI7 amWPw3ZQz5OkOy5uTH+rnmFlUuJu+/B3ECF9hV2LUGzKexl5Hr3dBdUmSOMBjnuA 3/+SF8F9V1Kle5Ls4bb2YRwKFtQ8CuIkMZK+Iuc39sHCsflLc1YzhhnrlGjIudyW B1eXDp1bTJbB5NvkvbrqaFBDfVnJDWDPbLjoiGwpadr4GCOpOceZByg17ByIRWoB iCq5xqgQg7zQvgIEC1hkY4ZeDI5UXQozx1klsJrgNJQ6E2Aqh0ZZ6jm37QUoozBs mcUV1GmxZl24bNimUj9CAEp2gSJDu0UzzAjbEehvDzmEvNtG+24ciSArig+tyJV3 c9mL3rc4Xo/dIDQ7unlxBRh4DUdhVmhynj553j6DSHC/Cxdm/iMjtfcx7ckYTe7y +CzWDCOnBPCs7uvjB6YwDalDc/FUzMW4J+3amqbk7dkwR/KD19ILUeXm9mumvog9 HWoj4RTaAzg= =CoIg -----END PGP SIGNATURE----- --deSP9Bnrq3taYiYM-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 11:07:07 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7FA41065721 for ; Mon, 10 Mar 2008 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1CAE8FC2A for ; Mon, 10 Mar 2008 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2AB77T1086632 for ; Mon, 10 Mar 2008 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2AB76wN086628 for freebsd-net@FreeBSD.org; Mon, 10 Mar 2008 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Mar 2008 11:07:06 GMT Message-Id: <200803101107.m2AB76wN086628@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org 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, 10 Mar 2008 11:07:07 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/92090 net [bge] bge0: watchdog timeout -- resetting f kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/105943 net Network stack may modify read-only mbuf chain copies o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/113842 net [ipv6] PF_INET6 proto domain state can't be cleared wi o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast f kern/116172 net [tun] [panic] Network / ipv6 recursive mutex panic o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116328 net [bge]: Solid hang with bge interface o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117423 net [vlan] Duplicate IP on different interfaces o kern/117448 net [carp] 6.2 kernel crash (regression) o kern/118880 net [ipv6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card (regr o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119361 net [bge] bge(4) transmit performance problem o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time f kern/120725 net [bce] On board second lan port 'bce1' with Broadcom Ne f kern/120966 net [rum]: kernel panic with if_rum and WPA encryption o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA 38 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 o kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o bin/79228 net [patch] extend /sbin/arp to be able to create blackhol o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/95267 net packet drops periodically appear o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/100519 net [netisr] suggestion to fix suboptimal network polling 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 conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/112179 net [sis] [patch] sis driver for natsemi DP83815D autonego o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o bin/117339 net [patch] route(8): loading routing management commands o kern/118727 net [ng] [patch] [request] add new ng_pf module a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118975 net [bge] [patch] Broadcom 5906 not handled by FreeBSD o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/119432 net [arp] route add -host -iface causes arp e o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120493 net [wpi] if_wpi.ko fails to load on a Toshiba Satellite P o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120958 net no response to ICMP traffic on interface configured wi o kern/121242 net [ate] [patch] Promiscuous mode of if_ate (arm) doesn't o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic f kern/121274 net [panic] Panic in ether_input() with different NIC's. o kern/121443 net [gif] LOR icmp6_input/nd6_lookup 35 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 11:53:27 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D366D1065672 for ; Mon, 10 Mar 2008 11:53:27 +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 C80F28FC19 for ; Mon, 10 Mar 2008 11:53:27 +0000 (UTC) (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 B6ECE46B1E; Mon, 10 Mar 2008 06:36:30 -0500 (EST) Date: Mon, 10 Mar 2008 12:36:30 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Message-ID: <20080310122338.T29929@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: net@FreeBSD.org Subject: netatm removal warning 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, 10 Mar 2008 11:53:27 -0000 Dear all, This is another of those boring e-mails about kernel subsystems that still require Giant. Sorry about that! As previously published, netatm is a non-MPSAFE protocol stack largely superseded by our two other ATM stacks, netnatm and the netgraph/atm (both MPSAFE). netatm is currently non-functional and uncompileable because it depends on the Giant compatibility shims for the protocol stack, which were removed in FreeBSD 7.0. We left the code in place in case to make it easier for any interested third parties to distribute patches against it (in particular, patches to make it MPSAFE). The current plan is that we will remove the netatm code from HEAD and RELENG_7 before FreeBSD 7.1. A specific schedue for 7.1 hasn't been published yet, but in order to give plenty of warning, here's the proposed netatm removal schedule: 10 March 2008 E-mail warning to arch@/net@ 10 April 2008 E-mail warning to arch@/net@ 10 May 2008 Removal of netatm from HEAD 20 May 2008 Removal of netatm from RELENG_7 Obviously, netatm will remain in the revision control history should anyone wish to ressurect it after that date. However, I suspect that those interested in ATM on FreeBSD have long since been using Harti's netgraph ATM framework. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 12:55:43 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0A4C106566B; Mon, 10 Mar 2008 12:55:43 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8CCC48FC14; Mon, 10 Mar 2008 12:55:43 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2ACthgt001083; Mon, 10 Mar 2008 12:55:43 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2ACthHM001079; Mon, 10 Mar 2008 12:55:43 GMT (envelope-from linimon) Date: Mon, 10 Mar 2008 12:55:43 GMT Message-Id: <200803101255.m2ACthHM001079@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121555: Fatal trap 12: current process = 12 (swi1: net) 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, 10 Mar 2008 12:55:43 -0000 Old Synopsis: [7.0-RELEASE] Fatal trap 12: current process = 12 (swi1: net) New Synopsis: Fatal trap 12: current process = 12 (swi1: net) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 10 12:53:45 UTC 2008 Responsible-Changed-Why: Appears to be a problem in the networking code. http://www.freebsd.org/cgi/query-pr.cgi?pr=121555 From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 13:07:53 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED8C3106566C; Mon, 10 Mar 2008 13:07:53 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D999F8FC13; Mon, 10 Mar 2008 13:07:53 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2AD7rqX001641; Mon, 10 Mar 2008 13:07:53 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2AD7r1G001637; Mon, 10 Mar 2008 13:07:53 GMT (envelope-from gavin) Date: Mon, 10 Mar 2008 13:07:53 GMT Message-Id: <200803101307.m2AD7r1G001637@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/121534: [ipl] [nat] FreeBSD Release 6.3 Kernel Trap 12: 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, 10 Mar 2008 13:07:54 -0000 Old Synopsis: FreeBSD Release 6.3 Kernel Trap 12: New Synopsis: [ipl] [nat] FreeBSD Release 6.3 Kernel Trap 12: Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Mon Mar 10 13:05:27 UTC 2008 Responsible-Changed-Why: Looks like this is -net's domain http://www.freebsd.org/cgi/query-pr.cgi?pr=121534 From owner-freebsd-net@FreeBSD.ORG Mon Mar 10 23:33:08 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABAAC1065671; Mon, 10 Mar 2008 23:33:08 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 651DF8FC20; Mon, 10 Mar 2008 23:33:08 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2ANX8J8060170; Mon, 10 Mar 2008 23:33:08 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2ANX8hD060166; Mon, 10 Mar 2008 23:33:08 GMT (envelope-from linimon) Date: Mon, 10 Mar 2008 23:33:08 GMT Message-Id: <200803102333.m2ANX8hD060166@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121574: [carp] CARP hash dependent on order of IP addresses on 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: Mon, 10 Mar 2008 23:33:08 -0000 Old Synopsis: CARP hash dependent on order of IP addresses on interface New Synopsis: [carp] CARP hash dependent on order of IP addresses on interface Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 10 23:32:44 UTC 2008 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=121574 From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 09:20:02 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C855E1065671 for ; Tue, 11 Mar 2008 09:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8A8108FC1E for ; Tue, 11 Mar 2008 09:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2B9K24p004979 for ; Tue, 11 Mar 2008 09:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2B9K23J004978; Tue, 11 Mar 2008 09:20:02 GMT (envelope-from gnats) Date: Tue, 11 Mar 2008 09:20:02 GMT Message-Id: <200803110920.m2B9K23J004978@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Wouter de Jong" Cc: Subject: Re: kern/121574: [carp] CARP hash dependent on order of IPaddresses on interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Wouter de Jong List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2008 09:20:02 -0000 The following reply was made to PR kern/121574; it has been noted by GNATS. From: "Wouter de Jong" To: , Cc: Subject: Re: kern/121574: [carp] CARP hash dependent on order of IPaddresses on interface Date: Tue, 11 Mar 2008 09:58:49 +0100 While it would be great to see carp fixed to handle this issue, shouldn't the order of IP-addresses on the interface be fixed as well ? It is very random, which people won't expect ... :) From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 10:40:02 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2CC41065673 for ; Tue, 11 Mar 2008 10:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AB8CA8FC26 for ; Tue, 11 Mar 2008 10:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2BAe2dl010864 for ; Tue, 11 Mar 2008 10:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2BAe2Iv010863; Tue, 11 Mar 2008 10:40:02 GMT (envelope-from gnats) Date: Tue, 11 Mar 2008 10:40:02 GMT Message-Id: <200803111040.m2BAe2Iv010863@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Max Laier" Cc: Subject: Re: kern/121574: [carp] CARP hash dependent on order of IP addresses on interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Max Laier List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2008 10:40:02 -0000 The following reply was made to PR kern/121574; it has been noted by GNATS. From: "Max Laier" To: bug-followup@freebsd.org Cc: rand@meridian-enviro.com, maddog2k@maddog2k.net Subject: Re: kern/121574: [carp] CARP hash dependent on order of IP addresses on interface Date: Tue, 11 Mar 2008 11:28:34 +0100 (CET) ------=_20080311112834_27075 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit (subject helps) Please try the attached patch (mostly OpenBSD rev. 1.114 plus follow-ups). This should fix the symptom. I have no idea why your address lists would get skewed however. They "should"[tm] be in the order in which you add aliases. -- Max ------=_20080311112834_27075 Content-Type: text/x-diff; name="ip_carp.c.HEAD.diff" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="ip_carp.c.HEAD.diff" Index: ip_carp.c =================================================================== RCS file: /home/mlaier/fcvs/src/sys/netinet/ip_carp.c,v retrieving revision 1.27.2.12 diff -u -r1.27.2.12 ip_carp.c --- ip_carp.c 1 Feb 2008 11:20:41 -0000 1.27.2.12 +++ ip_carp.c 11 Mar 2008 10:16:12 -0000 @@ -238,9 +238,12 @@ u_int8_t version = CARP_VERSION, type = CARP_ADVERTISEMENT; u_int8_t vhid = sc->sc_vhid & 0xff; struct ifaddr *ifa; - int i; + int i, found; +#ifdef INET + struct in_addr last, cur, in; +#endif #ifdef INET6 - struct in6_addr in6; + struct in6_addr last6, cur6, in6; #endif if (sc->sc_carpdev) @@ -261,21 +264,44 @@ SHA1Update(&sc->sc_sha1, (void *)&type, sizeof(type)); SHA1Update(&sc->sc_sha1, (void *)&vhid, sizeof(vhid)); #ifdef INET - TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { - if (ifa->ifa_addr->sa_family == AF_INET) - SHA1Update(&sc->sc_sha1, - (void *)&ifatoia(ifa)->ia_addr.sin_addr.s_addr, - sizeof(struct in_addr)); - } + cur.s_addr = 0; + do { + found = 0; + last = cur; + cur.s_addr = 0xffffffff; + TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { + in.s_addr = ifatoia(ifa)->ia_addr.sin_addr.s_addr; + if (ifa->ifa_addr->sa_family == AF_INET && + ntohl(in.s_addr) > ntohl(last.s_addr) && + ntohl(in.s_addr) < ntohl(cur.s_addr)) { + cur.s_addr = in.s_addr; + found++; + } + } + if (found) + SHA1Update(&sc->sc_sha1, (void *)&cur, sizeof(cur)); + } while (found); #endif /* INET */ #ifdef INET6 - TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { - if (ifa->ifa_addr->sa_family == AF_INET6) { + memset(&cur6, 0, sizeof(cur6)); + do { + found = 0; + last6 = cur6; + memset(&cur6, 0xff, sizeof(cur6)); + TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { in6 = ifatoia6(ifa)->ia_addr.sin6_addr; - in6_clearscope(&in6); - SHA1Update(&sc->sc_sha1, (void *)&in6, sizeof(in6)); + if (IN6_IS_SCOPE_EMBED(&in6)) + in6.s6_addr16[1] = 0; + if (ifa->ifa_addr->sa_family == AF_INET6 && + memcmp(&in6, &last6, sizeof(in6)) > 0 && + memcmp(&in6, &cur6, sizeof(in6)) < 0) { + cur6 = in6; + found++; + } } - } + if (found) + SHA1Update(&sc->sc_sha1, (void *)&cur6, sizeof(cur6)); + } while (found); #endif /* INET6 */ /* convert ipad to opad */ ------=_20080311112834_27075 Content-Type: text/x-diff; name="ip_carp.c.RELENG_6.diff" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="ip_carp.c.RELENG_6.diff" Index: ip_carp.c =================================================================== RCS file: /home/mlaier/fcvs/src/sys/netinet/ip_carp.c,v retrieving revision 1.27.2.12 diff -u -r1.27.2.12 ip_carp.c --- ip_carp.c 1 Feb 2008 11:20:41 -0000 1.27.2.12 +++ ip_carp.c 11 Mar 2008 10:20:42 -0000 @@ -238,9 +238,12 @@ u_int8_t version = CARP_VERSION, type = CARP_ADVERTISEMENT; u_int8_t vhid = sc->sc_vhid & 0xff; struct ifaddr *ifa; - int i; + int i, found; +#ifdef INET + struct in_addr last, cur, in; +#endif #ifdef INET6 - struct in6_addr in6; + struct in6_addr last6, cur6, in6; #endif if (sc->sc_carpdev) @@ -261,21 +264,45 @@ SHA1Update(&sc->sc_sha1, (void *)&type, sizeof(type)); SHA1Update(&sc->sc_sha1, (void *)&vhid, sizeof(vhid)); #ifdef INET - TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { - if (ifa->ifa_addr->sa_family == AF_INET) - SHA1Update(&sc->sc_sha1, - (void *)&ifatoia(ifa)->ia_addr.sin_addr.s_addr, - sizeof(struct in_addr)); - } + cur.s_addr = 0; + do { + found = 0; + last = cur; + cur.s_addr = 0xffffffff; + TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { + in.s_addr = ifatoia(ifa)->ia_addr.sin_addr.s_addr; + if (ifa->ifa_addr->sa_family == AF_INET && + ntohl(in.s_addr) > ntohl(last.s_addr) && + ntohl(in.s_addr) < ntohl(cur.s_addr)) { + cur.s_addr = in.s_addr; + found++; + } + } + if (found) + SHA1Update(&sc->sc_sha1, (void *)&cur, sizeof(cur)); + } while (found); #endif /* INET */ #ifdef INET6 - TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { - if (ifa->ifa_addr->sa_family == AF_INET6) { + memset(&cur6, 0, sizeof(cur6)); + do { + found = 0; + last6 = cur6; + memset(&cur6, 0xff, sizeof(cur6)); + TAILQ_FOREACH(ifa, &SC2IFP(sc)->if_addrlist, ifa_list) { in6 = ifatoia6(ifa)->ia_addr.sin6_addr; - in6_clearscope(&in6); - SHA1Update(&sc->sc_sha1, (void *)&in6, sizeof(in6)); + if (IN6_IS_SCOPE_LINKLOCAL(&in6) || + IN6_IS_ADDR_MC_INTFACELOCAL(&in6)) + in6.s6_addr16[1] = 0; + if (ifa->ifa_addr->sa_family == AF_INET6 && + memcmp(&in6, &last6, sizeof(in6)) > 0 && + memcmp(&in6, &cur6, sizeof(in6)) < 0) { + cur6 = in6; + found++; + } } - } + if (found) + SHA1Update(&sc->sc_sha1, (void *)&cur6, sizeof(cur6)); + } while (found); #endif /* INET6 */ /* convert ipad to opad */ ------=_20080311112834_27075-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 11:03:38 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54DED106566C for ; Tue, 11 Mar 2008 11:03:38 +0000 (UTC) (envelope-from fam@solacetel.com) Received: from mail.solactel.com (fam.sky.net.pk [203.175.64.65]) by mx1.freebsd.org (Postfix) with SMTP id 357C48FC2E for ; Tue, 11 Mar 2008 11:03:36 +0000 (UTC) (envelope-from fam@solacetel.com) Received: (qmail 6251 invoked by uid 1026); 11 Mar 2008 10:35:56 -0000 Received: from 192.168.2.10 by fam.sky.net.pk (envelope-from , uid 1025) with qmail-scanner-1.25-st-qms (clamdscan: 0.92/5767. uvscan: v5.1.00/v5224. spamassassin: 3.2.4. perlscan: 1.25-st-qms. Clear:RC:0(192.168.2.10):SA:0(-1.2/5.0):. Processed in 52.20903 secs); 11 Mar 2008 10:35:56 -0000 X-Spam-Status: No, hits=-1.2 required=5.0 X-Antivirus-SolaceTel-Mail-From: fam@solacetel.com via fam.sky.net.pk X-Antivirus-SolaceTel: 1.25-st-qms (Clear:RC:0(192.168.2.10):SA:0(-1.2/5.0):. Processed in 52.20903 secs Process 6018) Received: from unknown (HELO solace638d593b) (fam@solacetel.com@192.168.2.10) by mail.solactel.com with SMTP; 11 Mar 2008 10:34:59 -0000 From: "Fazal Ahmed Malik" To: Date: Tue, 11 Mar 2008 15:34:34 +0500 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AciDY38oEM/CLOUuQpKbIUvAc1Sn8g== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Antivirus-SolaceTel-Message-ID: <120523170410706018@fam.sky.net.pk> Message-Id: <20080311110337.357C48FC2E@mx1.freebsd.org> Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: VLAN Speed set to 0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2008 11:03:38 -0000 Dear All, I have FreeBSD 5.2 working as router. Now I have created vlans on freebsd and cisco switch. All is working perfect only problem while monitoring vlan interfaces on freebsd with snmp. When I run snmpwalk vlan interface speed is set to zero hence vlan interfaces are commented out in mrtg configuration file. Please help if some one has found out any solution to this problem. Thanks in advance for the help. Fazal Ahmed Malik No virus found in this outgoing message. Checked by AVG. Version: 7.5.518 / Virus Database: 269.21.7/1324 - Release Date: 3/10/2008 7:27 PM From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 11:05:00 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FEE11065672; Tue, 11 Mar 2008 11:05:00 +0000 (UTC) (envelope-from mlaier@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2EDFF8FC19; Tue, 11 Mar 2008 11:05:00 +0000 (UTC) (envelope-from mlaier@FreeBSD.org) Received: from freefall.freebsd.org (mlaier@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2BB50LE012468; Tue, 11 Mar 2008 11:05:00 GMT (envelope-from mlaier@freefall.freebsd.org) Received: (from mlaier@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2BB4tV0012464; Tue, 11 Mar 2008 11:04:55 GMT (envelope-from mlaier) Date: Tue, 11 Mar 2008 11:04:55 GMT Message-Id: <200803111104.m2BB4tV0012464@freefall.freebsd.org> To: rand@meridian-enviro.com, mlaier@FreeBSD.org, freebsd-net@FreeBSD.org, mlaier@FreeBSD.org From: mlaier@FreeBSD.org Cc: Subject: Re: kern/121574: [carp] CARP hash dependent on order of IP addresses on 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: Tue, 11 Mar 2008 11:05:00 -0000 Synopsis: [carp] CARP hash dependent on order of IP addresses on interface State-Changed-From-To: open->feedback State-Changed-By: mlaier State-Changed-When: Tue Mar 11 11:03:51 UTC 2008 State-Changed-Why: Patch needs testing. Responsible-Changed-From-To: freebsd-net->mlaier Responsible-Changed-By: mlaier Responsible-Changed-When: Tue Mar 11 11:03:51 UTC 2008 Responsible-Changed-Why: Take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=121574 From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 13:40:05 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4581E106566B for ; Tue, 11 Mar 2008 13:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1BB9F8FC12 for ; Tue, 11 Mar 2008 13:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2BDe5q8026037 for ; Tue, 11 Mar 2008 13:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2BDe54a026036; Tue, 11 Mar 2008 13:40:05 GMT (envelope-from gnats) Date: Tue, 11 Mar 2008 13:40:05 GMT Message-Id: <200803111340.m2BDe54a026036@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Jonas Wolz" Cc: Subject: Re: kern/119225: [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card (regression) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jonas Wolz List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2008 13:40:05 -0000 The following reply was made to PR kern/119225; it has been noted by GNATS. From: "Jonas Wolz" To: jyrki.k@post.cz, bug-followup@FreeBSD.org Cc: Subject: Re: kern/119225: [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card (regression) Date: Tue, 11 Mar 2008 14:04:19 +0100 I can confirm this bug with a Prism3 chipset and FreeBSD 7.0-RELEASE. The relevant dmesg output is: wi0: mem 0xe4006000-0xe4006fff irq 18 at device 11.0 on pci0 wi0: [ITHREAD] wi0: using RF:PRISM3(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.1), Station (1.5.6) wi0: Ethernet address: 00:02:8a:a0:8a:96 "ifconfig wi0 up scan" will sometimes "complete" in a few seconds and sometimes take a few minutes but will never show any APs. An interesting aspect is that if I clear the ssid with "ifconfig wi0 ssid -" and take the interface up and down repeatedly sometimes the ssid of one AP will show up in ifconfig, but there will still be "no carrier" (unfortunately I don't know how reproduce this effect reliably). From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 15:05:31 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B99BF1065671 for ; Tue, 11 Mar 2008 15:05:31 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from websrv01.jr-hosting.nl (websrv01.jr-hosting.nl [78.47.69.233]) by mx1.freebsd.org (Postfix) with ESMTP id 612018FC16 for ; Tue, 11 Mar 2008 15:05:31 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from localhost ([127.0.0.1] helo=galain.elvandar.org) by websrv01.jr-hosting.nl with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JZ5Ts-0004PG-6Z; Tue, 11 Mar 2008 14:29:28 +0000 Received: from 194.74.82.3 (SquirrelMail authenticated user remko) by galain.elvandar.org with HTTP; Tue, 11 Mar 2008 15:29:28 +0100 (CET) Message-ID: <46520.194.74.82.3.1205245768.squirrel@galain.elvandar.org> In-Reply-To: <20080311110337.357C48FC2E@mx1.freebsd.org> References: <20080311110337.357C48FC2E@mx1.freebsd.org> Date: Tue, 11 Mar 2008 15:29:28 +0100 (CET) From: "Remko Lodder" To: "Fazal Ahmed Malik" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-net@freebsd.org Subject: Re: VLAN Speed set to 0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: remko@elvandar.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2008 15:05:31 -0000 On Tue, March 11, 2008 11:34 am, Fazal Ahmed Malik wrote: > Dear All, > > > > I have FreeBSD 5.2 working as router. Now I have created vlans on freebsd > and cisco switch. All is working perfect only problem while monitoring > vlan > interfaces on freebsd with snmp. When I run snmpwalk vlan interface speed > is > set to zero hence vlan interfaces are commented out in mrtg configuration > file. Please help if some one has found out any solution to this problem. > > > > Thanks in advance for the help. > > > > > > Fazal Ahmed Malik Dear Fazal, Can you please upgrade to RELENG_6 (6.3-RELEASE) or to RELENG_7 (7.0-RELEASE)? This is because FreeBSD 5.2 is no longer supported, long time overdue. We are currently at RELEASE 5.5 for the 5 Branch which is EoL in 2 months (may). You are strongly advised to use RELENG_7 where possible. Thanks, Remko -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 17:49:42 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D6121065675; Tue, 11 Mar 2008 17:49:42 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 500698FC13; Tue, 11 Mar 2008 17:49:42 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2BHngWu047668; Tue, 11 Mar 2008 17:49:42 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2BHng4p047664; Tue, 11 Mar 2008 17:49:42 GMT (envelope-from gavin) Date: Tue, 11 Mar 2008 17:49:42 GMT Message-Id: <200803111749.m2BHng4p047664@freefall.freebsd.org> To: gavin@FreeBSD.org, gnats-admin@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/121608: zyd(4) monitor mode returns mangled data 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, 11 Mar 2008 17:49:42 -0000 Synopsis: zyd(4) monitor mode returns mangled data Responsible-Changed-From-To: gnats-admin->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Tue Mar 11 17:46:50 UTC 2008 Responsible-Changed-Why: Over to -net http://www.freebsd.org/cgi/query-pr.cgi?pr=121608 From owner-freebsd-net@FreeBSD.ORG Tue Mar 11 20:27:35 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6F6F106566B; Tue, 11 Mar 2008 20:27:35 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE4238FC27; Tue, 11 Mar 2008 20:27:35 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2BKRZRF060829; Tue, 11 Mar 2008 20:27:35 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2BKRZdJ060825; Tue, 11 Mar 2008 20:27:35 GMT (envelope-from gavin) Date: Tue, 11 Mar 2008 20:27:35 GMT Message-Id: <200803112027.m2BKRZdJ060825@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/121624: [em] [regression] Intel em WOL fails after upgrade to FreeBSD-6.3 (from 6.2) 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, 11 Mar 2008 20:27:36 -0000 Old Synopsis: Intel em didn't work anymore afet upgrade to FreeBSD-6.3 (from 6.2) New Synopsis: [em] [regression] Intel em WOL fails after upgrade to FreeBSD-6.3 (from 6.2) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Tue Mar 11 20:25:01 UTC 2008 Responsible-Changed-Why: Wake-on-LAN issue with em driver in 6.3, worked fine in 6.2 http://www.freebsd.org/cgi/query-pr.cgi?pr=121624 From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 01:23:32 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB8F5106566C for ; Wed, 12 Mar 2008 01:23:32 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 7AE498FC24 for ; Wed, 12 Mar 2008 01:23:32 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3086094waf.3 for ; Tue, 11 Mar 2008 18:23:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=8mQra0JHSxz3Py0iRrONnZ9dp41sI2QO+BMVfrvGgpw=; b=oZotu6ZCTB7529soqqFsLCXpVGe9Tq8bO10eYm+Mw7G4XeqDkSVDq+3xwfYMzvjF7YVrhXvOEQ/RISu6Im/fdNcNmMNj8SPngUU+3SqJc+Hpfm6YK3x6wcaj34zu20Yun2xCVlOHyAQLy/900ocaSTOIs/VJAQRZf65Or0vcl2w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=XWsC2/l6j1/71GqGhwCYpYUCxni4IBIU5HVh1l+l5bHxPSY/y3WeNjDg+sfXw1H7djvULO39pxC8fUsxkkgm7BdTh+nAX/zi2TNWD3/he9PTgAsNd9WsCu7wf0KjioKybUnv8eWKagJ5xijD6nvuVmcYYF8FKm1RMah6xJ/Vu2g= Received: by 10.114.170.1 with SMTP id s1mr6130507wae.54.1205283397593; Tue, 11 Mar 2008 17:56:37 -0700 (PDT) Received: by 10.115.15.12 with HTTP; Tue, 11 Mar 2008 17:56:37 -0700 (PDT) Message-ID: Date: Tue, 11 Mar 2008 20:56:37 -0400 From: "d.s. al coda" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_6845_23099961.1205283397588" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 01:23:32 -0000 ------=_Part_6845_23099961.1205283397588 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, We recently upgraded one of our webservers to FreeBSD 7, and we started receiving complaints from some users not able to connect to that server anymore. On top of that, users were saying that the problem only occurred on Windows (at least, the ones who had more than on OS to try it out). After managing to get a user who had the problem running windump, running tcpdump on the new server, and comparing that to the windump & tcpdump output for a "control" user (me) that could connect, we managed to figure out the following: - For the user with this problem, ping works fine, but all TCP connections to the server fail. - The user, trying to connect, sends out a SYN packet, receives no response, and retries a few times until timing out. - The server sees a bunch of SYN packets and responds with SYN-ACK each time. - The issue only seems to arise if the sender has RFC1323 disabled. So, the SYN-ACK is getting lost somewhere. - For the control user (who can connect via TCP just fine), we set the TCP window size and RFC1323 options the same as the user with the problem. - The control user sees the SYN-ACK packet. - We send a connection attempt to one of our other servers, running FreeBSD 5.5, and one to the server running FreeBSD 7. - There is only one notable difference between the responses: the order of the options. - FreeBSD 5.5 has - FreeBSD 7 has (there is of course an aligning nop after the eol, which tcpdump skips) - These options don't appear in this exact configuration when using RFC1323 options. I get a hunch that the users with the problem have a router that erroneously thinks that these options are invalid, or thinks that the some part of byte sequence (e.g. 0204 05b4 0101 0402) is an attack. Just to try it out, I patched tcp_output.c so that the SACK permitted option was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern from ever occuring. Looking through previous versions, I found where the tcp option code had changed, and there used to be a comment about putting SACK permitted last, but I can't tell if it's relevant. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 The one-line patch to tcp_output.c is attached. Sure enough, it fixed the problem. Afterwards, we collected some information about the routers the users who had the problem were using, and while they didn't all have the same manufacturer, several mentioned that their router had a built-in firewall, which, when they disabled it, allowed them to access the server. Does all of this sound reasonable? And if so, would it be worth submitting this patch? I don't know if this particular change in options order was intentional, or just a side-effect of the new code, but it certainly works around an extremely hard-to-diagnose problem. -coda ------=_Part_6845_23099961.1205283397588 Content-Type: text/plain; name=tcp_output.c.patch.txt Content-Transfer-Encoding: base64 X-Attachment-Id: f_fdp6j40n Content-Disposition: attachment; filename=tcp_output.c.patch.txt LS0tIHRjcF9vdXRwdXRfb3JpZy5jICAgMjAwOC0wMy0wMyAwMDoxMzowNi4wMDAwMDAwMDAgLTA1 MDANCisrKyB0Y3Bfb3V0cHV0X25ldy5jICAgIDIwMDgtMDMtMDMgMDA6MTY6MDYuMDAwMDAwMDAw IC0wNTAwDQpAQCAtMTMwNCw3ICsxMzA0LDcgQEANCiAgICAgICAgICAgICAgICAgICAgICAgICpv cHRwKysgPSB0by0+dG9fd3NjYWxlOw0KICAgICAgICAgICAgICAgICAgICAgICAgYnJlYWs7DQog ICAgICAgICAgICAgICAgY2FzZSBUT0ZfU0FDS1BFUk06DQotICAgICAgICAgICAgICAgICAgICAg ICB3aGlsZSAob3B0bGVuICUgMikgew0KKyAgICAgICAgICAgICAgICAgICAgICAgd2hpbGUgKCFv cHRsZW4gfHwgb3B0bGVuICUgNCAhPSAyKSB7DQogICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgIG9wdGxlbiArPSBUQ1BPTEVOX05PUDsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgKm9wdHArKyA9IFRDUE9QVF9OT1A7DQogICAgICAgICAgICAgICAgICAgICAgICB9DQo= ------=_Part_6845_23099961.1205283397588-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 01:53:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EF7E106566C for ; Wed, 12 Mar 2008 01:53:18 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.237]) by mx1.freebsd.org (Postfix) with ESMTP id 517178FC23 for ; Wed, 12 Mar 2008 01:53:18 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so2449230qbd.7 for ; Tue, 11 Mar 2008 18:53:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=YTIlEho1GnQ7yvhHpJpyLT4iYRpAM18zPGlI/Ud4DrQ=; b=rtMO5lzmVaqEFcK8LCCrG5SbYqlzaRp1umdnNZGQZbJxFH3GB0I6BZbRpdu9qesK7wEOw7YG4vBdvJNoqNKl+2UyLIUZXnbwKZumv++EqOP8qrLzP1d9E0itsKl0rLN1mcKZQpauI+ZxNFrOw2HjJZMlv4hCKjeeMf7xEiQpRco= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ia6sHrx9og7Ec9sMpIOQAeQUX/y8Fvz0ZHjGrFu0LYVxSdrpa0gc1yrESprXOOktFQQM7RO1MlirfJJ7P8u78exZH1I86xD58No7XinnujuTvbmL5ujEzpcdjuI6VKKXsZBNRhGt5g5LCEtX16f5HF/smtOh+YJcvQBmAf3y5wQ= Received: by 10.114.178.1 with SMTP id a1mr6683149waf.25.1205286796564; Tue, 11 Mar 2008 18:53:16 -0700 (PDT) Received: by 10.115.22.10 with HTTP; Tue, 11 Mar 2008 18:53:16 -0700 (PDT) Message-ID: Date: Tue, 11 Mar 2008 18:53:16 -0700 From: "Kip Macy" To: "d.s. al coda" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 01:53:18 -0000 Are you running 7.0-RELEASE? What I believe was this issue was a showstopper for it, so I'm surprised to hear of it now. -Kip On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda wrote: > Hi, > We recently upgraded one of our webservers to FreeBSD 7, and we started > receiving complaints from some users not able to connect to that server > anymore. On top of that, users were saying that the problem only occurred on > Windows (at least, the ones who had more than on OS to try it out). > > After managing to get a user who had the problem running windump, running > tcpdump on the new server, and comparing that to the windump & tcpdump > output for a "control" user (me) that could connect, we managed to figure > out the following: > - For the user with this problem, ping works fine, but all TCP connections > to the server fail. > - The user, trying to connect, sends out a SYN packet, receives no response, > and retries a few times until timing out. > - The server sees a bunch of SYN packets and responds with SYN-ACK each > time. > - The issue only seems to arise if the sender has RFC1323 disabled. > > So, the SYN-ACK is getting lost somewhere. > > - For the control user (who can connect via TCP just fine), we set the TCP > window size and RFC1323 options the same as the user with the problem. > - The control user sees the SYN-ACK packet. > - We send a connection attempt to one of our other servers, running FreeBSD > 5.5, and one to the server running FreeBSD 7. > - There is only one notable difference between the responses: the order of > the options. > - FreeBSD 5.5 has > - FreeBSD 7 has (there is of course an aligning nop > after the eol, which tcpdump skips) > - These options don't appear in this exact configuration when using RFC1323 > options. > > I get a hunch that the users with the problem have a router that erroneously > thinks that these options are invalid, or thinks that the some part of byte > sequence (e.g. 0204 05b4 0101 0402) is an attack. > > Just to try it out, I patched tcp_output.c so that the SACK permitted option > was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern from > ever occuring. Looking through previous versions, I found where the tcp > option code had changed, and there used to be a comment about putting SACK > permitted last, but I can't tell if it's relevant. > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 > > The one-line patch to tcp_output.c is attached. > > Sure enough, it fixed the problem. Afterwards, we collected some information > about the routers the users who had the problem were using, and while they > didn't all have the same manufacturer, several mentioned that their router > had a built-in firewall, which, when they disabled it, allowed them to > access the server. > > Does all of this sound reasonable? And if so, would it be worth submitting > this patch? I don't know if this particular change in options order was > intentional, or just a side-effect of the new code, but it certainly works > around an extremely hard-to-diagnose problem. > > -coda > > _______________________________________________ > 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 Wed Mar 12 02:48:40 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 299D71065671 for ; Wed, 12 Mar 2008 02:48:40 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.236]) by mx1.freebsd.org (Postfix) with ESMTP id BC7588FC1E for ; Wed, 12 Mar 2008 02:48:39 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so2465856qbd.7 for ; Tue, 11 Mar 2008 19:48:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=iC+1dFjhIhqYrQoo4akApCkIXpLS+On4Um9XbXZU8ME=; b=UwhAHmOtoIsdVIdfheAXbuXXyLxvaGXf6zKG720l1mGvJNbJsibopIMErLf1jEIDg4HN3YLqBHM/N/HaKlgEL+bCMSMRHal728M+Po5qfA5i1bOu87WCETq4OPhr5qrxCpkb3No/mAXFQKP4c5euH8tsoc6ScBzbc8mAFoMa56w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=vdimFkLmIawyMrXwG8js2DQhGtzk1TXclLwSZkyLGD8t07YtYN2sqj533wrznzYu7c9luyoB1U91xnOw5ZJDk4PLLQQ1aX8RPO2ZLPvDoJ8Ulun0ayz1g6aRkt+PthAY7MVbHz65Gu4zk6Rn7C5D7pemmvcCQkAXCSg3GAElcUw= Received: by 10.114.156.1 with SMTP id d1mr6008752wae.120.1205290118198; Tue, 11 Mar 2008 19:48:38 -0700 (PDT) Received: by 10.115.15.12 with HTTP; Tue, 11 Mar 2008 19:48:38 -0700 (PDT) Message-ID: Date: Tue, 11 Mar 2008 22:48:38 -0400 From: "d.s. al coda" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 02:48:40 -0000 On 3/11/08, Kip Macy wrote: > Are you running 7.0-RELEASE? What I believe was this issue was a > showstopper for it, so I'm surprised to hear of it now. > > -Kip Yes, we are running 7.0-RELEASE. -coda On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda > wrote: > > Hi, > > We recently upgraded one of our webservers to FreeBSD 7, and we started > > receiving complaints from some users not able to connect to that server > > anymore. On top of that, users were saying that the problem only > occurred on > > Windows (at least, the ones who had more than on OS to try it out). > > > > After managing to get a user who had the problem running windump, > running > > tcpdump on the new server, and comparing that to the windump & tcpdump > > output for a "control" user (me) that could connect, we managed to > figure > > out the following: > > - For the user with this problem, ping works fine, but all TCP > connections > > to the server fail. > > - The user, trying to connect, sends out a SYN packet, receives no > response, > > and retries a few times until timing out. > > - The server sees a bunch of SYN packets and responds with SYN-ACK each > > time. > > - The issue only seems to arise if the sender has RFC1323 disabled. > > > > So, the SYN-ACK is getting lost somewhere. > > > > - For the control user (who can connect via TCP just fine), we set the > TCP > > window size and RFC1323 options the same as the user with the problem. > > - The control user sees the SYN-ACK packet. > > - We send a connection attempt to one of our other servers, running > FreeBSD > > 5.5, and one to the server running FreeBSD 7. > > - There is only one notable difference between the responses: the order > of > > the options. > > - FreeBSD 5.5 has > > - FreeBSD 7 has (there is of course an aligning > nop > > after the eol, which tcpdump skips) > > - These options don't appear in this exact configuration when using > RFC1323 > > options. > > > > I get a hunch that the users with the problem have a router that > erroneously > > thinks that these options are invalid, or thinks that the some part of > byte > > sequence (e.g. 0204 05b4 0101 0402) is an attack. > > > > Just to try it out, I patched tcp_output.c so that the SACK permitted > option > > was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern > from > > ever occuring. Looking through previous versions, I found where the > tcp > > option code had changed, and there used to be a comment about putting > SACK > > permitted last, but I can't tell if it's relevant. > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 > > > > The one-line patch to tcp_output.c is attached. > > > > Sure enough, it fixed the problem. Afterwards, we collected some > information > > about the routers the users who had the problem were using, and while > they > > didn't all have the same manufacturer, several mentioned that their > router > > had a built-in firewall, which, when they disabled it, allowed them to > > access the server. > > > > Does all of this sound reasonable? And if so, would it be worth > submitting > > this patch? I don't know if this particular change in options order was > > intentional, or just a side-effect of the new code, but it certainly > works > > around an extremely hard-to-diagnose problem. > > > > -coda > > > > _______________________________________________ > > 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 Wed Mar 12 04:03:45 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C80C106566B; Wed, 12 Mar 2008 04:03:45 +0000 (UTC) (envelope-from weongyo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 100928FC14; Wed, 12 Mar 2008 04:03:45 +0000 (UTC) (envelope-from weongyo@FreeBSD.org) Received: from freefall.freebsd.org (weongyo@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2C43ig6002566; Wed, 12 Mar 2008 04:03:44 GMT (envelope-from weongyo@freefall.freebsd.org) Received: (from weongyo@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2C43i57002562; Wed, 12 Mar 2008 04:03:44 GMT (envelope-from weongyo) Date: Wed, 12 Mar 2008 04:03:44 GMT Message-Id: <200803120403.m2C43i57002562@freefall.freebsd.org> To: weongyo@FreeBSD.org, freebsd-net@FreeBSD.org, weongyo@FreeBSD.org From: weongyo@FreeBSD.org Cc: Subject: Re: kern/121608: zyd(4) monitor mode returns mangled data 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, 12 Mar 2008 04:03:45 -0000 Synopsis: zyd(4) monitor mode returns mangled data Responsible-Changed-From-To: freebsd-net->weongyo Responsible-Changed-By: weongyo Responsible-Changed-When: Wed Mar 12 04:02:50 UTC 2008 Responsible-Changed-Why: Grab this PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=121608 From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 06:50:18 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3850A106566B; Wed, 12 Mar 2008 06:50:18 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0384C8FC12; Wed, 12 Mar 2008 06:50:18 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2C6oH51017644; Wed, 12 Mar 2008 06:50:17 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2C6oH88017640; Wed, 12 Mar 2008 06:50:17 GMT (envelope-from remko) Date: Wed, 12 Mar 2008 06:50:17 GMT Message-Id: <200803120650.m2C6oH88017640@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-net@FreeBSD.org, darrenr@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/121534: [ipl] [nat] FreeBSD Release 6.3 Kernel Trap 12: 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, 12 Mar 2008 06:50:18 -0000 Synopsis: [ipl] [nat] FreeBSD Release 6.3 Kernel Trap 12: Responsible-Changed-From-To: freebsd-net->darrenr Responsible-Changed-By: remko Responsible-Changed-When: Wed Mar 12 06:50:05 UTC 2008 Responsible-Changed-Why: Darren can you have a look at this? http://www.freebsd.org/cgi/query-pr.cgi?pr=121534 From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 08:48:38 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1FD41065672 for ; Wed, 12 Mar 2008 08:48:38 +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 10FBF8FC33 for ; Wed, 12 Mar 2008 08:48:37 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 12583 invoked from network); 12 Mar 2008 08:00:56 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Mar 2008 08:00:56 -0000 Message-ID: <47D798E8.3090103@freebsd.org> Date: Wed, 12 Mar 2008 09:48:40 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Kip Macy References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 08:48:38 -0000 Kip Macy wrote: > Are you running 7.0-RELEASE? What I believe was this issue was a > showstopper for it, so I'm surprised to hear of it now. No, this is a different issue and not really the fault of TCP but of certain cable modem vendors with broken code in their devices. FreeBSD is fully compliant to the spec. Sibly committed a workaround for this issue to -current and I expect the MFC to RELENG_7 and RELENG_7_0 soon. -- Andre > -Kip > > On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda wrote: >> Hi, >> We recently upgraded one of our webservers to FreeBSD 7, and we started >> receiving complaints from some users not able to connect to that server >> anymore. On top of that, users were saying that the problem only occurred on >> Windows (at least, the ones who had more than on OS to try it out). >> >> After managing to get a user who had the problem running windump, running >> tcpdump on the new server, and comparing that to the windump & tcpdump >> output for a "control" user (me) that could connect, we managed to figure >> out the following: >> - For the user with this problem, ping works fine, but all TCP connections >> to the server fail. >> - The user, trying to connect, sends out a SYN packet, receives no response, >> and retries a few times until timing out. >> - The server sees a bunch of SYN packets and responds with SYN-ACK each >> time. >> - The issue only seems to arise if the sender has RFC1323 disabled. >> >> So, the SYN-ACK is getting lost somewhere. >> >> - For the control user (who can connect via TCP just fine), we set the TCP >> window size and RFC1323 options the same as the user with the problem. >> - The control user sees the SYN-ACK packet. >> - We send a connection attempt to one of our other servers, running FreeBSD >> 5.5, and one to the server running FreeBSD 7. >> - There is only one notable difference between the responses: the order of >> the options. >> - FreeBSD 5.5 has >> - FreeBSD 7 has (there is of course an aligning nop >> after the eol, which tcpdump skips) >> - These options don't appear in this exact configuration when using RFC1323 >> options. >> >> I get a hunch that the users with the problem have a router that erroneously >> thinks that these options are invalid, or thinks that the some part of byte >> sequence (e.g. 0204 05b4 0101 0402) is an attack. >> >> Just to try it out, I patched tcp_output.c so that the SACK permitted option >> was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern from >> ever occuring. Looking through previous versions, I found where the tcp >> option code had changed, and there used to be a comment about putting SACK >> permitted last, but I can't tell if it's relevant. >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 >> >> The one-line patch to tcp_output.c is attached. >> >> Sure enough, it fixed the problem. Afterwards, we collected some information >> about the routers the users who had the problem were using, and while they >> didn't all have the same manufacturer, several mentioned that their router >> had a built-in firewall, which, when they disabled it, allowed them to >> access the server. >> >> Does all of this sound reasonable? And if so, would it be worth submitting >> this patch? I don't know if this particular change in options order was >> intentional, or just a side-effect of the new code, but it certainly works >> around an extremely hard-to-diagnose problem. >> >> -coda >> >> _______________________________________________ >> 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" >> > _______________________________________________ > 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 Wed Mar 12 08:49:14 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08EA21065675 for ; Wed, 12 Mar 2008 08:49:14 +0000 (UTC) (envelope-from rizzojake@gmail.com) Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.154]) by mx1.freebsd.org (Postfix) with ESMTP id C140B8FC38 for ; Wed, 12 Mar 2008 08:49:13 +0000 (UTC) (envelope-from rizzojake@gmail.com) Received: by po-out-1718.google.com with SMTP id y22so4645860pof.3 for ; Wed, 12 Mar 2008 01:49:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=jw/lL02m0hwHN/58emHntWGd1KM35BuQ9hZCurtaaK0=; b=su+X8Uvk5lGF/4slyM7iRpPXnucGq0wo/107pyXQZZRLlTW35HMWo5w8dzYb2QmotTwybTXaq5Ok78lnvVZ3koxXpqaQF4Czx8K2TV54ia8ku03nUP7I4nnQU1CLLNZwKxJwFqow2GzpQtxSIbsGMjnDTXuA9u7aWEHLR/zbLFw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pCl5vvNPDTObD3DLUSoahCv8XmwLfsuUbh4+GcIXPKoKdrcrd9nmMo5D1GKBkABIvvJ0kiXIPjSRVZtxOPhMXygWM8zDKN4JL+cpZ9yuwyi+6AJEwJ6NtAGiOb6JYA+28F/aQZZ0qLV5N6HFpPz0p/NL0xjH/wCR8CWuACgSH1I= Received: by 10.141.171.6 with SMTP id y6mr4960415rvo.84.1205311752739; Wed, 12 Mar 2008 01:49:12 -0700 (PDT) Received: by 10.141.22.11 with HTTP; Wed, 12 Mar 2008 01:49:12 -0700 (PDT) Message-ID: Date: Wed, 12 Mar 2008 08:49:12 +0000 From: "Jake Rizzo" To: "d.s. al coda" In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Kip Macy , freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 08:49:14 -0000 Exact same problem that i'm having. I confirmed it exists in 7.0 only since downgrading one of our servers back to 6.3 stable allowed the same clients to connect again. This seems to work for us as a workaround: sysctl net.inet.tcp.sack.enable=0 On 3/12/08, d.s. al coda wrote: > > On 3/11/08, Kip Macy wrote: > > > Are you running 7.0-RELEASE? What I believe was this issue was a > > showstopper for it, so I'm surprised to hear of it now. > > > > -Kip > > > > > Yes, we are running 7.0-RELEASE. > > -coda > > > On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda > > wrote: > > > Hi, > > > We recently upgraded one of our webservers to FreeBSD 7, and we > started > > > receiving complaints from some users not able to connect to that > server > > > anymore. On top of that, users were saying that the problem only > > occurred on > > > Windows (at least, the ones who had more than on OS to try it out). > > > > > > After managing to get a user who had the problem running windump, > > running > > > tcpdump on the new server, and comparing that to the windump & > tcpdump > > > output for a "control" user (me) that could connect, we managed to > > figure > > > out the following: > > > - For the user with this problem, ping works fine, but all TCP > > connections > > > to the server fail. > > > - The user, trying to connect, sends out a SYN packet, receives no > > response, > > > and retries a few times until timing out. > > > - The server sees a bunch of SYN packets and responds with SYN-ACK > each > > > time. > > > - The issue only seems to arise if the sender has RFC1323 disabled. > > > > > > So, the SYN-ACK is getting lost somewhere. > > > > > > - For the control user (who can connect via TCP just fine), we set > the > > TCP > > > window size and RFC1323 options the same as the user with the > problem. > > > - The control user sees the SYN-ACK packet. > > > - We send a connection attempt to one of our other servers, running > > FreeBSD > > > 5.5, and one to the server running FreeBSD 7. > > > - There is only one notable difference between the responses: the > order > > of > > > the options. > > > - FreeBSD 5.5 has > > > - FreeBSD 7 has (there is of course an > aligning > > nop > > > after the eol, which tcpdump skips) > > > - These options don't appear in this exact configuration when using > > RFC1323 > > > options. > > > > > > I get a hunch that the users with the problem have a router that > > erroneously > > > thinks that these options are invalid, or thinks that the some part > of > > byte > > > sequence (e.g. 0204 05b4 0101 0402) is an attack. > > > > > > Just to try it out, I patched tcp_output.c so that the SACK permitted > > option > > > was aligned on a 4-byte boundary, preventing the "sackOK, eol" > pattern > > from > > > ever occuring. Looking through previous versions, I found where the > > tcp > > > option code had changed, and there used to be a comment about putting > > SACK > > > permitted last, but I can't tell if it's relevant. > > > > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 > > > > > > The one-line patch to tcp_output.c is attached. > > > > > > Sure enough, it fixed the problem. Afterwards, we collected some > > information > > > about the routers the users who had the problem were using, and while > > they > > > didn't all have the same manufacturer, several mentioned that their > > router > > > had a built-in firewall, which, when they disabled it, allowed them > to > > > access the server. > > > > > > Does all of this sound reasonable? And if so, would it be worth > > submitting > > > this patch? I don't know if this particular change in options order > was > > > intentional, or just a side-effect of the new code, but it certainly > > works > > > around an extremely hard-to-diagnose problem. > > > > > > -coda > > > > > > _______________________________________________ > > > 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 > " > > > > > > _______________________________________________ > 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 Wed Mar 12 10:49:47 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E86CD1065672; Wed, 12 Mar 2008 10:49:46 +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 B3BD98FC2B; Wed, 12 Mar 2008 10:49:46 +0000 (UTC) (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 6D19746B03; Wed, 12 Mar 2008 06:49:46 -0400 (EDT) Date: Wed, 12 Mar 2008 10:49:46 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andre Oppermann In-Reply-To: <47D798E8.3090103@freebsd.org> Message-ID: <20080312104812.V29518@fledge.watson.org> References: <47D798E8.3090103@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kip Macy , "d.s. al coda" , re@FreeBSD.org, freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 10:49:47 -0000 On Wed, 12 Mar 2008, Andre Oppermann wrote: > Kip Macy wrote: >> Are you running 7.0-RELEASE? What I believe was this issue was a >> showstopper for it, so I'm surprised to hear of it now. > > No, this is a different issue and not really the fault of TCP but of certain > cable modem vendors with broken code in their devices. FreeBSD is fully > compliant to the spec. Sibly committed a workaround for this issue to > -current and I expect the MFC to RELENG_7 and RELENG_7_0 soon. Sounds like a potential errata patch candidate. re@ added to the CC line. We should probably wait a couple of weeks to let it settle out, as well as see what other surprises with TCP are in store for us that we might want to fix in the same patch. Robert N M Watson Computer Laboratory University of Cambridge > > -- > Andre > >> -Kip >> >> On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda >> wrote: >>> Hi, >>> We recently upgraded one of our webservers to FreeBSD 7, and we started >>> receiving complaints from some users not able to connect to that server >>> anymore. On top of that, users were saying that the problem only occurred >>> on >>> Windows (at least, the ones who had more than on OS to try it out). >>> >>> After managing to get a user who had the problem running windump, running >>> tcpdump on the new server, and comparing that to the windump & tcpdump >>> output for a "control" user (me) that could connect, we managed to figure >>> out the following: >>> - For the user with this problem, ping works fine, but all TCP >>> connections >>> to the server fail. >>> - The user, trying to connect, sends out a SYN packet, receives no >>> response, >>> and retries a few times until timing out. >>> - The server sees a bunch of SYN packets and responds with SYN-ACK each >>> time. >>> - The issue only seems to arise if the sender has RFC1323 disabled. >>> >>> So, the SYN-ACK is getting lost somewhere. >>> >>> - For the control user (who can connect via TCP just fine), we set the >>> TCP >>> window size and RFC1323 options the same as the user with the problem. >>> - The control user sees the SYN-ACK packet. >>> - We send a connection attempt to one of our other servers, running >>> FreeBSD >>> 5.5, and one to the server running FreeBSD 7. >>> - There is only one notable difference between the responses: the order >>> of >>> the options. >>> - FreeBSD 5.5 has >>> - FreeBSD 7 has (there is of course an aligning >>> nop >>> after the eol, which tcpdump skips) >>> - These options don't appear in this exact configuration when using >>> RFC1323 >>> options. >>> >>> I get a hunch that the users with the problem have a router that >>> erroneously >>> thinks that these options are invalid, or thinks that the some part of >>> byte >>> sequence (e.g. 0204 05b4 0101 0402) is an attack. >>> >>> Just to try it out, I patched tcp_output.c so that the SACK permitted >>> option >>> was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern >>> from >>> ever occuring. Looking through previous versions, I found where the tcp >>> option code had changed, and there used to be a comment about putting >>> SACK >>> permitted last, but I can't tell if it's relevant. >>> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 >>> >>> The one-line patch to tcp_output.c is attached. >>> >>> Sure enough, it fixed the problem. Afterwards, we collected some >>> information >>> about the routers the users who had the problem were using, and while >>> they >>> didn't all have the same manufacturer, several mentioned that their >>> router >>> had a built-in firewall, which, when they disabled it, allowed them to >>> access the server. >>> >>> Does all of this sound reasonable? And if so, would it be worth >>> submitting >>> this patch? I don't know if this particular change in options order was >>> intentional, or just a side-effect of the new code, but it certainly >>> works >>> around an extremely hard-to-diagnose problem. >>> >>> -coda >>> >>> _______________________________________________ >>> 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" >>> >> _______________________________________________ >> 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" >> >> > > _______________________________________________ > 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 Wed Mar 12 12:16:28 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D92321065676 for ; Wed, 12 Mar 2008 12:16:28 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 0467D8FC26 for ; Wed, 12 Mar 2008 12:16:27 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 50684 invoked by uid 98); 12 Mar 2008 11:49:45 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.039869 secs); 12 Mar 2008 11:49:45 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.039869 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 12 Mar 2008 11:49:45 -0000 Message-ID: <47D7C34E.8060805@zirakzigil.org> Date: Wed, 12 Mar 2008 12:49:34 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: VLAN trunking and fragmentation 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, 12 Mar 2008 12:16:29 -0000 I need to configure ports to work with multiple vlan on my redundant freebsd router/firewall. In order to setup my test environment I have 2 freebsd boxes 7.0 STABLE amd64 both with gigabit realtek (re0). According to what the man says, these cards should support vlan in hardware. These PCs are connected to a dell 48 port managed layer-3 switch on port 1 and 2. On the dell CLI I configure the vlans: --------------------------- enable configure vlan database vlan 10 exit interface vlan 10 name testvlan exit interface ethernet 1/g1 switchport mode trunk switchport trunk allowed vlan add 10 exit interface ethernet 1/g2 switchport mode trunk switchport trunk allowed vlan add 10 exit --------------------------- On both PC I have configured a vlan interface like this: from /etc/rc.conf --------------------------- ifconfig_re0="inet 192.168.60.1 netmask 255.255.255.0" cloned_interfaces="vlan0" ifconfig_vlan0="inet 192.168.100.1 netmask 255.255.255.0 vlan 10 vlandev re0" --------------------------- same on the other PC, but with physical address = 192.168.60.2 and virtual address 192.168.100.2 When I now try to ping from one machine to the other there is no problem: --------------------------- # ping -c 1 192.168.100.2 PING 192.168.100.2 (192.168.100.2): 56 data bytes 64 bytes from 192.168.100.2: icmp_seq=0 ttl=64 time=0.108 ms --- 192.168.100.2 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.108/0.108/0.108/0.000 ms --------------------------- The problems start when I send a packet which is bigger than 1472 bytes: --------------------------- ping -c 1 -s 1473 192.168.100.2 --------------------------- The packet is fragmented as it should, but there seems to be some problem with the checksum computation. --------------------------- # on PC 192.168.100.1 tcpdump -i re0 -n -vvv not stp 13:33:37.789615 IP (tos 0x0, ttl 64, id 809, offset 0, flags [+], proto ICMP (1), length 1500, bad cksum 0 (->8a4)!) 192.168.100.1 > 192.168.100.2: ICMP echo request, id 31748, seq 0, length 1480 13:33:37.789622 IP (tos 0x0, ttl 64, id 809, offset 1480, flags [none], proto ICMP (1), length 21, bad cksum 0 (->2db2)!) 192.168.100.1 > 192.168.100.2: icmp #on PC 192.168.100.2 tcpdump -i re0 -n -vvv not stp 13:32:49.038581 IP (tos 0x0, ttl 64, id 809, offset 1480, flags [none], proto ICMP (1), length 21) 192.168.100.1 > 192.168.100.2: icmp --------------------------- I'm told that this same configuration works under linux. It seems to me this could be a bug of the vlan stack under freebsd... Thanks in advance for any workaround / quick patch to solve this issue. From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 14:30:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BB4F1065677 for ; Wed, 12 Mar 2008 14:30:11 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id ABB328FC2E for ; Wed, 12 Mar 2008 14:30:10 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 76243 invoked from network); 12 Mar 2008 14:30:08 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 12 Mar 2008 14:30:08 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 12 Mar 2008 09:30:05 -0500 (CDT) From: Mike Silbersack To: "d.s. al coda" In-Reply-To: Message-ID: <20080312092907.E54510@odysseus.silby.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 14:30:11 -0000 On Tue, 11 Mar 2008, d.s. al coda wrote: > Hi, > We recently upgraded one of our webservers to FreeBSD 7, and we started > receiving complaints from some users not able to connect to that server > anymore. On top of that, users were saying that the problem only occurred on > Windows (at least, the ones who had more than on OS to try it out). This sounds like the issue Jake Rizzo has been describing. The tcp_var.h change I put in a few days ago only seems to help when timestamps are enabled. I'll try to sit down and read through this e-mail tonight. -Mike From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 14:50:08 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BDCD1065676 for ; Wed, 12 Mar 2008 14:50:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id D1B348FC19 for ; Wed, 12 Mar 2008 14:50:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id ACDD141C756; Wed, 12 Mar 2008 15:50:05 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id ZpHEWXTtui7M; Wed, 12 Mar 2008 15:50:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 4620041C752; Wed, 12 Mar 2008 15:50:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 29CDE44487F; Wed, 12 Mar 2008 14:49:47 +0000 (UTC) Date: Wed, 12 Mar 2008 14:49:46 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: "d.s. al coda" In-Reply-To: Message-ID: <20080312144207.P50685@maildrop.int.zabbadoz.net> References: X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 14:50:08 -0000 On Tue, 11 Mar 2008, d.s. al coda wrote: > - FreeBSD 7 has (there is of course an aligning nop > after the eol, which tcpdump skips) Which is a bug (the nop after the EOL) that I recently fixed in HEAD. I am still curious to know if it's only ordering or the invalid padding or both that keeps clients from connecting. The problem is getting hands on such a problematic "client". I still cannot see why someone would drop because of option ordering but I could see why someone would drop because of the wrong padding which is violating the TCP RFC. Of course other exmaples seem to have shown that it was option ordering that made peers freak out and drop the packet. > - These options don't appear in this exact configuration when using RFC1323 > options. > > I get a hunch that the users with the problem have a router that erroneously > thinks that these options are invalid, or thinks that the some part of byte > sequence (e.g. 0204 05b4 0101 0402) is an attack. > > Just to try it out, I patched tcp_output.c so that the SACK permitted option > was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern from > ever occuring. Looking through previous versions, I found where the tcp > option code had changed, and there used to be a comment about putting SACK > permitted last, but I can't tell if it's relevant. > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 > > The one-line patch to tcp_output.c is attached. > > Sure enough, it fixed the problem. Afterwards, we collected some information That of course seems to have dropped the need for padding after a possible EOL (if there is no EOL anymore) hiding the second problem. I wonder if you would have the resources to try this patch (on an unpatched kernel) http://docs.freebsd.org/cgi/mid.cgi?200803091326.m29DQoCI095152 and find out if one of the formerly not working users can connect again. As said before this might not be the case and it might be option alignment/ordering but that would rule out the padding problem for us. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 17:56:00 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFFF11065670 for ; Wed, 12 Mar 2008 17:56:00 +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 8B1378FC15 for ; Wed, 12 Mar 2008 17:56:00 +0000 (UTC) (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 6A15246B96 for ; Wed, 12 Mar 2008 13:55:59 -0400 (EDT) Date: Wed, 12 Mar 2008 17:55:59 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: net@FreeBSD.org Message-ID: <20080312175151.V47697@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: FYI: inpcb/pcbinfo mutex -> rwlock at some point in the mid-distant future 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, 12 Mar 2008 17:56:00 -0000 FYI: Kris Kennaway and I have been working on diagnosing and addressing network stack contention and scheduling issues for high performance DNS serving with nsd and bind9. One of the changes in the pipeline is converting from using a mutex to protect the pcbinfo and inpcb data structures to an rwlock, so that UDP, which doesn't require exclusion for either of those structures in a number of key cases, doesn't have to experience as high contention. TCP would continue to use them only exclusively [for now]. This is a heads up that this change will likely end up in HEAD in the next month or two, but we're still working through some issues. This may well be something that can be MFC'd as rwlocks are intentionally fairly layout compatible with mutexes, and these locks and the data structures they protect are not considered "public" structures from the perspective of most kernel modules (although there are potentially issues with firewalls that reach "up" the stack to look at th connection table). One of those issues is that we need to demonstrate to ourselves that exclusive access contention is managed as well with rwlocks as with sleep mutexes, as these locks would continue to be fairly highly contended in TCP. The other issue is that rwlocks don't support full priority propagation for reader access, although Jeff Roberson has recently improved fairness to writers with many readers. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 18:49:12 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC9BD1065671 for ; Wed, 12 Mar 2008 18:49:12 +0000 (UTC) (envelope-from mattjreimer@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8F48FC14 for ; Wed, 12 Mar 2008 18:49:12 +0000 (UTC) (envelope-from mattjreimer@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so4452146pyb.10 for ; Wed, 12 Mar 2008 11:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=8yVIuzUXZp5W7DUQXq8T/91Jo8rLJA8ZhKJE8dDxbls=; b=SvmAaE3XWKO4oD5vntBQkqw4QASWywo15pm8PLkSjxWvY2JgWbHrLnr72LEbd77geIgJEWaQlZZU2yJGRMCJ5IIsaNxxG5FuKNtzKDO+FcLMadninBh9uXdfyDY1v5UJhxn/Zmekr0dIuDmZWmNhEJhnfQkPh/G4b84AgumDoQE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KnUoLc3iW3N6FQg8bIk+9UWRVe7AUAnfhVCV3o4ONuOYseIxFD7ZouoTZFAAoVhHv0ZdITjsEF7byCuSSoOzQzxa9TME8/XKOG5C5lYhSM6Vn6dOzjcHJ+APCnZsCF9WA+POfZD0UUUcPav+TS6v/iJlwD/I7IjxxboXj/pSagk= Received: by 10.35.110.13 with SMTP id n13mr13458629pym.43.1205346257355; Wed, 12 Mar 2008 11:24:17 -0700 (PDT) Received: by 10.35.58.11 with HTTP; Wed, 12 Mar 2008 11:24:09 -0700 (PDT) Message-ID: Date: Wed, 12 Mar 2008 11:24:09 -0700 From: "Matt Reimer" To: "d.s. al coda" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 18:49:12 -0000 On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda wrote: > Hi, > We recently upgraded one of our webservers to FreeBSD 7, and we started > receiving complaints from some users not able to connect to that server > anymore. On top of that, users were saying that the problem only occurred on > Windows (at least, the ones who had more than on OS to try it out). ... Me too: I saw this exact problem with RELENG_7 a month or so ago, and worked around it by disabling SACK. Matt From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 19:01:00 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 878511065678 for ; Wed, 12 Mar 2008 19:01:00 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.182]) by mx1.freebsd.org (Postfix) with ESMTP id 41E2C8FC21 for ; Wed, 12 Mar 2008 19:00:59 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so1692498ele.12 for ; Wed, 12 Mar 2008 12:00:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Tx+Hm3noJymkLtTBTa3ozYGZ6WjZ84WtpT47trVEFSk=; b=W5C5FPw5XsfgirUjq9KbwpQZBXSr1bmgBPuhjhB2JKhmt+QtStaxS4gB55JQRESYyd91C7o6bOvhIOqH/9JakJjlZ27PbHcr/QsktDAMCkfdX7S4awq0KZ+eNnlt1GDsxw8ZFjefBqv/L4masgQj6U3J7n97n3KlGjsWD5pdTwk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gDqE55PDr4vPp/2nlfy444DrQZ/bkUMq1wVzLknNFRuY5Ca87y4JEYuigdhfwfOjzymNK+VXNCcEXN6OR5badCDTU3mBhYVR8TGXGsG8vvJNffXzEt0C6ZBQs8vrcU82wRh61r45TZg5oozDuORwGnig8xuSf6EFhu6/MrJLB2g= Received: by 10.114.120.1 with SMTP id s1mr4839541wac.82.1205348457524; Wed, 12 Mar 2008 12:00:57 -0700 (PDT) Received: by 10.115.22.10 with HTTP; Wed, 12 Mar 2008 12:00:57 -0700 (PDT) Message-ID: Date: Wed, 12 Mar 2008 12:00:57 -0700 From: "Kip Macy" To: "Andre Oppermann" In-Reply-To: <47D798E8.3090103@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47D798E8.3090103@freebsd.org> Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 19:01:00 -0000 On Wed, Mar 12, 2008 at 1:48 AM, Andre Oppermann wrote: > Kip Macy wrote: > > Are you running 7.0-RELEASE? What I believe was this issue was a > > showstopper for it, so I'm surprised to hear of it now. > > No, this is a different issue and not really the fault of TCP but > of certain cable modem vendors with broken code in their devices. > FreeBSD is fully compliant to the spec. Sibly committed a workaround > for this issue to -current and I expect the MFC to RELENG_7 and > RELENG_7_0 soon. We know your opinion Andre. Most people don't care whose fault it is, they just want it to work. I didn't realized that Silby's change hadn't made it in to the release. -Kip > > -- > Andre > > > > > -Kip > > > > On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda wrote: > >> Hi, > >> We recently upgraded one of our webservers to FreeBSD 7, and we started > >> receiving complaints from some users not able to connect to that server > >> anymore. On top of that, users were saying that the problem only occurred on > >> Windows (at least, the ones who had more than on OS to try it out). > >> > >> After managing to get a user who had the problem running windump, running > >> tcpdump on the new server, and comparing that to the windump & tcpdump > >> output for a "control" user (me) that could connect, we managed to figure > >> out the following: > >> - For the user with this problem, ping works fine, but all TCP connections > >> to the server fail. > >> - The user, trying to connect, sends out a SYN packet, receives no response, > >> and retries a few times until timing out. > >> - The server sees a bunch of SYN packets and responds with SYN-ACK each > >> time. > >> - The issue only seems to arise if the sender has RFC1323 disabled. > >> > >> So, the SYN-ACK is getting lost somewhere. > >> > >> - For the control user (who can connect via TCP just fine), we set the TCP > >> window size and RFC1323 options the same as the user with the problem. > >> - The control user sees the SYN-ACK packet. > >> - We send a connection attempt to one of our other servers, running FreeBSD > >> 5.5, and one to the server running FreeBSD 7. > >> - There is only one notable difference between the responses: the order of > >> the options. > >> - FreeBSD 5.5 has > >> - FreeBSD 7 has (there is of course an aligning nop > >> after the eol, which tcpdump skips) > >> - These options don't appear in this exact configuration when using RFC1323 > >> options. > >> > >> I get a hunch that the users with the problem have a router that erroneously > >> thinks that these options are invalid, or thinks that the some part of byte > >> sequence (e.g. 0204 05b4 0101 0402) is an attack. > >> > >> Just to try it out, I patched tcp_output.c so that the SACK permitted option > >> was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern from > >> ever occuring. Looking through previous versions, I found where the tcp > >> option code had changed, and there used to be a comment about putting SACK > >> permitted last, but I can't tell if it's relevant. > >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 > >> > >> The one-line patch to tcp_output.c is attached. > >> > >> Sure enough, it fixed the problem. Afterwards, we collected some information > >> about the routers the users who had the problem were using, and while they > >> didn't all have the same manufacturer, several mentioned that their router > >> had a built-in firewall, which, when they disabled it, allowed them to > >> access the server. > >> > >> Does all of this sound reasonable? And if so, would it be worth submitting > >> this patch? I don't know if this particular change in options order was > >> intentional, or just a side-effect of the new code, but it certainly works > >> around an extremely hard-to-diagnose problem. > >> > >> -coda > >> > >> _______________________________________________ > >> 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" > >> > > _______________________________________________ > > 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 Wed Mar 12 19:55:49 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF7031065676 for ; Wed, 12 Mar 2008 19:55:49 +0000 (UTC) (envelope-from sean@chittenden.org) Received: from davie.textdrive.com (davie.textdrive.com [207.7.108.101]) by mx1.freebsd.org (Postfix) with ESMTP id A32858FC1F for ; Wed, 12 Mar 2008 19:55:49 +0000 (UTC) (envelope-from sean@chittenden.org) Received: from [192.168.255.187] (60.ten-net.org [71.6.14.60]) by davie.textdrive.com (Postfix) with ESMTP id 6D57ACA2D8; Wed, 12 Mar 2008 19:38:13 +0000 (GMT) Message-Id: From: Sean Chittenden To: Giulio Ferro In-Reply-To: <47D7C34E.8060805@zirakzigil.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 12 Mar 2008 12:38:06 -0700 References: <47D7C34E.8060805@zirakzigil.org> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 19:55:49 -0000 > interface ethernet 1/g1 > switchport mode trunk > switchport trunk allowed vlan add 10 > exit I think this is an issue with default VLAN membership. I have this config running on *hundreds* of servers without issue. Since Dell should be a cisco rip-off, on your switchport config, throw in (haven't tested this, on dell's CLI): switchport trunk encapsulation dot1q then change your ifconfig foo to: cloned_interfaces="vlan10 vlan11" ifconfig_re0="media 100baseTX mediaopt full-duplex" ifconfig_vlan10="vlan 10 vlandev re0" ifconfig_vlan10_alias0="inet 192.168.60.1 netmask 255.255.255.0" ifconfig_vlan11="vlan 11 valndev re0" ifconfig_vlan11_alias0="inet 192.168.100.1 netmask 255.255.255.0" FWIW, I think you'll find fewer gray hairs if you stick to the convention of using a vlan device that has the same VLAN tag. You may be able to have a default VLAN, but I consider it poor practice to rely on default VLAN membership. There are good reasons to have a default VLAN configured, but this doesn't sound like one of those cases. Stick with explicit VLAN tagging on your servers and you can't go wrong. -sc -- Sean Chittenden sean@chittenden.org http://sean.chittenden.org/ From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 20:01:33 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AC2C1065688 for ; Wed, 12 Mar 2008 20:01:33 +0000 (UTC) (envelope-from daniel@dgnetwork.com.br) Received: from mail.mastercabo.com.br (mail.mastercabo.com.br [200.179.179.14]) by mx1.freebsd.org (Postfix) with SMTP id AC0888FC1F for ; Wed, 12 Mar 2008 20:01:32 +0000 (UTC) (envelope-from daniel@dgnetwork.com.br) Received: (qmail 38372 invoked by uid 1008); 12 Mar 2008 20:01:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.6-unknown (2006-10-03) on srvmail2 X-Spam-Level: X-Spam-Status: No, score=-1.7 required=4.7 tests=AWL,BAYES_00 autolearn=ham version=3.1.6-unknown Received: from unknown (HELO ?10.0.0.10?) (daniel@dgnetwork.com.br@200.243.216.36) by mail.mastercabo.com.br with SMTP; 12 Mar 2008 20:01:25 -0000 Message-ID: <47D834AE.8080301@dgnetwork.com.br> Date: Wed, 12 Mar 2008 16:53:18 -0300 From: =?ISO-8859-1?Q?Daniel_Dias_Gon=E7alves?= Organization: DGNET Network Solutions User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-smp@freebsd.org Subject: FreeBSD 6.3 fxp0 MBUF and PAE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: daniel@dgnetwork.com.br List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Mar 2008 20:01:33 -0000 Hi, When using the interface fxp0 with PAE enable in kernel, occurs the following error: fxp0: can't map mbuf (error 12) ... it repeats, repeats and lost communication. Information: 6.3-RELEASE fxp0@pci14:4:0: class=0x020000 card=0x00708086 chip=0x12298086 rev=0x10 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class = network subclass = ethernet I wait reply. Thanks. Daniel From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 21:20:48 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ED0E1065674 for ; Wed, 12 Mar 2008 21:20:48 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from websrv01.jr-hosting.nl (websrv01.jr-hosting.nl [78.47.69.233]) by mx1.freebsd.org (Postfix) with ESMTP id E9AB88FC1E for ; Wed, 12 Mar 2008 21:20:47 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from localhost ([127.0.0.1] helo=galain.elvandar.org) by websrv01.jr-hosting.nl with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JZYNR-000CRx-AF; Wed, 12 Mar 2008 21:20:45 +0000 Received: from 195.64.94.120 (SquirrelMail authenticated user remko) by galain.elvandar.org with HTTP; Wed, 12 Mar 2008 22:20:45 +0100 (CET) Message-ID: <55002.195.64.94.120.1205356845.squirrel@galain.elvandar.org> In-Reply-To: References: <47D7C34E.8060805@zirakzigil.org> Date: Wed, 12 Mar 2008 22:20:45 +0100 (CET) From: "Remko Lodder" To: "Sean Chittenden" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-net@freebsd.org, Giulio Ferro Subject: Re: VLAN trunking and fragmentation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: remko@elvandar.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Mar 2008 21:20:48 -0000 On Wed, March 12, 2008 8:38 pm, Sean Chittenden wrote: >> interface ethernet 1/g1 >> switchport mode trunk >> switchport trunk allowed vlan add 10 >> exit > > I think this is an issue with default VLAN membership. I have this > config running on *hundreds* of servers without issue. Since Dell > should be a cisco rip-off, on your switchport config, throw in > (haven't tested this, on dell's CLI): > > switchport trunk encapsulation dot1q > > then change your ifconfig foo to: > > cloned_interfaces="vlan10 vlan11" > ifconfig_re0="media 100baseTX mediaopt full-duplex" > ifconfig_vlan10="vlan 10 vlandev re0" > ifconfig_vlan10_alias0="inet 192.168.60.1 netmask 255.255.255.0" > ifconfig_vlan11="vlan 11 valndev re0" > ifconfig_vlan11_alias0="inet 192.168.100.1 netmask 255.255.255.0" > > FWIW, I think you'll find fewer gray hairs if you stick to the > convention of using a vlan device that has the same VLAN tag. You may > be able to have a default VLAN, but I consider it poor practice to > rely on default VLAN membership. > > There are good reasons to have a default VLAN configured, but this > doesn't sound like one of those cases. > > Stick with explicit VLAN tagging on your servers and you can't go wrong. > > -sc > > -- > Sean Chittenden > sean@chittenden.org > http://sean.chittenden.org/ > For what it's worth: I am using the above setup a lot and that works fine for me! -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 21:22:42 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04E5E106566B for ; Wed, 12 Mar 2008 21:22:42 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 394AF8FC16 for ; Wed, 12 Mar 2008 21:22:40 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 55016 invoked by uid 98); 12 Mar 2008 21:22:39 -0000 Received: from 192.168.229.11 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:1(192.168.229.11):. Processed in 0.04097 secs); 12 Mar 2008 21:22:39 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:1(192.168.229.11):. Processed in 0.04097 secs) Received: from unknown (HELO aurynhome1ws2.zirakzigil.org) (postmaster@zirakzigil.org@192.168.229.11) by 0 with SMTP; 12 Mar 2008 21:22:39 -0000 Message-ID: <47D8499A.5070605@zirakzigil.org> Date: Wed, 12 Mar 2008 22:22:34 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.0 (X11/20070513) MIME-Version: 1.0 To: Sam Leffler References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> In-Reply-To: <47D817D2.9010306@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Andrew Thompson Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 21:22:42 -0000 Sam Leffler wrote: > You failed to provide the output of ifconfig on your running system. > Be sure any checksum offload is disabled (should be by the bridge). > > Sam My bad. I switched off checksum offload in /etc/rc.conf like this: ifconfig_re0="inet 192.168.60.1 netmask 255.255.255.0 -rxcsum -txcsum" (same thing on the other machine) Now my ifconfig on PC #1 is : ----------------------------------------- # ifconfig re0 re0: flags=8843 metric 0 mtu 1500 options=98 ether 00:14:c1:40:c2:e8 inet 192.168.60.1 netmask 0xffffff00 broadcast 192.168.60.255 media: Ethernet autoselect (1000baseTX ) status: active # ifconfig vlan0 vlan0: flags=8843 metric 0 mtu 1500 ether 00:14:c1:40:c2:e8 inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 media: Ethernet autoselect (1000baseTX ) status: active vlan: 10 parent interface: re0 ----------------------------------------- on PC #2 : ----------------------------------------- # ifconfig re0 re0: flags=8843 metric 0 mtu 1500 options=98 ether 00:15:8a:00:48:80 inet 192.168.60.2 netmask 0xffffff00 broadcast 192.168.60.255 media: Ethernet autoselect (1000baseTX ) status: active # ifconfig vlan0 vlan0: flags=8843 metric 0 mtu 1500 ether 00:15:8a:00:48:80 inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 media: Ethernet autoselect (1000baseTX ) status: active vlan: 10 parent interface: re0 ----------------------------------------- Any packet greater than 1472 which gets fragmented doesn't pass through: command : ping -c 1 -s 1473 192.168.100.2 on the sending machine: ----------------------------------------- # tcpdump -i re0 -n -vvv not tcp and not stp 23:11:07.649600 IP (tos 0x0, ttl 64, id 399, offset 0, flags [+], proto ICMP (1), length 1500) 192.168.100.1 > 192.168.100.2: ICMP echo request, id 19972, seq 0, length 1480 23:11:07.649605 IP (tos 0x0, ttl 64, id 399, offset 1480, flags [none], proto ICMP (1), length 21) 192.168.100.1 > 192.168.100.2: icmp ----------------------------------------- Whereas on the receiving machine I don't get any packet. Thanks for your answer. From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 21:30:01 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB172106566C for ; Wed, 12 Mar 2008 21:30:01 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id D744B8FC1D for ; Wed, 12 Mar 2008 21:30:00 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 55054 invoked by uid 98); 12 Mar 2008 21:30:00 -0000 Received: from 192.168.229.11 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:1(192.168.229.11):. Processed in 0.047782 secs); 12 Mar 2008 21:30:00 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:1(192.168.229.11):. Processed in 0.047782 secs) Received: from unknown (HELO aurynhome1ws2.zirakzigil.org) (postmaster@zirakzigil.org@192.168.229.11) by 0 with SMTP; 12 Mar 2008 21:29:59 -0000 Message-ID: <47D84B52.5020607@zirakzigil.org> Date: Wed, 12 Mar 2008 22:29:54 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.0 (X11/20070513) MIME-Version: 1.0 To: Sean Chittenden References: <47D7C34E.8060805@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 21:30:01 -0000 Sean Chittenden wrote: >> interface ethernet 1/g1 >> switchport mode trunk >> switchport trunk allowed vlan add 10 >> exit > > I think this is an issue with default VLAN membership. I don't think it's where the problem lies, otherwise even a simple ping wouldn't work. The problem here explicitly arises when packets are fragmented... > switchport trunk encapsulation dot1q > There's no such option, I believe it's implicit in the trunk mode... > then change your ifconfig foo to: > > cloned_interfaces="vlan10 vlan11" > ifconfig_re0="media 100baseTX mediaopt full-duplex" > ifconfig_vlan10="vlan 10 vlandev re0" > ifconfig_vlan10_alias0="inet 192.168.60.1 netmask 255.255.255.0" > ifconfig_vlan11="vlan 11 valndev re0" > ifconfig_vlan11_alias0="inet 192.168.100.1 netmask 255.255.255.0" > Apart from vlan names, this configuration is equivalent to mine... > There are good reasons to have a default VLAN configured, but this > doesn't sound like one of those cases. I have no default vlan. Thanks for your answer. From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 21:52:51 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96C111065671 for ; Wed, 12 Mar 2008 21:52:51 +0000 (UTC) (envelope-from if@xip.at) Received: from chile.gbit.at (ns1.xip.at [193.239.188.99]) by mx1.freebsd.org (Postfix) with ESMTP id E49E68FC1B for ; Wed, 12 Mar 2008 21:52:50 +0000 (UTC) (envelope-from if@xip.at) Received: (qmail 7710 invoked from network); 12 Mar 2008 22:52:48 +0100 Received: from unknown (HELO filebunker.xip.at) (86.59.10.180) by chile.gbit.at with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Mar 2008 22:52:48 +0100 Date: Wed, 12 Mar 2008 22:52:47 +0100 (CET) From: Ingo Flaschberger To: Giulio Ferro In-Reply-To: <47D84B52.5020607@zirakzigil.org> Message-ID: References: <47D7C34E.8060805@zirakzigil.org> <47D84B52.5020607@zirakzigil.org> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-net@freebsd.org, Sean Chittenden Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 21:52:51 -0000 Dear Giuilio, > Sean Chittenden wrote: >>> interface ethernet 1/g1 >>> switchport mode trunk >>> switchport trunk allowed vlan add 10 >>> exit >> >> I think this is an issue with default VLAN membership. > > I don't think it's where the problem lies, otherwise even a simple ping > wouldn't work. The problem here explicitly arises when packets are > fragmented... fragmentation? I think, you use ethernet links, all have 1500byte max packet size, you have 1500byte packet size also comfigured at the vlan interface, so.. why do you think anything should start fragmenting? (and tagged vlan frames are bigger than 1500byte at the "raw" ethernet link). check for maximum mtu that can travel over the link. (ping -s 1472 for 1500byte packet) >> switchport trunk encapsulation dot1q >> > There's no such option, I believe it's implicit in the trunk mode... and put the server back to back and remove the switch, just to be shure the switch is not the problem. Kind regards, Ingo Flaschberger From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 22:13:20 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 269CB106566C for ; Wed, 12 Mar 2008 22:13:20 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 9D11F8FC22 for ; Wed, 12 Mar 2008 22:13:19 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from heff.fud.org.nz (localhost [127.0.0.1]) by heff.fud.org.nz (Postfix) with ESMTP id 93BCC83FD; Thu, 13 Mar 2008 11:13:17 +1300 (NZDT) Received: (from thompsa@localhost) by heff.fud.org.nz (8.14.2/8.14.2/Submit) id m2CMDFBe005296; Thu, 13 Mar 2008 11:13:15 +1300 (NZDT) (envelope-from thompsa@FreeBSD.org) X-Authentication-Warning: heff.fud.org.nz: thompsa set sender to thompsa@FreeBSD.org using -f Date: Thu, 13 Mar 2008 11:13:14 +1300 From: Andrew Thompson To: Sean Chittenden Message-ID: <20080312221314.GA4458@heff.fud.org.nz> References: <47D7C34E.8060805@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-net@FreeBSD.org, Giulio Ferro Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 22:13:20 -0000 On Wed, Mar 12, 2008 at 12:38:06PM -0700, Sean Chittenden wrote: >> interface ethernet 1/g1 >> switchport mode trunk >> switchport trunk allowed vlan add 10 >> exit > > I think this is an issue with default VLAN membership. I have this config > running on *hundreds* of servers without issue. Since Dell should be a > cisco rip-off, on your switchport config, throw in (haven't tested this, on > dell's CLI): > > switchport trunk encapsulation dot1q > > then change your ifconfig foo to: > > cloned_interfaces="vlan10 vlan11" > ifconfig_re0="media 100baseTX mediaopt full-duplex" > ifconfig_vlan10="vlan 10 vlandev re0" > ifconfig_vlan10_alias0="inet 192.168.60.1 netmask 255.255.255.0" > ifconfig_vlan11="vlan 11 valndev re0" > ifconfig_vlan11_alias0="inet 192.168.100.1 netmask 255.255.255.0" > > FWIW, I think you'll find fewer gray hairs if you stick to the convention > of using a vlan device that has the same VLAN tag. You may be able to have > a default VLAN, but I consider it poor practice to rely on default VLAN > membership. Even nicer is using . autoconfig, the following is equivalent to above: cloned_interfaces="re0.10 re0.11" ifconfig_re0="media 100baseTX mediaopt full-duplex" ifconfig_re0.10="inet 192.168.60.1 netmask 255.255.255.0" ifconfig_re0.11="inet 192.168.100.1 netmask 255.255.255.0" Andrew From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 22:34:05 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F29E5106566C for ; Wed, 12 Mar 2008 22:34:04 +0000 (UTC) (envelope-from sean@chittenden.org) Received: from davie.textdrive.com (davie.textdrive.com [207.7.108.101]) by mx1.freebsd.org (Postfix) with ESMTP id D69668FC1F for ; Wed, 12 Mar 2008 22:34:04 +0000 (UTC) (envelope-from sean@chittenden.org) Received: from [192.168.255.187] (60.ten-net.org [71.6.14.60]) by davie.textdrive.com (Postfix) with ESMTP id 1CDEBC2F0E; Wed, 12 Mar 2008 22:34:03 +0000 (GMT) Message-Id: From: Sean Chittenden To: Andrew Thompson In-Reply-To: <20080312221314.GA4458@heff.fud.org.nz> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 12 Mar 2008 15:34:00 -0700 References: <47D7C34E.8060805@zirakzigil.org> <20080312221314.GA4458@heff.fud.org.nz> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-net@FreeBSD.org, Giulio Ferro Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 22:34:05 -0000 >>>> interface ethernet 1/g1 >>>> switchport mode trunk >>>> switchport trunk allowed vlan add 10 >>>> exit >>> I think this is an issue with default VLAN membership. >> >> I don't think it's where the problem lies, otherwise even a simple >> ping >> wouldn't work. The problem here explicitly arises when packets are >> fragmented... > > fragmentation? > I think, you use ethernet links, all have 1500byte max packet size, > you have 1500byte packet size also comfigured at the vlan interface, > so.. > why do you think anything should start fragmenting? > (and tagged vlan frames are bigger than 1500byte at the "raw" > ethernet link). > > check for maximum mtu that can travel over the link. > (ping -s 1472 for 1500byte packet) It's the MTU size, not the fragmentation or VLAN membership. The use of a default VLAN can cause problems potentially because the size of each frame can vary and, IMHO, is the cause of the problem. By default VLAN membership, I don't mean to suggest you've got your port tagged in the wrong VLAN. Switch all traffic to 802.1q tagged and you should see everything work. Use of VLANs reduces the MTU size automatically, but cycling between the two? Likely a no-go and the source of your problems. > Even nicer is using . autoconfig, the following is > equivalent to above: > > cloned_interfaces="re0.10 re0.11" > ifconfig_re0="media 100baseTX mediaopt full-duplex" > ifconfig_re0.10="inet 192.168.60.1 netmask 255.255.255.0" > ifconfig_re0.11="inet 192.168.100.1 netmask 255.255.255.0" *boggles* That's hawt! 'ya learn something new every day, thanks! :~] -sc -- Sean Chittenden sean@chittenden.org http://sean.chittenden.org/ From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 23:00:58 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE5021065671 for ; Wed, 12 Mar 2008 23:00:58 +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 2F3758FC22 for ; Wed, 12 Mar 2008 23:00:57 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 26482 invoked from network); 12 Mar 2008 22:13:10 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Mar 2008 22:13:10 -0000 Message-ID: <47D860AC.6030707@freebsd.org> Date: Thu, 13 Mar 2008 00:01:00 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: "d.s. al coda" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 12 Mar 2008 23:00:58 -0000 d.s. al coda wrote: > Hi, > We recently upgraded one of our webservers to FreeBSD 7, and we started > receiving complaints from some users not able to connect to that server > anymore. On top of that, users were saying that the problem only occurred on > Windows (at least, the ones who had more than on OS to try it out). > > After managing to get a user who had the problem running windump, running > tcpdump on the new server, and comparing that to the windump & tcpdump > output for a "control" user (me) that could connect, we managed to figure > out the following: > - For the user with this problem, ping works fine, but all TCP connections > to the server fail. > - The user, trying to connect, sends out a SYN packet, receives no response, > and retries a few times until timing out. > - The server sees a bunch of SYN packets and responds with SYN-ACK each > time. > - The issue only seems to arise if the sender has RFC1323 disabled. > > So, the SYN-ACK is getting lost somewhere. > > - For the control user (who can connect via TCP just fine), we set the TCP > window size and RFC1323 options the same as the user with the problem. > - The control user sees the SYN-ACK packet. > - We send a connection attempt to one of our other servers, running FreeBSD > 5.5, and one to the server running FreeBSD 7. > - There is only one notable difference between the responses: the order of > the options. > - FreeBSD 5.5 has > - FreeBSD 7 has (there is of course an aligning nop > after the eol, which tcpdump skips) > - These options don't appear in this exact configuration when using RFC1323 > options. > > I get a hunch that the users with the problem have a router that erroneously > thinks that these options are invalid, or thinks that the some part of byte > sequence (e.g. 0204 05b4 0101 0402) is an attack. > > Just to try it out, I patched tcp_output.c so that the SACK permitted option > was aligned on a 4-byte boundary, preventing the "sackOK, eol" pattern from > ever occuring. Looking through previous versions, I found where the tcp > option code had changed, and there used to be a comment about putting SACK > permitted last, but I can't tell if it's relevant. > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.125;r2=1.126 > > The one-line patch to tcp_output.c is attached. > > Sure enough, it fixed the problem. Afterwards, we collected some information > about the routers the users who had the problem were using, and while they > didn't all have the same manufacturer, several mentioned that their router > had a built-in firewall, which, when they disabled it, allowed them to > access the server. I'd be very interesting to know the exactly models and their firmware version of the affected routers. If available locally I'd like to obtain a similar model myself for future regression tests. > Does all of this sound reasonable? And if so, would it be worth submitting > this patch? I don't know if this particular change in options order was > intentional, or just a side-effect of the new code, but it certainly works > around an extremely hard-to-diagnose problem. We've already fixed two issues. The first changes the order of the TCP options and is in this change: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_var.h.diff?r1=1.160;r2=1.161 It is to solve a problem observed by ISC that sounds very much like what you describe. This fixed the issue in this case. The second changes the alignment padding from NOP to 0x00. Whether this was a contributing factor to the reported problem is not clear. There hasn't (yet) been any specific test case for it. It was fixed because the RFC specifies 0x00 to be used for padding and nothing else. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.145;r2=1.146 It would be very helpful if you could apply these two patches after each other to your 7.0 test server and find out together with the affected user(s) which of these fixes the issue. If you can please try to test each one with and w/o the routers firewall enabled. It is interesting to know whether the NAT or firewalling part of the router chokes on it. Your help is very appreciated and I try to document all strange TCP occurrences so we can incorporate them into a regression test suite later on. The more information we have the better it'll become. -- Andre From owner-freebsd-net@FreeBSD.ORG Wed Mar 12 23:11:39 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CB461065672; Wed, 12 Mar 2008 23:11:39 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id 945378FC18; Wed, 12 Mar 2008 23:11:38 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.1/8.13.8) with ESMTP id m2CMgs2A079750; Wed, 12 Mar 2008 17:42:54 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m2CMgrd1079749; Wed, 12 Mar 2008 17:42:53 -0500 (CDT) (envelope-from brooks) Date: Wed, 12 Mar 2008 17:42:53 -0500 From: Brooks Davis To: Andrew Thompson Message-ID: <20080312224253.GB79445@lor.one-eyed-alien.net> References: <47D7C34E.8060805@zirakzigil.org> <20080312221314.GA4458@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2JFBq9zoW8cOFH7v" Content-Disposition: inline In-Reply-To: <20080312221314.GA4458@heff.fud.org.nz> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 12 Mar 2008 17:42:54 -0500 (CDT) Cc: freebsd-net@freebsd.org, Giulio Ferro , Sean Chittenden Subject: Re: VLAN trunking and fragmentation 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, 12 Mar 2008 23:11:39 -0000 --2JFBq9zoW8cOFH7v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 13, 2008 at 11:13:14AM +1300, Andrew Thompson wrote: > On Wed, Mar 12, 2008 at 12:38:06PM -0700, Sean Chittenden wrote: > >> interface ethernet 1/g1 > >> switchport mode trunk > >> switchport trunk allowed vlan add 10 > >> exit > > > > I think this is an issue with default VLAN membership. I have this con= fig=20 > > running on *hundreds* of servers without issue. Since Dell should be a= =20 > > cisco rip-off, on your switchport config, throw in (haven't tested this= , on=20 > > dell's CLI): > > > > switchport trunk encapsulation dot1q > > > > then change your ifconfig foo to: > > > > cloned_interfaces=3D"vlan10 vlan11" > > ifconfig_re0=3D"media 100baseTX mediaopt full-duplex" > > ifconfig_vlan10=3D"vlan 10 vlandev re0" > > ifconfig_vlan10_alias0=3D"inet 192.168.60.1 netmask 255.255.255.0" > > ifconfig_vlan11=3D"vlan 11 valndev re0" > > ifconfig_vlan11_alias0=3D"inet 192.168.100.1 netmask 255.255.255.0" > > > > FWIW, I think you'll find fewer gray hairs if you stick to the conventi= on=20 > > of using a vlan device that has the same VLAN tag. You may be able to = have=20 > > a default VLAN, but I consider it poor practice to rely on default VLAN= =20 > > membership. >=20 > Even nicer is using . autoconfig, the following is > equivalent to above: >=20 > cloned_interfaces=3D"re0.10 re0.11" > ifconfig_re0=3D"media 100baseTX mediaopt full-duplex" > ifconfig_re0.10=3D"inet 192.168.60.1 netmask 255.255.255.0" > ifconfig_re0.11=3D"inet 192.168.100.1 netmask 255.255.255.0" One small nit. The '.' isn't valid in variable names so the ifconfig_re0.xx lines need to turn into ifconfig_re0_xx (we compress ./-+ to _). -- Brooks --2JFBq9zoW8cOFH7v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFH2FxtXY6L6fI4GtQRAsELAJ9YtW6812JUYwSD7fjPJHtFB/ATjACfYyo7 LF4vuTwa/1n82S7nm6+nSmI= =g92q -----END PGP SIGNATURE----- --2JFBq9zoW8cOFH7v-- From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 00:36:19 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D96A11065673 for ; Thu, 13 Mar 2008 00:36:19 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: from coruscant.far-far-away.com (coruscant.far-far-away.us [70.91.196.65]) by mx1.freebsd.org (Postfix) with SMTP id 81B2F8FC1D for ; Thu, 13 Mar 2008 00:36:19 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: (qmail 89496 invoked from network); 12 Mar 2008 20:03:31 -0400 Received: from unknown (HELO ?192.168.0.5?) (192.168.0.5) by coruscant.far-far-away.com with SMTP; 12 Mar 2008 20:03:31 -0400 From: Yousif Hassan To: Benjamin Close In-Reply-To: <47D6FB5B.3020107@clearchain.com> References: <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl> <47D6FB5B.3020107@clearchain.com> Content-Type: text/plain Date: Wed, 12 Mar 2008 20:09:16 -0400 Message-Id: <1205366956.2082.13.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Mel , Alphons Fonz van Werven , freebsd-mobile@freebsd.org Subject: Re: [Wireless] Can't connect to wlan 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, 13 Mar 2008 00:36:20 -0000 On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: > Alphons "Fonz" van Werven wrote: > > Mel wrote: > > > >>> Do the recent patches by Andrew make a difference? > >>> > >>> http://people.freebsd.org/~thompsa/wpi_head.diff > >>> http://people.freebsd.org/~thompsa/wpi_releng7.diff > > (ccing freebsd-net) Ben, I had a go with this patch today on top of 7.0-RELEASE. The good: - Switching off the radio and back on finally works - nice work. - Scanning seems faster (but see caveat below) - Association is MUCH faster (mind you, I don't use an encrypted AP). - The "failed to align memory" stuff when the driver loads up - fixed. - The fact that it reloaded in the kernel even if I manually kldunloaded if_wpi.ko - fixed The slightly wonky: - As reported by someone else: wpi0: timeout resetting Tx ring 1 wpi0: timeout resetting Tx ring 3 wpi0: timeout resetting Tx ring 4 appear on startup and occasionally on kldload - however they don't appear to adversely affect too much The ugly: - I can only do an ifconfig wpi0 scan every OTHER time - in between successful attempts, I get wpi0: fatal firmware error wpi0: timeout resetting Tx ring (or: timeout resetting Tx ring 0) wpi0: link state changed to DOWN This wouldn't be so bad since it works every other time, but the problem is that every time I do a scan, it sets the link state down, causing the connection to drop - doesn't seem normal. Of course then it comes right back up but the network interruption is not so great. Hmm - what else? The whole thing seems - livelier. I need to run some throughput benchmarks but traffic to/from the card on my local network seems faster and more responsive. Hopefully this isn't the placebo effect. ;) Great work to you & rest of team on this patch... it's more than usable at this point! --Yousif From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 01:27:53 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFEE01065670 for ; Thu, 13 Mar 2008 01:27:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by mx1.freebsd.org (Postfix) with ESMTP id 39DA28FC19 for ; Thu, 13 Mar 2008 01:27:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so1825133ele.12 for ; Wed, 12 Mar 2008 18:27:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=cPnyEOp1Rzzd/jS2ttQoEijwEb0ocGvnwZEdexBB+H4=; b=nFq/31rRrJTOF1VZGtbnOzAxEgy/9rvAaeiWQ81zFJv9VuE6NdokoVZ9e4ujTNZjXHg9t0aBqJcoAlUGweWi/0llbTv7liJJUd9HyugX9kMPzJz+p/oxtmNEufC4JabmVW4zvxqXoSjkSsRe7twzskXhORJTUBJnByowFd4+1WU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=bAqgzQw+djkzZDBafAihEMA9oIMITJnaSzYA7qpgHPsUn70z0OFhv+BneC3i8v9X5Ie/Ds86i31Xwkzw6UwFPz6CRtjwEgdNQRsTgvK6po704ylxiwtyaQjFY9kg5K0OXcCqw0+WGaFsOXQKpbU1YpL6USakgvsZJtI8lDaI+/A= Received: by 10.150.203.8 with SMTP id a8mr4982783ybg.56.1205371672225; Wed, 12 Mar 2008 18:27:52 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 35sm17258713wra.37.2008.03.12.18.27.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Mar 2008 18:27:50 -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 m2D1RjIm017355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Mar 2008 10:27:45 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2D1Rflt017354; Thu, 13 Mar 2008 10:27:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 13 Mar 2008 10:27:41 +0900 From: Pyun YongHyeon To: Daniel Dias Gon?alves Message-ID: <20080313012741.GC16972@cdnetworks.co.kr> References: <47D834AE.8080301@dgnetwork.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47D834AE.8080301@dgnetwork.com.br> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org, freebsd-smp@freebsd.org Subject: Re: FreeBSD 6.3 fxp0 MBUF and PAE 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: Thu, 13 Mar 2008 01:27:53 -0000 On Wed, Mar 12, 2008 at 04:53:18PM -0300, Daniel Dias Gon?alves wrote: > Hi, > > When using the interface fxp0 with PAE enable in kernel, occurs the > following error: > > fxp0: can't map mbuf (error 12) > ... > > it repeats, repeats and lost communication. > error 12 means ENOMEM. bus_dmamap_load_mbuf_sg(9) failed due to insuffcient resources. I guess there is no way to overcome this situation in driver. The only remaining way I can think of would be reclaiming of transmitted frames but how well it works would depends on circumstances. Personally I don't see a reason to print these ENOMEM errors for production box without late limiting. > Information: > 6.3-RELEASE > > fxp0@pci14:4:0: class=0x020000 card=0x00708086 chip=0x12298086 rev=0x10 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' > class = network > subclass = ethernet > > I wait reply. > > Thanks. > > Daniel -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 01:35:06 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A82A106566C for ; Thu, 13 Mar 2008 01:35:06 +0000 (UTC) (envelope-from crahman@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 3ED8D8FC1B for ; Thu, 13 Mar 2008 01:35:06 +0000 (UTC) (envelope-from crahman@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3671030waf.3 for ; Wed, 12 Mar 2008 18:35:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vxQD0+rAIuFljdEB1NJL9Mw6HHtEFV63pCEFVwasEJc=; b=Wanub3klGiEeEuefDfwWA3H7X/y3VZ8WqX61mc9+P/u+iX2hTjMEn7DEX+6J+dMPx6T67g9mvhXMN2RqMdj5qaXIkudxaTYn2HsgVgu/WCiifiM4S/KPQ/w6qUTRalnTqFKnKOZMhmpoS65zpfCbYQ1R6/Ae2p1lkRQIQF8jNyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pC5JgFFmrUm/96r2ztAq7Nb0TL5WvdJBBey2gNGpDFS32vCP8IBkEHNKbbTSizPCz0AkYjllIy/x3lDyX5xal/hbQ6xOWWWcMVMTNnxtM9xvpdEeiLyctEC4MHcRlQy1SYyl8eQ7NIunlwmBIv8/EnLOuTUt7IXFSoxWS1JoSJc= Received: by 10.114.157.1 with SMTP id f1mr8302059wae.10.1205372105653; Wed, 12 Mar 2008 18:35:05 -0700 (PDT) Received: by 10.115.19.7 with HTTP; Wed, 12 Mar 2008 18:35:05 -0700 (PDT) Message-ID: <9e77bdb50803121835u33b10d67i30b6f20ec833921@mail.gmail.com> Date: Wed, 12 Mar 2008 19:35:05 -0600 From: "Cyrus Rahman" To: bz@freebsd.org In-Reply-To: <200803082305.m28N5DkU075120@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200803082305.m28N5DkU075120@freefall.freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: kern/121374: [ipsec] SP refcnt increases with each packet in ipv6 with new IPSEC 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, 13 Mar 2008 01:35:06 -0000 > Synopsis: [ipsec] SP refcnt increases with each packet in ipv6 with new IPSEC > > Wait for feedback if the patch presented is fine. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=121374 Ok, I've tested this patch. Exchanging packets through a policy works after a fashion, but after sending one packet the kernel deletes the policy, presumably because the refcnt goes to 0: hostB# setkey -DP hostA[any] hostB[any] any in ipsec esp/transport//require spid=22 seq=1 pid=1037 refcnt=1 hostB[any] hostA[any] any out ipsec esp/transport//require spid=21 seq=0 pid=1037 refcnt=1 hostB# ping6 hostA PING6(56=40+8+8 bytes) hostB --> hostA 16 bytes from hostA, icmp_seq=0 hlim=64 time=12.401 ms ^C --- hostA ping6 statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 12.401/12.401/12.401/0.000 ms hostB# setkey -DP hostA[any] hostB[any] any in ipsec esp/transport//require spid=22 seq=0 pid=1040 refcnt=1 **** So the outbound policy is gone! From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 02:37:14 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A19E81065673; Thu, 13 Mar 2008 02:37:14 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 60C458FC22; Thu, 13 Mar 2008 02:37:14 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m2D2DKvb044374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Mar 2008 19:13:20 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <47D88DC0.1010903@freebsd.org> Date: Wed, 12 Mar 2008 19:13:20 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Yousif Hassan References: <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl> <47D6FB5B.3020107@clearchain.com> <1205366956.2082.13.camel@localhost> In-Reply-To: <1205366956.2082.13.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Misty-Metrics: ebb.errno.com; whitelist Cc: freebsd-net@freebsd.org, Benjamin Close , Mel , Alphons Fonz van Werven , freebsd-mobile@freebsd.org Subject: Re: [Wireless] Can't connect to wlan 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, 13 Mar 2008 02:37:14 -0000 Yousif Hassan wrote: > On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: > >> Alphons "Fonz" van Werven wrote: >> >>> Mel wrote: >>> >>> >>>>> Do the recent patches by Andrew make a difference? >>>>> >>>>> http://people.freebsd.org/~thompsa/wpi_head.diff >>>>> http://people.freebsd.org/~thompsa/wpi_releng7.diff >>>>> > > (ccing freebsd-net) > > Ben, > > I had a go with this patch today on top of 7.0-RELEASE. > > The good: > - Switching off the radio and back on finally works - nice work. > - Scanning seems faster (but see caveat below) > - Association is MUCH faster (mind you, I don't use an encrypted AP). > - The "failed to align memory" stuff when the driver loads up - fixed. > - The fact that it reloaded in the kernel even if I manually kldunloaded > if_wpi.ko - fixed > > The slightly wonky: > - As reported by someone else: > wpi0: timeout resetting Tx ring 1 > wpi0: timeout resetting Tx ring 3 > wpi0: timeout resetting Tx ring 4 > appear on startup and occasionally on kldload - however they don't > appear to adversely affect too much > > The ugly: > - I can only do an ifconfig wpi0 scan every OTHER time - in between > successful attempts, I get > wpi0: fatal firmware error > wpi0: timeout resetting Tx ring (or: timeout resetting Tx ring 0) > wpi0: link state changed to DOWN > > This wouldn't be so bad since it works every other time, but the > problem is that every time I do a scan, it sets the link state down, > causing the connection to drop - doesn't seem normal. Of course then it > comes right back up but the network interruption is not so great. > > Hmm - what else? The whole thing seems - livelier. I need to run some > throughput benchmarks but traffic to/from the card on my local network > seems faster and more responsive. Hopefully this isn't the placebo > effect. ;) > > Great work to you & rest of team on this patch... it's more than usable > at this point! > wpi doesn't yet support background scan so doing an explicit scan from the command line will disconnect you from any ap you care connected to. It shouldn't be hard to add bgscan--but that's easy for me to say :) Sam From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 03:30:38 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EAEE1065672 for ; Thu, 13 Mar 2008 03:30:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by mx1.freebsd.org (Postfix) with ESMTP id 1F89E8FC2A for ; Thu, 13 Mar 2008 03:30:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so1833526ele.12 for ; Wed, 12 Mar 2008 20:30:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=H2MHRYygwsA7YoNSKudRYogN7KZIwW6whwWxPhIc00A=; b=OqVMfyTwu9g7OWC5DFgvirbMSgzBQavNtzZ/G6ITHPYDMKAlJtzCLmflT0yz5kWcUpzkSQRJ0pjK1FdmX8stBlsv9ow7EvB/HxoHxzvtvbqO32nFAuFGy/O/c2FBxn3TejHgl7CdbyUaIyA0+vU3anM6tiU90Ow/AOlpet7IVh8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=g7J1PhkBdR6Ao4uW2XhLLAwV9nHXGEjr48gOvynsw+9fjl6ZCbV4AbmnaemxXjGSXM31ZqJXtLW0cfnBAcxkxntLzdjMqvUOpOZwzQbOp9TyTFvjRbmpc06sGRviLVW2INF6okWZk58QDWp31nkmiap8i/cSjA7DtXilvhjHbA4= Received: by 10.150.203.8 with SMTP id a8mr5044559ybg.146.1205379037338; Wed, 12 Mar 2008 20:30:37 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 45sm17618673wri.8.2008.03.12.20.30.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Mar 2008 20:30:36 -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 m2D3UUCv017742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Mar 2008 12:30:30 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2D3UTYH017741; Thu, 13 Mar 2008 12:30:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 13 Mar 2008 12:30:29 +0900 From: Pyun YongHyeon To: Giulio Ferro Message-ID: <20080313033029.GF16972@cdnetworks.co.kr> References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47D8499A.5070605@zirakzigil.org> User-Agent: Mutt/1.4.2.1i Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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: Thu, 13 Mar 2008 03:30:38 -0000 On Wed, Mar 12, 2008 at 10:22:34PM +0100, Giulio Ferro wrote: > Sam Leffler wrote: > >You failed to provide the output of ifconfig on your running system. > >Be sure any checksum offload is disabled (should be by the bridge). > > > > Sam > My bad. > > I switched off checksum offload in /etc/rc.conf like this: > ifconfig_re0="inet 192.168.60.1 netmask 255.255.255.0 -rxcsum -txcsum" > (same thing on the other machine) > > Now my ifconfig on PC #1 is : > ----------------------------------------- > # ifconfig re0 > re0: flags=8843 metric 0 mtu 1500 > options=98 > ether 00:14:c1:40:c2:e8 > inet 192.168.60.1 netmask 0xffffff00 broadcast 192.168.60.255 > media: Ethernet autoselect (1000baseTX ) > status: active > > # ifconfig vlan0 > vlan0: flags=8843 metric 0 mtu 1500 > ether 00:14:c1:40:c2:e8 > inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 > media: Ethernet autoselect (1000baseTX ) > status: active > vlan: 10 parent interface: re0 > ----------------------------------------- > > on PC #2 : > ----------------------------------------- > # ifconfig re0 > re0: flags=8843 metric 0 mtu 1500 > options=98 > ether 00:15:8a:00:48:80 > inet 192.168.60.2 netmask 0xffffff00 broadcast 192.168.60.255 > media: Ethernet autoselect (1000baseTX ) > status: active > > # ifconfig vlan0 > vlan0: flags=8843 metric 0 mtu 1500 > ether 00:15:8a:00:48:80 > inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 > media: Ethernet autoselect (1000baseTX ) > status: active > vlan: 10 parent interface: re0 > ----------------------------------------- > > > > Any packet greater than 1472 which gets fragmented doesn't pass through: > command : ping -c 1 -s 1473 192.168.100.2 > > on the sending machine: > ----------------------------------------- > # tcpdump -i re0 -n -vvv not tcp and not stp > > 23:11:07.649600 IP (tos 0x0, ttl 64, id 399, offset 0, flags [+], proto > ICMP (1), length 1500) 192.168.100.1 > 192.168.100.2: ICMP echo request, > id 19972, seq 0, length 1480 > 23:11:07.649605 IP (tos 0x0, ttl 64, id 399, offset 1480, flags [none], > proto ICMP (1), length 21) 192.168.100.1 > 192.168.100.2: icmp > ----------------------------------------- > > > Whereas on the receiving machine I don't get any packet. > To rule out other possible issues, would you try the following files on your box? http://people.freebsd.org/~yongari/re/if_re.c http://people.freebsd.org/~yongari/re/if_rereg.h -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 03:57:52 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7863F1065672; Thu, 13 Mar 2008 03:57:52 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 6426A8FC19; Thu, 13 Mar 2008 03:57:52 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 8304DC3F38; Wed, 12 Mar 2008 23:57:51 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 12 Mar 2008 23:57:51 -0400 X-Sasl-enc: UjIm2aq5dci79rNOVb9njsZ9/c26WuHgzO2X9opO5gam 1205380671 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id E2783D2A5; Wed, 12 Mar 2008 23:57:50 -0400 (EDT) Message-ID: <47D8A63D.3050903@FreeBSD.org> Date: Thu, 13 Mar 2008 03:57:49 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.9 (X11/20080207) MIME-Version: 1.0 To: Robert Watson References: <20080312175151.V47697@fledge.watson.org> In-Reply-To: <20080312175151.V47697@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@FreeBSD.org Subject: Re: FYI: inpcb/pcbinfo mutex -> rwlock at some point in the mid-distant future 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, 13 Mar 2008 03:57:52 -0000 Robert Watson wrote: > One of those issues is that we need to demonstrate to ourselves that > exclusive access contention is managed as well with rwlocks as with > sleep mutexes, as these locks would continue to be fairly highly > contended in TCP. The other issue is that rwlocks don't support full > priority propagation for reader access, although Jeff Roberson has > recently improved fairness to writers with many readers. Don't forget that p4 bms_netdev contains a number of optimizations for the multicast paths -- there are lock acquisitions which are quite often unnecessary, or whose granularity is too high for the data structure(s) which need to be shared. BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 04:19:17 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51C6C1065675 for ; Thu, 13 Mar 2008 04:19:17 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.freebsd.org (Postfix) with SMTP id 033A58FC1B for ; Thu, 13 Mar 2008 04:19:16 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 11038 invoked from network); 13 Mar 2008 04:19:15 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 13 Mar 2008 04:19:15 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 12 Mar 2008 23:19:14 -0500 (CDT) From: Mike Silbersack To: "d.s. al coda" In-Reply-To: Message-ID: <20080312231330.D60219@odysseus.silby.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 13 Mar 2008 04:19:17 -0000 On Tue, 11 Mar 2008, d.s. al coda wrote: > - FreeBSD 7 has (there is of course an aligning nop > after the eol, which tcpdump skips) Jake Rizzo sent me some updated tcpdumps comparing 6.3 vs 7.0, and that aligning NOP that tcpdump (and wireshark) omit seems to be the only difference. Here's what Jake's 6.3 dump shows: IP A > B : S 2575736483:2575736483(0) ack 1762868649 win 65535 And the actual option data is: 02 04 05 b4 04 02 00 00 <- ends with two EOLs For 7.0: IP A > B : S 3304309835:3304309835(0) ack 710421411 win 65535 And the actual option data is: 02 04 05 64 04 02 00 01 <- ends with a NOP after the EOL I think we will need to fix tcpdump before trying to finish diagnosing this problem. We were missing key information before. -Mike From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 04:28:49 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C2BE1065672 for ; Thu, 13 Mar 2008 04:28:49 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id F3D958FC14 for ; Thu, 13 Mar 2008 04:28:48 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 59568 invoked from network); 13 Mar 2008 04:28:47 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 13 Mar 2008 04:28:47 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 12 Mar 2008 23:28:46 -0500 (CDT) From: Mike Silbersack To: "d.s. al coda" In-Reply-To: <20080312231330.D60219@odysseus.silby.com> Message-ID: <20080312232607.J60219@odysseus.silby.com> References: <20080312231330.D60219@odysseus.silby.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1861302967-1271846343-1205382526=:60219" Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 13 Mar 2008 04:28:49 -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. --1861302967-1271846343-1205382526=:60219 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Wed, 12 Mar 2008, Mike Silbersack wrote: > I think we will need to fix tcpdump before trying to finish diagnosing this > problem. We were missing key information before. > > -Mike Hm, that was far easier than expected. Patch attached. Here's what the two tcpdumps show now: 6.3: IP A > B : S 2575736483:2575736483(0) ack 1762868649 win 65535 7.0: IP A > B : S 3304309835:3304309835(0) ack 710421411 win 65535 That makes the problem quite a bit more clear. Anyone working on this issue should apply this patch ASAP. -Mike --1861302967-1271846343-1205382526=:60219 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=tcpdump-opt_past_eol.patch Content-Transfer-Encoding: BASE64 Content-ID: <20080312232846.R60219@odysseus.silby.com> Content-Description: Content-Disposition: attachment; filename=tcpdump-opt_past_eol.patch LS0tIHByaW50LXRjcC5jLm9sZAkyMDA4LTAzLTEyIDIzOjIxOjUyLjAwMDAw MDAwMCAtMDUwMA0KKysrIHByaW50LXRjcC5jCTIwMDgtMDMtMTIgMjM6MjQ6 NTAuMDAwMDAwMDAwIC0wNTAwDQpAQCAtNjM3LDggKzYzNywxMCBAQA0KIAkJ CWlmIChkYXRhbGVuICE9IGxlbikNCiAJCQkJKHZvaWQpcHJpbnRmKCJbbGVu ICVkXSIsIGxlbik7DQogCQkJY2ggPSAnLCc7DQorI2lmIDANCiAJCQlpZiAo b3B0ID09IFRDUE9QVF9FT0wpDQogCQkJCWJyZWFrOw0KKyNlbmRpZg0KIAkJ fQ0KIAkJcHV0Y2hhcignPicpOw0KIAl9DQo= --1861302967-1271846343-1205382526=:60219-- From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 04:57:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A58D1065670 for ; Thu, 13 Mar 2008 04:57:36 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id C87BE8FC13 for ; Thu, 13 Mar 2008 04:57:35 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 63299 invoked from network); 13 Mar 2008 04:57:35 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 13 Mar 2008 04:57:35 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 12 Mar 2008 23:57:34 -0500 (CDT) From: Mike Silbersack To: "Bjoern A. Zeeb" In-Reply-To: <20080312144207.P50685@maildrop.int.zabbadoz.net> Message-ID: <20080312235523.I60219@odysseus.silby.com> References: <20080312144207.P50685@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 13 Mar 2008 04:57:36 -0000 On Wed, 12 Mar 2008, Bjoern A. Zeeb wrote: > On Tue, 11 Mar 2008, d.s. al coda wrote: > >> - FreeBSD 7 has (there is of course an aligning nop >> after the eol, which tcpdump skips) > > Which is a bug (the nop after the EOL) that I recently fixed in HEAD. > I am still curious to know if it's only ordering or the invalid padding > or both that keeps clients from connecting. The problem is getting > hands on such a problematic "client". Bjoern, can you get that fix MFC'd ASAP? I've e-mailed a tcpdump developer asking how we can enhance it so that it prints out <..., eol, nop> so that we can detect such errors more easily in the future. I wish I had paid more attention to that part of the previous thread on this topic! -Mike From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 07:15:08 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07E491065688 for ; Thu, 13 Mar 2008 07:15:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id C34DF8FC25 for ; Thu, 13 Mar 2008 07:15:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id E8D0E41C7A6; Thu, 13 Mar 2008 08:15:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id rRKV5jZfZQpv; Thu, 13 Mar 2008 08:15:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 0E0EE41C7B4; Thu, 13 Mar 2008 08:15:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2C45644487F; Thu, 13 Mar 2008 07:14:14 +0000 (UTC) Date: Thu, 13 Mar 2008 07:14:14 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Mike Silbersack In-Reply-To: <20080312232607.J60219@odysseus.silby.com> Message-ID: <20080313071306.F50685@maildrop.int.zabbadoz.net> References: <20080312231330.D60219@odysseus.silby.com> <20080312232607.J60219@odysseus.silby.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 13 Mar 2008 07:15:08 -0000 On Wed, 12 Mar 2008, Mike Silbersack wrote: > > On Wed, 12 Mar 2008, Mike Silbersack wrote: > >> I think we will need to fix tcpdump before trying to finish diagnosing this >> problem. We were missing key information before. >> >> -Mike > > Hm, that was far easier than expected. Patch attached. > > Here's what the two tcpdumps show now: > > 6.3: > IP A > B : S 2575736483:2575736483(0) ack 1762868649 win 65535 1460,sackOK,eol,eol> > > 7.0: > IP A > B : S 3304309835:3304309835(0) ack 710421411 win 65535 1380,sackOK,eol,nop> > > That makes the problem quite a bit more clear. Anyone working on this issue > should apply this patch ASAP. While this makes it more clear I'd rather see things in hex after the first EOL but either way is fine, just to see it. Ideally tcpdump would also complain if any padding after EOL is not 0x00. I wonder if wireshark does? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 07:34:10 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 619921065671 for ; Thu, 13 Mar 2008 07:34:10 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 2E51A8FC18 for ; Thu, 13 Mar 2008 07:34:09 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 6311341C7A5; Thu, 13 Mar 2008 08:15:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id HE+BYOksWUyt; Thu, 13 Mar 2008 08:15:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 0630541C7AE; Thu, 13 Mar 2008 08:15:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 22C4944487F; Thu, 13 Mar 2008 07:13:00 +0000 (UTC) Date: Thu, 13 Mar 2008 07:13:00 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Mike Silbersack In-Reply-To: <20080312235523.I60219@odysseus.silby.com> Message-ID: <20080313071242.Q50685@maildrop.int.zabbadoz.net> References: <20080312144207.P50685@maildrop.int.zabbadoz.net> <20080312235523.I60219@odysseus.silby.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 13 Mar 2008 07:34:10 -0000 On Wed, 12 Mar 2008, Mike Silbersack wrote: > > On Wed, 12 Mar 2008, Bjoern A. Zeeb wrote: > >> On Tue, 11 Mar 2008, d.s. al coda wrote: >> >>> - FreeBSD 7 has (there is of course an aligning >>> nop >>> after the eol, which tcpdump skips) >> >> Which is a bug (the nop after the EOL) that I recently fixed in HEAD. >> I am still curious to know if it's only ordering or the invalid padding >> or both that keeps clients from connecting. The problem is getting >> hands on such a problematic "client". > > Bjoern, can you get that fix MFC'd ASAP? I'll do that the next hours. > I've e-mailed a tcpdump developer asking how we can enhance it so that it > prints out <..., eol, nop> so that we can detect such errors more easily in > the future. > > I wish I had paid more attention to that part of the previous thread on this > topic! > > -Mike > _______________________________________________ > 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" > -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 13:44:15 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73585106566C for ; Thu, 13 Mar 2008 13:44:15 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 680428FC15 for ; Thu, 13 Mar 2008 13:44:12 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 63155 invoked by uid 98); 13 Mar 2008 13:44:09 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.043226 secs); 13 Mar 2008 13:44:09 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.043226 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 13 Mar 2008 13:44:09 -0000 Message-ID: <47D92F9D.4070701@zirakzigil.org> Date: Thu, 13 Mar 2008 14:43:57 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: pyunyh@gmail.com References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> In-Reply-To: <20080313033029.GF16972@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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, 13 Mar 2008 13:44:15 -0000 Pyun YongHyeon wrote: > To rule out other possible issues, would you try the following > files on your box? > > http://people.freebsd.org/~yongari/re/if_re.c > http://people.freebsd.org/~yongari/re/if_rereg.h > > The latter is if_rlreg.h, I guess... Anyway they don't compile: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/dev/random/yarrow.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/dev/re/if_re.c /usr/src/sys/dev/re/if_re.c: In function 're_allocmem': /usr/src/sys/dev/re/if_re.c:997: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:998: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1017: error: 'RL_NTXSEGS' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1017: error: (Each undeclared identifier is reported only once /usr/src/sys/dev/re/if_re.c:1017: error: for each function it appears in.) /usr/src/sys/dev/re/if_re.c:1018: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1030: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1073: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1074: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1075: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1119: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1120: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1125: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1126: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1127: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c: In function 're_attach': /usr/src/sys/dev/re/if_re.c:1200: error: 'RL_CFG2_MSI' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1266: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1266: error: 'RL_8169_TX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1267: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1267: error: 'RL_8169_RX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1272: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1272: error: 'RL_8139_TX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1273: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1273: error: 'RL_8139_RX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_detach': /usr/src/sys/dev/re/if_re.c:1517: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1518: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1519: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1520: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1521: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1523: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1524: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1525: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1526: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:1527: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1528: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1529: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1530: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c: In function 're_discard_rxbuf': /usr/src/sys/dev/re/if_re.c:1561: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:1564: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1565: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_newbuf': /usr/src/sys/dev/re/if_re.c:1601: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1602: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1609: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:1610: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1611: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1611: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1611: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1613: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1613: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1613: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1616: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1617: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1618: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1618: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1619: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1620: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1621: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1621: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1621: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1629: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_tx_list_init': /usr/src/sys/dev/re/if_re.c:1666: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1667: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1668: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1670: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1679: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_rx_list_init': /usr/src/sys/dev/re/if_re.c:1691: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1692: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1693: error: 'struct rl_list_data' has no member named 'rl_rx_desc' cc1: warnings being treated as errors /usr/src/sys/dev/re/if_re.c: In function 're_rxeof': /usr/src/sys/dev/re/if_re.c:1737: warning: implicit declaration of function 'RL_RX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1737: warning: nested extern declaration of 'RL_RX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1744: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c: In function 're_txeof': /usr/src/sys/dev/re/if_re.c:1920: warning: implicit declaration of function 'RL_TX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1920: warning: nested extern declaration of 'RL_TX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1931: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1932: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1932: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1932: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1934: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1934: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1934: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1938: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1939: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1955: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_encap': /usr/src/sys/dev/re/if_re.c:2151: error: 'RL_NTXSEGS' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2213: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:2214: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2214: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2224: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2225: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2241: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2241: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2241: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2245: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2245: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2245: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2277: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:2286: warning: implicit declaration of function 'RL_TX_DESC_PRV' /usr/src/sys/dev/re/if_re.c:2286: warning: nested extern declaration of 'RL_TX_DESC_PRV' /usr/src/sys/dev/re/if_re.c:2308: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:2309: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2310: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2310: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2311: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2312: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2151: warning: unused variable 'segs' /usr/src/sys/dev/re/if_re.c: In function 're_ioctl': /usr/src/sys/dev/re/if_re.c:2662: error: 'RL_MAX_FRAMELEN' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_stop': /usr/src/sys/dev/re/if_re.c:2817: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:2818: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:2819: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2820: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2820: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2820: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2822: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2822: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2822: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2824: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2825: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2831: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:2832: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:2833: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2834: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2834: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2834: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2836: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2836: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:2836: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2838: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2839: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c: In function 're_setwol': /usr/src/sys/dev/re/if_re.c:2945: error: 'RL_CFG1_PME' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2950: error: 'RL_CFG3' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2951: error: 'RL_CFG3_WOL_LINK' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2951: error: 'RL_CFG3_WOL_MAGIC' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2959: error: 'RL_CFG5' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2960: error: 'RL_CFG5_WOL_BCAST' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2960: error: 'RL_CFG5_WOL_MCAST' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2960: error: 'RL_CFG5_WOL_UCAST' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2961: error: 'RL_CFG5_WOL_LANWAKE' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_clrwol': /usr/src/sys/dev/re/if_re.c:2999: error: 'RL_CFG3' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3000: error: 'RL_CFG3_WOL_LINK' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3000: error: 'RL_CFG3_WOL_MAGIC' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3006: error: 'RL_CFG5' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3007: error: 'RL_CFG5_WOL_BCAST' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3007: error: 'RL_CFG5_WOL_MCAST' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3007: error: 'RL_CFG5_WOL_UCAST' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3008: error: 'RL_CFG5_WOL_LANWAKE' undeclared (first use in this function) *** Error code 1 Stop in /usr/obj/usr/src/sys/FIREWALL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. dcsuff-db-data1# From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 14:11:43 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 095591065673; Thu, 13 Mar 2008 14:11:43 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id A3DAA8FC2B; Thu, 13 Mar 2008 14:11:42 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=YZJ0uYWOxs2xpaEoStMX5idK1O2r0HBLumlywQ+0IwKO6zY3KqsvEY1goKNeDlSiMvkKLS59rep9nPueS9plSL8u3AAzv3Xq+p2k19YRZGBeGSmpy9M7l+ZFHQ/6TM/3RMEEWyo054QTNv94NiESn8cs2M9CSOflbUYnXH1vUho=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JZo9k-000DZh-Tj; Thu, 13 Mar 2008 17:11:41 +0300 Date: Thu, 13 Mar 2008 17:11:39 +0300 From: Eygene Ryabinkin To: Giulio Ferro Message-ID: References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <47D92F9D.4070701@zirakzigil.org> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.7 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: pyunyh@gmail.com, freebsd-net@freebsd.org, Andrew Thompson Subject: Re: VLAN trunking and fragmentation 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, 13 Mar 2008 14:11:43 -0000 Giulio, good day. Thu, Mar 13, 2008 at 02:43:57PM +0100, Giulio Ferro wrote: > Pyun YongHyeon wrote: >> To rule out other possible issues, would you try the following >> files on your box? >> >> http://people.freebsd.org/~yongari/re/if_re.c >> http://people.freebsd.org/~yongari/re/if_rereg.h >> >> > The latter is if_rlreg.h, I guess... > > Anyway they don't compile: If you're running 7.x, you probably want to get the files from http://people.freebsd.org/~yongari/re/7.0R/ For 6.3 use http://people.freebsd.org/~yongari/re/6.3R/ I am running the 7.x flavour and it compiled without problems around two weeks ago. And it is working far more better then the original driver. You seem to use the version for the -CURRENT. -- Eygene From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 14:54:33 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1BF4106567A for ; Thu, 13 Mar 2008 14:54:33 +0000 (UTC) (envelope-from eagletree@hughes.net) Received: from n126.sc0.he.tucows.com (smtpout1111.sc0.he.tucows.com [64.97.144.111]) by mx1.freebsd.org (Postfix) with ESMTP id 921F08FC29 for ; Thu, 13 Mar 2008 14:54:33 +0000 (UTC) (envelope-from eagletree@hughes.net) Received: from sc0-out03.emaildefenseservice.com (64.97.131.2) by n126.sc0.he.tucows.com (7.2.069.1) id 47AEF770004FE0A5 for freebsd-net@freebsd.org; Thu, 13 Mar 2008 14:26:03 +0000 X-SpamScore: 2 X-Spamcatcher-Summary: 2, 0, 0, cc895812cb10ccaa, 8ed9ec56d2b75d02, eagletree@hughes.net, -, RULES_HIT:355:379:541:564:945:966:988:989:1260:1261:1277:1311:1313:1314:1345:1437:1515:1516:1518:1534:1539:1593:1594:1711:1730:1747:1766:1792:2196:2199:2393:2559:2562:3352:3622:3636:3690:3865:3867:3868:3869:3870:3871:3872:3873:3874:4250:4321:4362:4385:5007:7652, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:none, DNSBL:none X-Spamcatcher-Explanation: Received: from [192.168.0.3] (dpc6744118153.direcpc.com [67.44.118.153]) (Authenticated sender: eagletree@hughes.net) by sc0-out03.emaildefenseservice.com (Postfix) with ESMTP for ; Thu, 13 Mar 2008 14:25:57 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <759F7CF5-D47A-4431-88FF-B40FFDE0E24C@hughes.net> Content-Transfer-Encoding: 7bit From: Chris Date: Thu, 13 Mar 2008 07:16:17 -0700 To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.753) Subject: IPFW, DIVERT, and if_bridge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: snagit@cbpratt.prohosting.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Mar 2008 14:54:33 -0000 Hello, I posted a similar message to Questions but received no answer so I'm reposting a paraphrase here to see if anyone knows. I built FreeBSD 7.0 with options DIVERT and if_bridge to see if I could make snort_inline work with the bridging firewall I'm building. I found that the divert would not direct packets to snort_inline which sounded a little like the experiences people had when they tried to do this with the pre-6.x bridge. Is it still not possible to use divert with if_bridge? Here is what I'm seeing in ipfw. 65000 48 7382 count ip from any to any 65001 0 0 divert 8300 ip from any to any 65010 48 7382 allow ip from any to any Thank you, Chris Pratt From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 15:50:07 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 782551065673 for ; Thu, 13 Mar 2008 15:50:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 220DB8FC1B for ; Thu, 13 Mar 2008 15:50:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 4DE2E41C7AA; Thu, 13 Mar 2008 16:50:05 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id mrFwh1Jaas34; Thu, 13 Mar 2008 16:50:04 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id F05BC41C7AE; Thu, 13 Mar 2008 16:50:04 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id C789544487F; Thu, 13 Mar 2008 15:49:27 +0000 (UTC) Date: Thu, 13 Mar 2008 15:49:27 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Mike Silbersack In-Reply-To: <20080312232607.J60219@odysseus.silby.com> Message-ID: <20080313154547.F50685@maildrop.int.zabbadoz.net> References: <20080312231330.D60219@odysseus.silby.com> <20080312232607.J60219@odysseus.silby.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 13 Mar 2008 15:50:07 -0000 On Wed, 12 Mar 2008, Mike Silbersack wrote: > > On Wed, 12 Mar 2008, Mike Silbersack wrote: > >> I think we will need to fix tcpdump before trying to finish diagnosing this >> problem. We were missing key information before. >> >> -Mike > > Hm, that was far easier than expected. Patch attached. > > Here's what the two tcpdumps show now: > > 6.3: > IP A > B : S 2575736483:2575736483(0) ack 1762868649 win 65535 1460,sackOK,eol,eol> > > 7.0: > IP A > B : S 3304309835:3304309835(0) ack 710421411 win 65535 1380,sackOK,eol,nop> > > That makes the problem quite a bit more clear. Anyone working on this issue > should apply this patch ASAP. what do you think of this version? http://sources.zabbadoz.net/freebsd/patchset/20080313-01-tcpdump-print-tcp-option-padding.diff It should give you output like this: -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 15:52:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 142C11065675 for ; Thu, 13 Mar 2008 15:52:18 +0000 (UTC) (envelope-from ronr@econet.com) Received: from mx1.econet.com (hubble.sl.econet.com [208.70.186.171]) by mx1.freebsd.org (Postfix) with ESMTP id B86AA8FC2D for ; Thu, 13 Mar 2008 15:52:17 +0000 (UTC) (envelope-from ronr@econet.com) X-Virus-Scanned: amavisd-new at econet.com Received: from mx1.econet.com ([127.0.0.1]) by localhost.sl.econet.com (hubble.sl.econet.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSggirpqJnp0; Thu, 13 Mar 2008 10:34:24 -0500 (CDT) Received: from scalix.ops.econet.com (scalix.sl.econet.com [172.29.255.23]) by mx1.econet.com (Postfix) with ESMTP id 0661721042; Thu, 13 Mar 2008 10:34:24 -0500 (CDT) Received: from [192.168.32.69] (iresine.sl.econet.com [192.168.32.69]) by scalix.ops.econet.com (Postfix) with ESMTP id 2BE9184943D; Thu, 13 Mar 2008 10:40:19 -0500 (CDT) From: Ronald Roskens To: snagit@cbpratt.prohosting.com In-Reply-To: <759F7CF5-D47A-4431-88FF-B40FFDE0E24C@hughes.net> References: <759F7CF5-D47A-4431-88FF-B40FFDE0E24C@hughes.net> Content-Type: text/plain Date: Thu, 13 Mar 2008 10:34:19 -0500 Message-Id: <1205422459.62776.43.camel@iresine.sl.econet.com> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: IPFW, DIVERT, and if_bridge 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, 13 Mar 2008 15:52:18 -0000 On Thu, 2008-03-13 at 07:16 -0700, Chris wrote: > Hello, > > I posted a similar message to Questions but received no > answer so I'm reposting a paraphrase here to see if anyone > knows. > > I built FreeBSD 7.0 with options DIVERT and if_bridge to > see if I could make snort_inline work with the bridging > firewall I'm building. I found that the divert would not > direct packets to snort_inline which sounded a little like > the experiences people had when they tried to do this > with the pre-6.x bridge. > > Is it still not possible to use divert with if_bridge? Here > is what I'm seeing in ipfw. > > 65000 48 7382 count ip from any to any > 65001 0 0 divert 8300 ip from any to any > 65010 48 7382 allow ip from any to any Yes, it is possible to use divert with if_bridge and ipfw. It sounds like you have not enabled packet filtering on the bridge. I use the following: # /etc/sysctl.conf net.link.ether.ipfw=1 net.link.bridge.ipfw=0 net.link.bridge.pfil_bridge=0 net.link.bridge.pfil_member=1 # ipfw.conf 10000 divert 8000 ip from any to any out via bridge0 > > Thank you, > Chris Pratt > > _______________________________________________ > 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 Thu Mar 13 16:05:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F0A31065672 for ; Thu, 13 Mar 2008 16:05:18 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 7F9AC8FC13 for ; Thu, 13 Mar 2008 16:05:16 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 64372 invoked by uid 98); 13 Mar 2008 16:05:14 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.175962 secs); 13 Mar 2008 16:05:14 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.175962 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 13 Mar 2008 16:05:14 -0000 Message-ID: <47D950AD.7080505@zirakzigil.org> Date: Thu, 13 Mar 2008 17:05:01 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: Eygene Ryabinkin , freebsd-net@freebsd.org References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, Andrew Thompson Subject: Re: VLAN trunking and fragmentation 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, 13 Mar 2008 16:05:18 -0000 Eygene Ryabinkin wrote: > Giulio, good day. > > Thu, Mar 13, 2008 at 02:43:57PM +0100, Giulio Ferro wrote: > >> Pyun YongHyeon wrote: >> >>> To rule out other possible issues, would you try the following >>> files on your box? >>> >>> http://people.freebsd.org/~yongari/re/if_re.c >>> http://people.freebsd.org/~yongari/re/if_rereg.h >>> >>> >>> >> The latter is if_rlreg.h, I guess... >> >> Anyway they don't compile: >> > > If you're running 7.x, you probably want to get the files from > http://people.freebsd.org/~yongari/re/7.0R/ > Yes, these are the files I'm now using... # md5 if_re.c MD5 (if_re.c) = bab9ab56e24b5090b9cac6f697736602 # md5 if_rlreg.h MD5 (if_rlreg.h) = aa08e0f34bf394f7e43d180f0ffdd855 # uname -a FreeBSD x.x.x 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon Mar 10 13:28:18 CET 2008 root@x.x.x:/usr/obj/usr/src/sys/FIREWALL amd64 And this is how it aborts: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/dev/re/if_re.c /usr/src/sys/dev/re/if_re.c: In function 're_allocmem': /usr/src/sys/dev/re/if_re.c:999: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1000: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1019: error: 'RL_NTXSEGS' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1019: error: (Each undeclared identifier is reported only once /usr/src/sys/dev/re/if_re.c:1019: error: for each function it appears in.) /usr/src/sys/dev/re/if_re.c:1020: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1032: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1075: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1076: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1077: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1121: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1122: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1127: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1128: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1129: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c: In function 're_attach': /usr/src/sys/dev/re/if_re.c:1260: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1260: error: 'RL_8169_TX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1261: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1261: error: 'RL_8169_RX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1266: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1266: error: 'RL_8139_TX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1267: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1267: error: 'RL_8139_RX_DESC_CNT' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_detach': /usr/src/sys/dev/re/if_re.c:1503: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1504: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1505: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1506: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1507: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1509: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1510: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1511: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1512: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:1513: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1514: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1515: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1516: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c: In function 're_discard_rxbuf': /usr/src/sys/dev/re/if_re.c:1547: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:1550: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1551: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_newbuf': /usr/src/sys/dev/re/if_re.c:1587: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1588: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1595: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:1596: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1597: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1597: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1597: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1599: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1599: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1599: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1602: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1603: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1604: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1604: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1605: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1606: error: 'struct rl_list_data' has no member named 'rl_rx_sparemap' /usr/src/sys/dev/re/if_re.c:1607: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1607: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:1607: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1615: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_tx_list_init': /usr/src/sys/dev/re/if_re.c:1652: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1653: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1654: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1656: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1665: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_rx_list_init': /usr/src/sys/dev/re/if_re.c:1677: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1678: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:1679: error: 'struct rl_list_data' has no member named 'rl_rx_desc' cc1: warnings being treated as errors /usr/src/sys/dev/re/if_re.c: In function 're_rxeof': /usr/src/sys/dev/re/if_re.c:1723: warning: implicit declaration of function 'RL_RX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1723: warning: nested extern declaration of 'RL_RX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1730: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c: In function 're_txeof': /usr/src/sys/dev/re/if_re.c:1906: warning: implicit declaration of function 'RL_TX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1906: warning: nested extern declaration of 'RL_TX_DESC_NXT' /usr/src/sys/dev/re/if_re.c:1917: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:1918: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1918: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1918: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1920: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1920: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:1920: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1924: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1925: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:1941: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c: In function 're_encap': /usr/src/sys/dev/re/if_re.c:2137: error: 'RL_NTXSEGS' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2199: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:2200: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2200: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2210: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2211: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2227: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2227: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2227: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2231: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2231: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2231: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2263: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:2272: warning: implicit declaration of function 'RL_TX_DESC_PRV' /usr/src/sys/dev/re/if_re.c:2272: warning: nested extern declaration of 'RL_TX_DESC_PRV' /usr/src/sys/dev/re/if_re.c:2294: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:2295: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2296: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2296: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2297: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2298: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2137: warning: unused variable 'segs' /usr/src/sys/dev/re/if_re.c: In function 're_stop': /usr/src/sys/dev/re/if_re.c:2781: error: 'struct rl_list_data' has no member named 'rl_tx_desc_cnt' /usr/src/sys/dev/re/if_re.c:2782: error: 'struct rl_list_data' has no member named 'rl_tx_desc' /usr/src/sys/dev/re/if_re.c:2783: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2784: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2784: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2784: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2786: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2786: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2786: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2788: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2789: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2795: error: 'struct rl_list_data' has no member named 'rl_rx_desc_cnt' /usr/src/sys/dev/re/if_re.c:2796: error: 'struct rl_list_data' has no member named 'rl_rx_desc' /usr/src/sys/dev/re/if_re.c:2797: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2798: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2798: error: 'struct rl_list_data' has no member named 'rl_tx_mtag' /usr/src/sys/dev/re/if_re.c:2798: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2800: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2800: error: 'struct rl_list_data' has no member named 'rl_rx_mtag' /usr/src/sys/dev/re/if_re.c:2800: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2802: error: dereferencing pointer to incomplete type /usr/src/sys/dev/re/if_re.c:2803: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/obj/usr/src/sys/FIREWALL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 16:22:30 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D70C4106566B for ; Thu, 13 Mar 2008 16:22:30 +0000 (UTC) (envelope-from eagletree@hughes.net) Received: from n120.sc0.he.tucows.com (smtpout1077.sc0.he.tucows.com [64.97.144.77]) by mx1.freebsd.org (Postfix) with ESMTP id A70558FC1C for ; Thu, 13 Mar 2008 16:22:30 +0000 (UTC) (envelope-from eagletree@hughes.net) Received: from sc0-out03.emaildefenseservice.com (64.97.131.2) by n120.sc0.he.tucows.com (7.2.069.1) id 476BFC810127B6F9 for freebsd-net@freebsd.org; Thu, 13 Mar 2008 16:22:29 +0000 X-SpamScore: 2 X-Spamcatcher-Summary: 2, 0, 0, 0a42cc5372cd4012, 341093f8f759d937, eagletree@hughes.net, -, RULES_HIT:355:379:541:564:599:601:945:966:967:973:980:988:989:1260:1261:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1766:1792:2196:2199:2393:2525:2553:2559:2563:2682:2685:2857:2859:2902:2933:2937:2939:2942:2945:2947:2951:2954:3022:3027:3354:3636:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:4250:4321:4362:4385:4860:5007:7652: 7679, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:none, DNSBL:none X-Spamcatcher-Explanation: Received: from [192.168.0.3] (dpc6744118153.direcpc.com [67.44.118.153]) (Authenticated sender: eagletree@hughes.net) by sc0-out03.emaildefenseservice.com (Postfix) with ESMTP for ; Thu, 13 Mar 2008 16:22:25 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <1205422459.62776.43.camel@iresine.sl.econet.com> References: <759F7CF5-D47A-4431-88FF-B40FFDE0E24C@hughes.net> <1205422459.62776.43.camel@iresine.sl.econet.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chris Pratt Date: Thu, 13 Mar 2008 09:12:46 -0700 To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.753) Subject: Re: IPFW, DIVERT, and if_bridge 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, 13 Mar 2008 16:22:31 -0000 On Mar 13, 2008, at 8:34 AM, Ronald Roskens wrote: > On Thu, 2008-03-13 at 07:16 -0700, Chris wrote: >> Hello, >> >> I posted a similar message to Questions but received no >> answer so I'm reposting a paraphrase here to see if anyone >> knows. >> >> I built FreeBSD 7.0 with options DIVERT and if_bridge to >> see if I could make snort_inline work with the bridging >> firewall I'm building. I found that the divert would not >> direct packets to snort_inline which sounded a little like >> the experiences people had when they tried to do this >> with the pre-6.x bridge. >> >> Is it still not possible to use divert with if_bridge? Here >> is what I'm seeing in ipfw. >> >> 65000 48 7382 count ip from any to any >> 65001 0 0 divert 8300 ip from any to any >> 65010 48 7382 allow ip from any to any > > Yes, it is possible to use divert with if_bridge and ipfw. It sounds > like you have not enabled packet filtering on the bridge. > > I use the following: > > # /etc/sysctl.conf > net.link.ether.ipfw=1 > net.link.bridge.ipfw=0 > net.link.bridge.pfil_bridge=0 > net.link.bridge.pfil_member=1 > > # ipfw.conf > 10000 divert 8000 ip from any to any out via bridge0 Thanks very much. I had commented out two of these. The reason was that I was unable to differentiate between the local interface and the bridge (this is from memory). The reason isn't relevant anymore so I've set them correctly. The divert appears to work fine now as shown. 65000 5 288 count ip from any to any 65001 5 288 divert 8300 ip from any to any 65010 0 0 allow ip from any to any Thank you very much. > >> >> Thank you, >> Chris Pratt >> >> _______________________________________________ >> 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 Thu Mar 13 22:24:01 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00652106566B for ; Thu, 13 Mar 2008 22:24:00 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail05.adl2.internode.on.net (ipmail05.adl2.internode.on.net [203.16.214.145]) by mx1.freebsd.org (Postfix) with ESMTP id 73F0B8FC1C for ; Thu, 13 Mar 2008 22:23:59 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AogFAL9A2Ud5LWvf/2dsb2JhbACBWqhp X-IronPort-AV: E=Sophos;i="4.25,496,1199626200"; d="scan'208";a="75049769" Received: from ppp121-45-107-223.lns10.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.107.223]) by ipmail05.adl2.internode.on.net with ESMTP; 14 Mar 2008 08:38:37 +1030 Received: from [192.168.155.54] (taurus.internal.clearchain.com [192.168.155.54]) (authenticated bits=0) by mail.clearchain.com (8.14.2/8.14.2) with ESMTP id m2DM8IFG062770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 08:38:18 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <47D9A5E3.1020900@clearchain.com> Date: Fri, 14 Mar 2008 08:38:35 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Sam Leffler References: <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl> <47D6FB5B.3020107@clearchain.com> <1205366956.2082.13.camel@localhost> <47D88DC0.1010903@freebsd.org> In-Reply-To: <47D88DC0.1010903@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (mail.clearchain.com [192.168.154.1]); Fri, 14 Mar 2008 08:38:21 +1030 (CST) Cc: freebsd-net@freebsd.org, Yousif Hassan , Mel , Alphons Fonz van Werven , freebsd-mobile@freebsd.org Subject: Re: [Wireless] Can't connect to wlan 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, 13 Mar 2008 22:24:01 -0000 Sam Leffler wrote: > Yousif Hassan wrote: >> On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: >> >>> Alphons "Fonz" van Werven wrote: >>> >>>> Mel wrote: >>>> >>>> >>>>>> Do the recent patches by Andrew make a difference? >>>>>> >>>>>> http://people.freebsd.org/~thompsa/wpi_head.diff >>>>>> http://people.freebsd.org/~thompsa/wpi_releng7.diff >>>>>> >> >> (ccing freebsd-net) >> >> Ben, >> >> I had a go with this patch today on top of 7.0-RELEASE. >> >> The good: >> - Switching off the radio and back on finally works - nice work. >> - Scanning seems faster (but see caveat below) >> - Association is MUCH faster (mind you, I don't use an encrypted AP). >> - The "failed to align memory" stuff when the driver loads up - >> fixed. - The fact that it reloaded in the kernel even if I manually >> kldunloaded >> if_wpi.ko - fixed >> >> The slightly wonky: >> - As reported by someone else: >> wpi0: timeout resetting Tx ring 1 >> wpi0: timeout resetting Tx ring 3 >> wpi0: timeout resetting Tx ring 4 >> appear on startup and occasionally on kldload - however they don't >> appear to adversely affect too much >> >> The ugly: >> - I can only do an ifconfig wpi0 scan every OTHER time - in between >> successful attempts, I get >> wpi0: fatal firmware error >> wpi0: timeout resetting Tx ring (or: timeout resetting Tx ring 0) >> wpi0: link state changed to DOWN >> >> This wouldn't be so bad since it works every other time, but the >> problem is that every time I do a scan, it sets the link state down, >> causing the connection to drop - doesn't seem normal. Of course then it >> comes right back up but the network interruption is not so great. >> >> Hmm - what else? The whole thing seems - livelier. I need to run some >> throughput benchmarks but traffic to/from the card on my local network >> seems faster and more responsive. Hopefully this isn't the placebo >> effect. ;) >> >> Great work to you & rest of team on this patch... it's more than usable >> at this point! >> > > wpi doesn't yet support background scan so doing an explicit scan from > the command line will disconnect you from any ap you care connected > to. It shouldn't be hard to add bgscan--but that's easy for me to say :) > It's certainly on my todo list! Cheers, Benjamin From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 00:17:16 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 457CB106566B for ; Fri, 14 Mar 2008 00:17:16 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.180]) by mx1.freebsd.org (Postfix) with ESMTP id CC7268FC13 for ; Fri, 14 Mar 2008 00:17:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so2117837ele.12 for ; Thu, 13 Mar 2008 17:17:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=MkS6MWXN5gTUswCWBbxQVGGBEmpHtnHrPLn4PVtMivI=; b=Z7Z9wMn9MjyKxsSxg4bqeSrG+8MVK/SyGJlWiLfmAM1rZtTAEmt+FEBiESkKe8S/BtTr4JBV5+LpkkHY1xAKJghwbHjxWoO6OMFDAiXKakd0mL210Lq2p9kZmaw89nmR3OGawMmlVYBqLEzKgPeTSxAPzMLh6e9ggRTwlrLC1Mw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=oPDGWR7FyHuYiXiid484cZKuf3a86PiVj0VSf8g9Ct3khW32GLxj37+zT/spFfLCprJ932939ujvuwTH4L+14ok1DxdUXKeXegSwdiQEfXGrwTxuJ7LK4JQsXYHR1lbDtQqQgnoElWfSR1qd6g7pSSVx14zbrk+o9CI009uFCuk= Received: by 10.151.78.15 with SMTP id f15mr5810691ybl.187.1205453834920; Thu, 13 Mar 2008 17:17:14 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 9sm19978096wrl.31.2008.03.13.17.17.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Mar 2008 17:17:13 -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 m2E0H66s022991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 09:17:06 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2E0H5Kf022990; Fri, 14 Mar 2008 09:17:05 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 14 Mar 2008 09:17:04 +0900 From: Pyun YongHyeon To: Giulio Ferro Message-ID: <20080314001704.GA22788@cdnetworks.co.kr> References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47D92F9D.4070701@zirakzigil.org> User-Agent: Mutt/1.4.2.1i Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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: Fri, 14 Mar 2008 00:17:16 -0000 On Thu, Mar 13, 2008 at 02:43:57PM +0100, Giulio Ferro wrote: > Pyun YongHyeon wrote: > >To rule out other possible issues, would you try the following > >files on your box? > > > >http://people.freebsd.org/~yongari/re/if_re.c > >http://people.freebsd.org/~yongari/re/if_rereg.h ^^^^^^^^^^ Should be read if_rlreg.h > > > > > The latter is if_rlreg.h, I guess... Oops, yes. > > Anyway they don't compile: > Maybe you don't copy if_rlreg.h to /usr/src/sys/pci directory? The above files have latest fixes I'd like to commit and it should build without problems on CURRENT/RELENG_7/7.0-RELEASE. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 00:40:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A59A1065671 for ; Fri, 14 Mar 2008 00:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 45ABA8FC12 for ; Fri, 14 Mar 2008 00:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2E0e3ZG048697 for ; Fri, 14 Mar 2008 00:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2E0e34m048696; Fri, 14 Mar 2008 00:40:03 GMT (envelope-from gnats) Date: Fri, 14 Mar 2008 00:40:03 GMT Message-Id: <200803140040.m2E0e34m048696@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: James Snow Cc: Subject: Re: kern/120958: no response to ICMP traffic on interface configured with a link-local address X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: James Snow List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 00:40:03 -0000 The following reply was made to PR kern/120958; it has been noted by GNATS. From: James Snow To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/120958: no response to ICMP traffic on interface configured with a link-local address Date: Thu, 13 Mar 2008 20:23:55 -0400 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Attached is a patch that reworks the problematic if statement in sys/netinet/ip_icmp.c and adds two new macros to sys/netinet/in.h. This fixes the problem, and eliminates a duplicate check for loopback addresses. (Although it introduces some redundant ntohl() calls.) -Snow --IS0zKkzwUGydFO0o Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="link-local-icmp.patch" diff -ru /usr/src/sys/netinet/in.h /usr/src.new/sys/netinet/in.h --- /usr/src/sys/netinet/in.h 2007-06-12 16:24:53.000000000 +0000 +++ /usr/src.new/sys/netinet/in.h 2008-03-13 10:44:29.000000000 +0000 @@ -379,6 +379,8 @@ #define IN_BADCLASS(i) (((u_int32_t)(i) & 0xf0000000) == 0xf0000000) #define IN_LINKLOCAL(i) (((u_int32_t)(i) & 0xffff0000) == 0xa9fe0000) +#define IN_LOOPBACK(i) (((u_int32_t)(i) & 0xff000000) == 0x7f000000) +#define IN_ZERONET(i) (((u_int32_t)(i) & 0xff000000) == 0) #define IN_PRIVATE(i) ((((u_int32_t)(i) & 0xff000000) == 0x0a000000) || \ (((u_int32_t)(i) & 0xfff00000) == 0xac100000) || \ diff -ru /usr/src/sys/netinet/ip_icmp.c /usr/src.new/sys/netinet/ip_icmp.c --- /usr/src/sys/netinet/ip_icmp.c 2007-10-07 20:44:23.000000000 +0000 +++ /usr/src.new/sys/netinet/ip_icmp.c 2008-03-13 11:03:44.000000000 +0000 @@ -622,13 +622,14 @@ struct mbuf *opts = 0; int optlen = (ip->ip_hl << 2) - sizeof(struct ip); - if (!in_canforward(ip->ip_src) && - ((ntohl(ip->ip_src.s_addr) & IN_CLASSA_NET) != - (IN_LOOPBACKNET << IN_CLASSA_NSHIFT))) { + if (IN_MULTICAST(ntohl(ip->ip_src.s_addr)) || + IN_EXPERIMENTAL(ntohl(ip->ip_src.s_addr)) || + IN_ZERONET(ntohl(ip->ip_src.s_addr)) ) { m_freem(m); /* Bad return address */ icmpstat.icps_badaddr++; goto done; /* Ip_output() will check for broadcast */ } + t = ip->ip_dst; ip->ip_dst = ip->ip_src; --IS0zKkzwUGydFO0o-- From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 00:40:08 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B15AB106567D; Fri, 14 Mar 2008 00:40:08 +0000 (UTC) (envelope-from snow@teardrop.org) Received: from silver.teardrop.org (silver.teardrop.org [66.92.75.234]) by mx1.freebsd.org (Postfix) with ESMTP id 79A218FC13; Fri, 14 Mar 2008 00:40:08 +0000 (UTC) (envelope-from snow@teardrop.org) Received: by silver.teardrop.org (Postfix, from userid 100) id C5B6A958B7; Thu, 13 Mar 2008 20:40:07 -0400 (EDT) Date: Thu, 13 Mar 2008 20:40:07 -0400 From: James Snow To: "Bruce M. Simpson" Message-ID: <20080314004007.GC92537@teardrop.org> References: <200802222124.m1MLO7qq012802@freefall.freebsd.org> <47BF46DC.6030700@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="dTy3Mrz/UPE2dbVg" Content-Disposition: inline In-Reply-To: <47BF46DC.6030700@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@FreeBSD.org Subject: [PATCH] kern/120958: no response to ICMP traffic on interface configured with a link-local address 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, 14 Mar 2008 00:40:08 -0000 --dTy3Mrz/UPE2dbVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Feb 22, 2008 at 10:04:12PM +0000, Bruce M. Simpson wrote: > I looked at this very briefly. > > It's gnarly because in_canforward() is a candidate for inlining and is a > predicate which is being overloaded with different meanings by > ip_forward()/ip_input() and icmp_reflect(). > > So whilst the fix is most likely a 3 liner, it risks making the code > look crap. We genuinely don't want to forward 169.254.0.0/16 traffic, > however we genuinely need to reply to ICMP which originates from these > ranges. Attached is a patch that fixes the failure to respond to ICMP for link-local addresses. I reworked the opening if statement in icmp_reflect() to make it a touch more readable, and eliminated the call to in_canforward() since its logic doesn't work in this context. Also, I took a cue from the IN_LINKLOCAL() macro and added two new macros to sys/netinet/in.h to perform checks for the loopback network and the "zero" network. IN_LOOPBACK() and IN_ZERONET(), respectively. IN_ZERONET seems like a lousy name, but the only alternative I could find in RFC3330 was "'this' net," and IN_THISNET wasn't an improvement. -Snow --dTy3Mrz/UPE2dbVg Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="link-local-icmp.patch" diff -ru /usr/src/sys/netinet/in.h /usr/src.new/sys/netinet/in.h --- /usr/src/sys/netinet/in.h 2007-06-12 16:24:53.000000000 +0000 +++ /usr/src.new/sys/netinet/in.h 2008-03-13 10:44:29.000000000 +0000 @@ -379,6 +379,8 @@ #define IN_BADCLASS(i) (((u_int32_t)(i) & 0xf0000000) == 0xf0000000) #define IN_LINKLOCAL(i) (((u_int32_t)(i) & 0xffff0000) == 0xa9fe0000) +#define IN_LOOPBACK(i) (((u_int32_t)(i) & 0xff000000) == 0x7f000000) +#define IN_ZERONET(i) (((u_int32_t)(i) & 0xff000000) == 0) #define IN_PRIVATE(i) ((((u_int32_t)(i) & 0xff000000) == 0x0a000000) || \ (((u_int32_t)(i) & 0xfff00000) == 0xac100000) || \ diff -ru /usr/src/sys/netinet/ip_icmp.c /usr/src.new/sys/netinet/ip_icmp.c --- /usr/src/sys/netinet/ip_icmp.c 2007-10-07 20:44:23.000000000 +0000 +++ /usr/src.new/sys/netinet/ip_icmp.c 2008-03-13 11:03:44.000000000 +0000 @@ -622,13 +622,14 @@ struct mbuf *opts = 0; int optlen = (ip->ip_hl << 2) - sizeof(struct ip); - if (!in_canforward(ip->ip_src) && - ((ntohl(ip->ip_src.s_addr) & IN_CLASSA_NET) != - (IN_LOOPBACKNET << IN_CLASSA_NSHIFT))) { + if (IN_MULTICAST(ntohl(ip->ip_src.s_addr)) || + IN_EXPERIMENTAL(ntohl(ip->ip_src.s_addr)) || + IN_ZERONET(ntohl(ip->ip_src.s_addr)) ) { m_freem(m); /* Bad return address */ icmpstat.icps_badaddr++; goto done; /* Ip_output() will check for broadcast */ } + t = ip->ip_dst; ip->ip_dst = ip->ip_src; --dTy3Mrz/UPE2dbVg-- From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 00:58:27 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2035D1065670 for ; Fri, 14 Mar 2008 00:58:27 +0000 (UTC) (envelope-from snow@teardrop.org) Received: from silver.teardrop.org (silver.teardrop.org [66.92.75.234]) by mx1.freebsd.org (Postfix) with ESMTP id DF6CD8FC12 for ; Fri, 14 Mar 2008 00:58:26 +0000 (UTC) (envelope-from snow@teardrop.org) Received: by silver.teardrop.org (Postfix, from userid 100) id D6401958B7; Thu, 13 Mar 2008 20:58:25 -0400 (EDT) Date: Thu, 13 Mar 2008 20:58:25 -0400 From: James Snow To: freebsd-net@FreeBSD.org Message-ID: <20080314005825.GD92537@teardrop.org> References: <200802222124.m1MLO7qq012802@freefall.freebsd.org> <47BF46DC.6030700@FreeBSD.org> <20080314004007.GC92537@teardrop.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VywGB/WGlW4DM4P8" Content-Disposition: inline In-Reply-To: <20080314004007.GC92537@teardrop.org> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: [PATCH] kern/120958: no response to ICMP traffic on interface configured with a link-local address 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, 14 Mar 2008 00:58:27 -0000 --VywGB/WGlW4DM4P8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Mar 13, 2008 at 08:40:07PM -0400, James Snow wrote: > > Also, I took a cue from the IN_LINKLOCAL() macro and added two new > macros to sys/netinet/in.h to perform checks for the loopback network > and the "zero" network. IN_LOOPBACK() and IN_ZERONET(), respectively. Woops. I suppose the macros are more useful when they're actually called. Attached is a revised patch that performs the check for loopback addresses less than twice but more than never. -Snow --VywGB/WGlW4DM4P8 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="link-local-icmp-revised.patch" diff -ru src/sys/netinet/in.h src.new/sys/netinet/in.h --- src/sys/netinet/in.h 2007-06-12 16:24:53.000000000 +0000 +++ src.new/sys/netinet/in.h 2008-03-13 10:44:29.000000000 +0000 @@ -379,6 +379,8 @@ #define IN_BADCLASS(i) (((u_int32_t)(i) & 0xf0000000) == 0xf0000000) #define IN_LINKLOCAL(i) (((u_int32_t)(i) & 0xffff0000) == 0xa9fe0000) +#define IN_LOOPBACK(i) (((u_int32_t)(i) & 0xff000000) == 0x7f000000) +#define IN_ZERONET(i) (((u_int32_t)(i) & 0xff000000) == 0) #define IN_PRIVATE(i) ((((u_int32_t)(i) & 0xff000000) == 0x0a000000) || \ (((u_int32_t)(i) & 0xfff00000) == 0xac100000) || \ diff -ru src/sys/netinet/ip_icmp.c src.new/sys/netinet/ip_icmp.c --- src/sys/netinet/ip_icmp.c 2007-10-07 20:44:23.000000000 +0000 +++ src.new/sys/netinet/ip_icmp.c 2008-03-14 00:47:44.000000000 +0000 @@ -622,13 +622,15 @@ struct mbuf *opts = 0; int optlen = (ip->ip_hl << 2) - sizeof(struct ip); - if (!in_canforward(ip->ip_src) && - ((ntohl(ip->ip_src.s_addr) & IN_CLASSA_NET) != - (IN_LOOPBACKNET << IN_CLASSA_NSHIFT))) { + if (IN_MULTICAST(ntohl(ip->ip_src.s_addr)) || + IN_EXPERIMENTAL(ntohl(ip->ip_src.s_addr)) || + IN_LOOPBACK(ntohl(ip->ip_src.s_addr)) || + IN_ZERONET(ntohl(ip->ip_src.s_addr)) ) { m_freem(m); /* Bad return address */ icmpstat.icps_badaddr++; goto done; /* Ip_output() will check for broadcast */ } + t = ip->ip_dst; ip->ip_dst = ip->ip_src; --VywGB/WGlW4DM4P8-- From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 03:22:15 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0309F106566B for ; Fri, 14 Mar 2008 03:22:15 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.freebsd.org (Postfix) with ESMTP id ADC6E8FC19 for ; Fri, 14 Mar 2008 03:22:14 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so4241110wxd.7 for ; Thu, 13 Mar 2008 20:22:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=Jk+jmB/cwfuuiUmg402JkDJIo2OIyvkHmzVz7KKVR+8=; b=jHmwba/Mh3rUDaMd60oMdOgQQd14RR4noCEEipcdYV/zCLH9nrV9tu9Veq4u9AtTYSdye89hVYUZsugHXemq1F7QZkHcm/K5NHfHZRfxtm6kNiOu1KE7XX0bd/vUbP7eH0mUK1CCBzLjTYdWZogajW0p9vK7xtVUxbUTRCccpSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=N1gSZqkhPuu7PmiZRfoSfLdAT4sBXCif3X4E5XNtJIkeHJBull7bA4LIYKkQWOWubq3bRvsxMXljfn+87V/NpQOXkrc88Z2RBKaIYoNTzbHsfkpgecw6Zvg8zRYjnTAfB+P7D4/eLBoiD70KoB1WO7Y1UYEdsIzDDASFzgBQgDc= Received: by 10.70.75.12 with SMTP id x12mr11398385wxa.68.1205463365514; Thu, 13 Mar 2008 19:56:05 -0700 (PDT) Received: from ?192.168.1.2? ( [24.229.62.9]) by mx.google.com with ESMTPS id i40sm1268129wxd.9.2008.03.13.19.56.03 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Mar 2008 19:56:04 -0700 (PDT) From: Glen Barber To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Date: Thu, 13 Mar 2008 22:56:01 -0400 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803132256.01197.glen.j.barber@gmail.com> Cc: Subject: ndis0 no link on 6.3-RELEASE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 03:22:15 -0000 Hello everyone. First off, sorry for the double post, but I'm not 100% certain at where this post belongs. I've found via Google many problems with ndis0 and failure to find a link in 6.3-RELEASE, without resolution. So here's my setup. I'm using a Broadcom 4318 chipset, with drivers created from ndisgen. If you need more specific information on the drivers, I'll be more than happy to provide information, however I believe it to be irrelevant at this moment, as I have used more than one driver version, with the same results. In 6.3-RC1 and below (tested in 6.2-RELEASE, and all -STABLE releases in between), my ndis0 adapter works as exptected, using WPA and DHCP. I can't pinpoint exaclty what changed (I've check in /usr/src/UPDATING, as it seemed to be most relevant), with no avail to finding anything regarding either wpa or dhclient. Since an upgrade to 6.3-RELEASE (both, via csup and a fresh install off of cd), I generate my ndis module, create an /etc/wpa_supplicant.conf, leaving /etc/dhclient as default, and am prompted with: ndis0: no link.......... giving up Upon 'kldunload bcmwl5.ko; kldload bcmwl5.ko', my ndis0 card looses all WPA capabilities. What seems to me to be the interesting part is this: If I 'csup' to 6.3-RELEASE from -RC1, and build a kernel, the problem does not occur -- as long as I do not 'buildworld'. However, once I 'buildworld; installworld', I am faced with the same problems as if I had installed 6.3-RELEASE from cd. I would really like to figure out what is causing this (both for myself, and the other affected ndis0 victims), but I'm not sure where to look -- dhclient, wpa_supplicant or ndis itself. Any other information I could provide, please let me know. Thanks. -- Glen Barber (570)328-0318 http://www.dev-urandom.com/ From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 05:53:34 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D11C1065671 for ; Fri, 14 Mar 2008 05:53:34 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.freebsd.org (Postfix) with SMTP id CE0648FC1D for ; Fri, 14 Mar 2008 05:53:33 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 54804 invoked from network); 14 Mar 2008 05:53:32 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 14 Mar 2008 05:53:32 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 14 Mar 2008 00:53:31 -0500 (CDT) From: Mike Silbersack To: "Bjoern A. Zeeb" In-Reply-To: <20080313154547.F50685@maildrop.int.zabbadoz.net> Message-ID: <20080314005224.S65945@odysseus.silby.com> References: <20080312231330.D60219@odysseus.silby.com> <20080312232607.J60219@odysseus.silby.com> <20080313154547.F50685@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "d.s. al coda" Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 14 Mar 2008 05:53:34 -0000 On Thu, 13 Mar 2008, Bjoern A. Zeeb wrote: > It should give you output like this: > > 19549200,sackOK,eol,0x01[bad padding]> I like the [bad padding]. > But I think the "good" case should look like it did before, per POLA. -Mike From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 10:05:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40BDC106566B for ; Fri, 14 Mar 2008 10:05:18 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 7DE9B8FC1D for ; Fri, 14 Mar 2008 10:05:17 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 72152 invoked by uid 98); 14 Mar 2008 10:05:14 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.043758 secs); 14 Mar 2008 10:05:14 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.043758 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 14 Mar 2008 10:05:14 -0000 Message-ID: <47DA4DCD.6050304@zirakzigil.org> Date: Fri, 14 Mar 2008 11:05:01 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: pyunyh@gmail.com References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> In-Reply-To: <20080314001704.GA22788@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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, 14 Mar 2008 10:05:18 -0000 Pyun YongHyeon wrote: > > The latter is if_rlreg.h, I guess... > > Oops, yes. > > > > Anyway they don't compile: > > > > Maybe you don't copy if_rlreg.h to /usr/src/sys/pci directory? > I didn't ;-) Ok, I compiled and installed it. The behavior didn't change: the simple ping works all right, but when I send a ping greater than 1472 byte and fragments, nothing passes through: # tcpdump -i re0 -n -vvv not stp tcpdump: listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes 11:49:38.004179 IP (tos 0x0, ttl 64, id 51279, offset 0, flags [+], proto ICMP (1), length 1500) 192.168.100.2 > 192.168.100.1: ICMP echo request, id 5, seq 0, length 1480 11:49:38.004183 IP (tos 0x0, ttl 64, id 51279, offset 1480, flags [none], proto ICMP (1), length 48) 192.168.100.2 > 192.168.100.1: icmp No packet reached the other PC. From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 10:15:08 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58284106566B for ; Fri, 14 Mar 2008 10:15:08 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3524A8FC14 for ; Fri, 14 Mar 2008 10:15:07 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 291D141C730; Fri, 14 Mar 2008 11:15:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 16XDt49L5vGX; Fri, 14 Mar 2008 11:15:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id C18CA41C729; Fri, 14 Mar 2008 11:15:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 46E7044487F; Fri, 14 Mar 2008 10:11:06 +0000 (UTC) Date: Fri, 14 Mar 2008 10:11:06 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Mike Silbersack In-Reply-To: <20080314005224.S65945@odysseus.silby.com> Message-ID: <20080314100707.F50685@maildrop.int.zabbadoz.net> References: <20080312231330.D60219@odysseus.silby.com> <20080312232607.J60219@odysseus.silby.com> <20080313154547.F50685@maildrop.int.zabbadoz.net> <20080314005224.S65945@odysseus.silby.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers 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, 14 Mar 2008 10:15:08 -0000 On Fri, 14 Mar 2008, Mike Silbersack wrote: > On Thu, 13 Mar 2008, Bjoern A. Zeeb wrote: > >> It should give you output like this: >> >> > 19549200,sackOK,eol,0x01[bad padding]> > > I like the [bad padding]. :-) >> > 19641135,sackOK,eol,0x00> > > But I think the "good" case should look like it did before, per POLA. Ok, I am only printing it in case bad padding happens or one gave -v. The new patch is here: http://sources.zabbadoz.net/freebsd/patchset/20080314-01-tcpdump-print-tcp-option-padding.diff -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 10:16:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02E5D1065673 for ; Fri, 14 Mar 2008 10:16:05 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id E45DA8FC1B for ; Fri, 14 Mar 2008 10:16:04 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so4420845waf.3 for ; Fri, 14 Mar 2008 03:16:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=wCqQc26qoRHvJnFbcnNUrm+aw7B4PCCXbcmHioPdJtc=; b=oGYTP39tG8g6Gjf4UY+DepBajxLfnzJroUyvVhDHlgYFkpAt1a/vd8GuvrD/uV23tXMvI1MUf9RSXRsRiGxH5ToGqadRGAYN6xDEHaPeDy1TL/Pptcnh2v2RAvsNCgGemxT9dtcsK9ntk/xF8ITugKSjfqbELGg2FhRJ0N9wrUo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=JH8/X/k6jynWqJVZrTICXO72j/CT6csr+h/m6qo7gDFXzKa2GoQFR/C50MGE3BZi6wysNXrEgVaXg4x/ZWCN5zRl9smdDfnBZ2SfWlA7bF0tL8UO/vyAxAEf0CJ296AjW9WalfRJMz53HV1L6iZG0yfnoVIVaiN6qtyozNlCk9Q= Received: by 10.114.150.1 with SMTP id x1mr11383157wad.46.1205489764153; Fri, 14 Mar 2008 03:16:04 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id g5sm20980825wra.33.2008.03.14.03.16.01 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Mar 2008 03:16:02 -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 m2EAFuga024507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 19:15:56 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2EAFt1o024506; Fri, 14 Mar 2008 19:15:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 14 Mar 2008 19:15:55 +0900 From: Pyun YongHyeon To: Giulio Ferro Message-ID: <20080314101555.GF22788@cdnetworks.co.kr> References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> <47DA4DCD.6050304@zirakzigil.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47DA4DCD.6050304@zirakzigil.org> User-Agent: Mutt/1.4.2.1i Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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: Fri, 14 Mar 2008 10:16:05 -0000 On Fri, Mar 14, 2008 at 11:05:01AM +0100, Giulio Ferro wrote: > Pyun YongHyeon wrote: > > > The latter is if_rlreg.h, I guess... > > > >Oops, yes. > > > > > > Anyway they don't compile: > > > > > > >Maybe you don't copy if_rlreg.h to /usr/src/sys/pci directory? > > > > I didn't ;-) > > Ok, I compiled and installed it. > > The behavior didn't change: the simple ping works all right, but when I > send a ping > greater than 1472 byte and fragments, nothing passes through: > > # tcpdump -i re0 -n -vvv not stp > tcpdump: listening on re0, link-type EN10MB (Ethernet), capture size 96 > bytes > > 11:49:38.004179 IP (tos 0x0, ttl 64, id 51279, offset 0, flags [+], > proto ICMP (1), length 1500) 192.168.100.2 > 192.168.100.1: ICMP echo > request, id 5, seq 0, length 1480 > 11:49:38.004183 IP (tos 0x0, ttl 64, id 51279, offset 1480, flags > [none], proto ICMP (1), length 48) 192.168.100.2 > 192.168.100.1: icmp > > > No packet reached the other PC. Ok, then try disabling hardware VLAN tagging. (#ifconfig re0 -vlanhwtag) -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 11:20:20 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37BF61065673; Fri, 14 Mar 2008 11:20:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 32CF68FC14; Fri, 14 Mar 2008 11:20:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2EBKKCg004308; Fri, 14 Mar 2008 11:20:20 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2EBKK7u004304; Fri, 14 Mar 2008 11:20:20 GMT (envelope-from linimon) Date: Fri, 14 Mar 2008 11:20:20 GMT Message-Id: <200803141120.m2EBKK7u004304@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121693: [nat] [panic] in kernel alias_irc nat double panic 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, 14 Mar 2008 11:20:20 -0000 Old Synopsis: in kernel alias_irc nat double panic New Synopsis: [nat] [panic] in kernel alias_irc nat double panic Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Mar 14 11:18:51 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=121693 From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 11:40:05 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8D731065674 for ; Fri, 14 Mar 2008 11:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C484B8FC23 for ; Fri, 14 Mar 2008 11:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2EBe5EK005891 for ; Fri, 14 Mar 2008 11:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2EBe55u005890; Fri, 14 Mar 2008 11:40:05 GMT (envelope-from gnats) Date: Fri, 14 Mar 2008 11:40:05 GMT Message-Id: <200803141140.m2EBe55u005890@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Vadim Goncharov Cc: Subject: Re: kern/121693: in kernel alias_irc nat double panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vadim Goncharov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 11:40:05 -0000 The following reply was made to PR kern/121693; it has been noted by GNATS. From: Vadim Goncharov To: Gael Roualland Cc: bug-followup@FreeBSD.org, eugen@kuzbass.ru Subject: Re: kern/121693: in kernel alias_irc nat double panic Date: Fri, 14 Mar 2008 17:06:39 +0600 Hi Gael Roualland! On Fri, 14 Mar 2008 09:28:14 GMT; Gael Roualland wrote: >>Number: 121693 >>Category: kern >>Synopsis: in kernel alias_irc nat double panic >>Confidential: no >>Severity: serious >>Priority: low >>Responsible: freebsd-bugs >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Fri Mar 14 09:40:00 UTC 2008 >>Closed-Date: >>Last-Modified: >>Originator: Gael Roualland >>Release: 7.0-STABLE >>Organization: >>Environment: > FreeBSD jerry.priv 7.0-STABLE FreeBSD 7.0-STABLE #0: Thu Mar 13 21:12:57 CET 2008 gael@jerry:/home/cvsup/obj/home/cvsup/src/sys/JERRY i386 >>Description: > Loading alias_irc in a kernel with nat activated leads to a kernel crash with a double panic a few seconds later when at least one irc connection is active to the outside (locally originated). > Unfortunately I do not have a backtrace available, core dump was lost. I will reproduce if needed to get it. Oops, sent letter with wrong PR number. This looks like the same bug as in kern/118432 on 6.3 - which has backtrace included. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 11:40:08 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D056106566B for ; Fri, 14 Mar 2008 11:40:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 18F318FC16 for ; Fri, 14 Mar 2008 11:40:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2EBe7Bp005941 for ; Fri, 14 Mar 2008 11:40:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2EBe7Qu005940; Fri, 14 Mar 2008 11:40:07 GMT (envelope-from gnats) Date: Fri, 14 Mar 2008 11:40:07 GMT Message-Id: <200803141140.m2EBe7Qu005940@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Vadim Goncharov Cc: Subject: Re: kern/121693: in kernel alias_irc nat double panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vadim Goncharov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 11:40:08 -0000 The following reply was made to PR kern/121693; it has been noted by GNATS. From: Vadim Goncharov To: Gael Roualland Cc: bug-followup@FreeBSD.org Subject: Re: kern/121693: in kernel alias_irc nat double panic Date: Fri, 14 Mar 2008 17:02:47 +0600 Hi Gael Roualland! On Fri, 14 Mar 2008 09:28:14 GMT; Gael Roualland wrote: >>Number: 121693 >>Category: kern >>Synopsis: in kernel alias_irc nat double panic >>Confidential: no >>Severity: serious >>Priority: low >>Responsible: freebsd-bugs >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Fri Mar 14 09:40:00 UTC 2008 >>Closed-Date: >>Last-Modified: >>Originator: Gael Roualland >>Release: 7.0-STABLE >>Organization: >>Environment: > FreeBSD jerry.priv 7.0-STABLE FreeBSD 7.0-STABLE #0: Thu Mar 13 21:12:57 CET 2008 gael@jerry:/home/cvsup/obj/home/cvsup/src/sys/JERRY i386 >>Description: > Loading alias_irc in a kernel with nat activated leads to a kernel crash with a double panic a few seconds later when at least one irc connection is active to the outside (locally originated). > Unfortunately I do not have a backtrace available, core dump was lost. I will reproduce if needed to get it. This is looks much the same like kern/121693 on 6.3, which has backtrace included. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 11:41:48 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50E401065679; Fri, 14 Mar 2008 11:41:48 +0000 (UTC) (envelope-from piso@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 439C78FC1C; Fri, 14 Mar 2008 11:41:48 +0000 (UTC) (envelope-from piso@FreeBSD.org) Received: from freefall.freebsd.org (piso@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2EBfmxA006027; Fri, 14 Mar 2008 11:41:48 GMT (envelope-from piso@freefall.freebsd.org) Received: (from piso@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2EBfmhZ006023; Fri, 14 Mar 2008 11:41:48 GMT (envelope-from piso) Date: Fri, 14 Mar 2008 11:41:48 GMT Message-Id: <200803141141.m2EBfmhZ006023@freefall.freebsd.org> To: piso@FreeBSD.org, freebsd-net@FreeBSD.org, piso@FreeBSD.org From: piso@FreeBSD.org Cc: Subject: Re: kern/121693: [nat] [panic] in kernel alias_irc nat double panic 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, 14 Mar 2008 11:41:48 -0000 Synopsis: [nat] [panic] in kernel alias_irc nat double panic Responsible-Changed-From-To: freebsd-net->piso@FreeBSD.org Responsible-Changed-By: piso Responsible-Changed-When: Fri Mar 14 11:40:28 UTC 2008 Responsible-Changed-Why: Assign it to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=121693 From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 11:48:04 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF6E6106566B for ; Fri, 14 Mar 2008 11:48:04 +0000 (UTC) (envelope-from vadim_nuclight@mail.ru) Received: from mx28.mail.ru (mx28.mail.ru [194.67.23.67]) by mx1.freebsd.org (Postfix) with ESMTP id B3D4A8FC26 for ; Fri, 14 Mar 2008 11:48:04 +0000 (UTC) (envelope-from vadim_nuclight@mail.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.23]) by mx28.mail.ru (mPOP.Fallback_MX) with ESMTP id 9B06E31934D for ; Fri, 14 Mar 2008 14:18:48 +0300 (MSK) Received: from [78.140.2.78] (port=42460 helo=nuclight.avtf.net) by mx27.mail.ru with asmtp id 1Ja7vV-000Cpw-00; Fri, 14 Mar 2008 14:18:18 +0300 To: bug-followup@freebsd.org, eugen@kuzbass.ru Date: Fri, 14 Mar 2008 17:18:11 +0600 From: "Vadim Goncharov" Organization: AVTF TPU Hostel Content-Type: text/plain; format=flowed; delsp=yes; charset=koi8-r MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera M2/7.54 (Win32, build 3865) Cc: "freebsd-ipfw@freebsd.org" , "freebsd-net@freebsd.org" Subject: Re: kern/118432: [ng_nat] [panic] kernel libalias: repeatable panic (double fault) 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, 14 Mar 2008 11:48:05 -0000 Hi! The issue seems to be reprodusable on 7.0 - see kern/121693. -- WBR, Vadim Goncharov From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 11:57:50 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03B861065673 for ; Fri, 14 Mar 2008 11:57:50 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 318188FC17 for ; Fri, 14 Mar 2008 11:57:48 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 73306 invoked by uid 98); 14 Mar 2008 11:57:47 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.04158 secs); 14 Mar 2008 11:57:47 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.04158 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 14 Mar 2008 11:57:47 -0000 Message-ID: <47DA682E.9010504@zirakzigil.org> Date: Fri, 14 Mar 2008 12:57:34 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: pyunyh@gmail.com References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> <47DA4DCD.6050304@zirakzigil.org> <20080314101555.GF22788@cdnetworks.co.kr> In-Reply-To: <20080314101555.GF22788@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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, 14 Mar 2008 11:57:50 -0000 Pyun YongHyeon wrote: > > No packet reached the other PC. > > Ok, then try disabling hardware VLAN tagging. > (#ifconfig re0 -vlanhwtag) > > That's it! Now seems to work properly, the problem then is with hardware tagging. My question now is: can I use vlans without htag in a complex system with heavy traffic without a significant performance loss? If not, how much will it take to fix the issue with the driver? Thanks for your answer. From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 12:14:55 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A82121065671 for ; Fri, 14 Mar 2008 12:14:55 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id CEA6D8FC23 for ; Fri, 14 Mar 2008 12:14:54 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 73461 invoked by uid 98); 14 Mar 2008 12:14:53 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.042169 secs); 14 Mar 2008 12:14:53 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.042169 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 14 Mar 2008 12:14:53 -0000 Message-ID: <47DA6C30.400@zirakzigil.org> Date: Fri, 14 Mar 2008 13:14:40 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: pyunyh@gmail.com References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> <47DA4DCD.6050304@zirakzigil.org> <20080314101555.GF22788@cdnetworks.co.kr> <47DA682E.9010504@zirakzigil.org> In-Reply-To: <47DA682E.9010504@zirakzigil.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Andrew Thompson Subject: Re: VLAN trunking and fragmentation 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, 14 Mar 2008 12:14:55 -0000 Giulio Ferro wrote: > That's it! > Now seems to work properly, the problem then is with hardware tagging. > > My question now is: can I use vlans without htag in a complex system with > heavy traffic without a significant performance loss? If not, how much > will it > take to fix the issue with the driver? > There's seems to be another problem now. If I send flood pings to the other host with big packets (say 2000 bytes) it works, but one packet out of 4 or 5 takes a huge time to round-trip (about 1000ms), whereas the rest of the packets have a reasonable 0.2 ms average... I fear this may lead to unacceptable performance for real-time protocols (ie voip) in a production environment. Do you think the problem is localized in the "re" driver? If so I could just change the network interface and be done with that. (In production I can use bge cards). Thanks again. From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 12:27:16 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECA18106566B for ; Fri, 14 Mar 2008 12:27:16 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.188]) by mx1.freebsd.org (Postfix) with ESMTP id BE6EE8FC28 for ; Fri, 14 Mar 2008 12:27:16 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id g13so2609243rvb.43 for ; Fri, 14 Mar 2008 05:27:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=laXEyYDdZKqHGohMDCW0No3iW8ktN7cF5/pU96ZjIU8=; b=sKmlu+ZWJq5vSwqlIcRc30GxpcJWqTaLe077r/phVCcziZz/VExNhTSx52yw0JArSYwZogPdnAbAF84DYRv1eXxbVqbk8peJbdmNZ9MNwLsMQugWTlYvcsQpn9pp1uxTkdTQjXIUtHnzuy+7kAU0klCz0P/bwbNN6m5xI5FKgac= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=k9G7E1JXT0P4kB46+Ti9JGCGcARJxZedFq3qi9SuIDNonFkAo8S6tcxEMIlrXQVklfPiT7r5NOePeTA3MtCq2c00/TA+cR4f0WfFyTBhxr5yDsw3jD03mvMbZdR2tSedOIM8fJNhLGENL3x3tsRne9apCghjdNjTlvHx7Qj55/0= Received: by 10.141.87.13 with SMTP id p13mr6446844rvl.55.1205497636020; Fri, 14 Mar 2008 05:27:16 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 7sm21124612wrl.12.2008.03.14.05.27.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Mar 2008 05:27:14 -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 m2ECR9lt024898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 21:27:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2ECR8S2024897; Fri, 14 Mar 2008 21:27:08 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 14 Mar 2008 21:27:08 +0900 From: Pyun YongHyeon To: Giulio Ferro Message-ID: <20080314122708.GG22788@cdnetworks.co.kr> References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> <47DA4DCD.6050304@zirakzigil.org> <20080314101555.GF22788@cdnetworks.co.kr> <47DA682E.9010504@zirakzigil.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47DA682E.9010504@zirakzigil.org> User-Agent: Mutt/1.4.2.1i Cc: Andrew Thompson , freebsd-net@freebsd.org Subject: Re: VLAN trunking and fragmentation 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: Fri, 14 Mar 2008 12:27:17 -0000 On Fri, Mar 14, 2008 at 12:57:34PM +0100, Giulio Ferro wrote: > Pyun YongHyeon wrote: > > > No packet reached the other PC. > > > >Ok, then try disabling hardware VLAN tagging. > >(#ifconfig re0 -vlanhwtag) > > > > > That's it! > Now seems to work properly, the problem then is with hardware tagging. > > My question now is: can I use vlans without htag in a complex system with > heavy traffic without a significant performance loss? If not, how much Using available hardware assitance is almost always better than software approach. Disabling VLAN hardware assistance also disables checksum offload on VLAN interface so it may hurt VLAN performance a lot. > will it > take to fix the issue with the driver? > This hardware really make me crazy. There had been many attempts to fix checksum offload related issues. But it seems that several users still suffer from bad checksum or VLAN issues. So I guess the root cause of hardware bug was not yet known. This means that previous patch to work around hardware bug is not complete. Hmm, I'm not sure but it could be related with padding. What makes me wonder is why the first packet of fragmented packet does not show up on destination host. I guess the second packet of fragmented packet may be composed of single mbuf. From these information I will experiment possible combination of work around in next week. I'll let you know when I have a code. > Thanks for your answer. > -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 12:28:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E5A5106567C for ; Fri, 14 Mar 2008 12:28:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 72BB38FC1A for ; Fri, 14 Mar 2008 12:28:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so3892401wfa.7 for ; Fri, 14 Mar 2008 05:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=8GlKhq+kLMFM2I5ZPqiH9s2a8Wx89O23/RzZmthLvqc=; b=G7R0JuUuBJHDj9UAD5P6q9vBg3AhDw1Ebf/mjKk/S/YojhSzO7aC7eei9Z/DYTlbRu+uG8Wi2dIZLY1Ad7ZUsrAjPthWoDb2RIATl5cQRtB418vVDPKdlzC5cvy9zdRhchsGy89/uGYCNGXCI/Lnr2v93Gkt8ieQTXYTXh0PvqM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=rSyM+4sT1KqEZhXsCqZydIg8U7Ghrki7lrIwgXiuwh03Sh8gPmjH0lrm+ha+LVmKdpPZNyDZ6CPVGfmgwnp+WGuKHhKcc5YX2w4tIT40Nj2RMaF6WBUcTZawOTmIveJS4fAH03TxCSXL363IaNOfVKGohPo909Q7kaR+KdV6HKY= Received: by 10.143.37.20 with SMTP id p20mr4798337wfj.236.1205497701674; Fri, 14 Mar 2008 05:28:21 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 38sm23256670wrl.1.2008.03.14.05.28.18 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Mar 2008 05:28:20 -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 m2ECSFad024909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 21:28:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2ECSEB5024908; Fri, 14 Mar 2008 21:28:14 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 14 Mar 2008 21:28:14 +0900 From: Pyun YongHyeon To: Giulio Ferro Message-ID: <20080314122814.GH22788@cdnetworks.co.kr> References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> <47DA4DCD.6050304@zirakzigil.org> <20080314101555.GF22788@cdnetworks.co.kr> <47DA682E.9010504@zirakzigil.org> <47DA6C30.400@zirakzigil.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47DA6C30.400@zirakzigil.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Andrew Thompson Subject: Re: VLAN trunking and fragmentation 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: Fri, 14 Mar 2008 12:28:22 -0000 On Fri, Mar 14, 2008 at 01:14:40PM +0100, Giulio Ferro wrote: > Giulio Ferro wrote: > >That's it! > >Now seems to work properly, the problem then is with hardware tagging. > > > >My question now is: can I use vlans without htag in a complex system with > >heavy traffic without a significant performance loss? If not, how much > >will it > >take to fix the issue with the driver? > > > > > There's seems to be another problem now. > > If I send flood pings to the other host with big packets (say 2000 > bytes) it works, but one > packet out of 4 or 5 takes a huge time to round-trip (about 1000ms), > whereas the rest > of the packets have a reasonable 0.2 ms average... > > > I fear this may lead to unacceptable performance for real-time protocols > (ie voip) in a > production environment. > > Do you think the problem is localized in the "re" driver? If so I could Yes. > just change the > network interface and be done with that. (In production I can use bge > cards). > > > Thanks again. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 13:53:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24BCC106566B for ; Fri, 14 Mar 2008 13:53:11 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: from coruscant.far-far-away.com (coruscant.far-far-away.us [70.91.196.65]) by mx1.freebsd.org (Postfix) with SMTP id C2F6F8FC26 for ; Fri, 14 Mar 2008 13:53:10 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: (qmail 19968 invoked from network); 14 Mar 2008 09:47:02 -0400 Received: from unknown (HELO alderaan) (68.162.198.134) by coruscant.far-far-away.us with SMTP; 14 Mar 2008 09:47:02 -0400 Message-ID: From: "Yousif Hassan" To: "Benjamin Close" , "Sam Leffler" References: <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl><47D6FB5B.3020107@clearchain.com><1205366956.2082.13.camel@localhost> <47D88DC0.1010903@freebsd.org> <47D9A5E3.1020900@clearchain.com> In-Reply-To: <47D9A5E3.1020900@clearchain.com> Date: Fri, 14 Mar 2008 09:54:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545 Cc: freebsd-net@freebsd.org, Mel , Alphons Fonz van Werven , freebsd-mobile@freebsd.org Subject: Re: [Wireless] Can't connect to wlan 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, 14 Mar 2008 13:53:11 -0000 Benjamin Close wrote: > Sam Leffler wrote: >> Yousif Hassan wrote: >>> On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: >>> >>> The slightly wonky: >>> - As reported by someone else: >>> wpi0: timeout resetting Tx ring 1 >>> wpi0: timeout resetting Tx ring 3 >>> wpi0: timeout resetting Tx ring 4 >>> appear on startup and occasionally on kldload - however they don't >>> appear to adversely affect too much >> >> wpi doesn't yet support background scan so doing an explicit scan from >> the command line will disconnect you from any ap you care connected to. >> It shouldn't be hard to add bgscan--but that's easy for me to say :) >> > It's certainly on my todo list! Thanks for reminding me about the bgscan thing. I had read that somewhere before and completely forgotten! Ben, are the wpi0: timeout resetting Tx ring 1 wpi0: timeout resetting Tx ring 3 wpi0: timeout resetting Tx ring 4 (and other variants thereof) messages anything to be concerned about? It doesn't seem to affect stuff but it does show up on initial startup and every other scan I do. Thanks to everyone who worked on wpi for a most excellent driver. --Y From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 15:37:51 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBE91106566C for ; Fri, 14 Mar 2008 15:37:51 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynhome1sv1.zirakzigil.org (mail.zirakzigil.org [82.63.178.63]) by mx1.freebsd.org (Postfix) with SMTP id 1DD8F8FC62 for ; Fri, 14 Mar 2008 15:37:50 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: (qmail 75019 invoked by uid 98); 14 Mar 2008 15:37:48 -0000 Received: from 89.96.52.22 by aurynhome1sv1.zirakzigil.org (envelope-from , uid 89) with qmail-scanner-1.25 ( Clear:RC:0(89.96.52.22):. Processed in 0.044069 secs); 14 Mar 2008 15:37:48 -0000 X-Qmail-Scanner-Mail-From: auryn@zirakzigil.org via aurynhome1sv1.zirakzigil.org X-Qmail-Scanner: 1.25 (Clear:RC:0(89.96.52.22):. Processed in 0.044069 secs) Received: from unknown (HELO aurynmob2.giulioferro.it) (auryn@zirakzigil.org@89.96.52.22) by 0 with SMTP; 14 Mar 2008 15:37:48 -0000 Message-ID: <47DA9BC0.8030205@zirakzigil.org> Date: Fri, 14 Mar 2008 16:37:36 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: pyunyh@gmail.com, Sam Leffler , Andrew Thompson , freebsd-net@freebsd.org References: <47D7C34E.8060805@zirakzigil.org> <47D817D2.9010306@errno.com> <47D8499A.5070605@zirakzigil.org> <20080313033029.GF16972@cdnetworks.co.kr> <47D92F9D.4070701@zirakzigil.org> <20080314001704.GA22788@cdnetworks.co.kr> <47DA4DCD.6050304@zirakzigil.org> <20080314101555.GF22788@cdnetworks.co.kr> <47DA682E.9010504@zirakzigil.org> <20080314122708.GG22788@cdnetworks.co.kr> In-Reply-To: <20080314122708.GG22788@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: VLAN trunking and fragmentation 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, 14 Mar 2008 15:37:52 -0000 Pyun YongHyeon wrote: > This hardware really make me crazy. There had been many attempts to > fix checksum offload related issues. But it seems that several users > still suffer from bad checksum or VLAN issues. So I guess the root > cause of hardware bug was not yet known. This means that previous > patch to work around hardware bug is not complete. > > Hmm, I'm not sure but it could be related with padding. What makes > me wonder is why the first packet of fragmented packet does not > show up on destination host. I guess the second packet of fragmented > packet may be composed of single mbuf. From these information I > will experiment possible combination of work around in next week. > I'll let you know when I have a code. > > Great! Thanks for the good job. From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 23:24:56 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C983F1065670 for ; Fri, 14 Mar 2008 23:24:56 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: from hal.rescomp.berkeley.edu (hal.Rescomp.Berkeley.EDU [169.229.70.150]) by mx1.freebsd.org (Postfix) with ESMTP id B543C8FC18 for ; Fri, 14 Mar 2008 23:24:56 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: by hal.rescomp.berkeley.edu (Postfix, from userid 1225) id 7A0EB3C04CE; Fri, 14 Mar 2008 16:24:56 -0700 (PDT) Date: Fri, 14 Mar 2008 16:24:56 -0700 From: Christopher Cowart To: freebsd-net@freebsd.org Message-ID: <20080314232456.GQ91152@hal.rescomp.berkeley.edu> Mail-Followup-To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K9fy5ol1Oes4Q/ix" Content-Disposition: inline Organization: RSSP-IT, UC Berkeley User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Behavior of `ipfw table n list' in 7.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 23:24:56 -0000 --K9fy5ol1Oes4Q/ix Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I've been debugging some scripts for the better part of the hour, and finally figured out what's going on. On 6.2, `ipfw table 3 list' outputs: 169.229.127.61/32 100127061 But on 7.0, `ipfw table 4 list' outputs: 10.9.156.254/32 11.237.178.84 They're different tables with different values, but what's shocking is the change to dotted-quad representation on 7.0. I notice in ipfw(8) on 7.0, tablearg is now a valid value to fwd. The thing is, according to the 'LOOKUP TABLES' section of the man page, "Associated with each entry is a 32-bit unsigned value". It's very explicitly *not* an IP address, because tablearg can be used for all sorts of other things, like indexing pipes, specifying tag values, or in my case, holding netgraph cookies.=20 It's not a big deal -- I already had an ip_to_number function in my shell library, and now that I know what the issue is, I can deal with it. I wanted to bring it up, because printing something that's not an IP address in dotted-quad notation seems misleading and confusing. --=20 Chris Cowart Network Technical Lead Network & Infrastructure Services, RSSP-IT UC Berkeley --K9fy5ol1Oes4Q/ix Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iQIVAwUBR9sJSCPHEDszU3zYAQLdJg//X5h3t+asISUign3ds5seqHS6a7xPBB0f X/aGrFXM4LYt14Z4qMEvii+jBYHZIqWQHD9WNjr9zYamlyHvY1U6b/EUyD2rrbeo EGvWPl7ZlJJJp+4J/HVr/HwP/fRin+p7evzvKU727/UOk+plFWUCHvBHuyBgnzhD m4yjUWiwqmVf0De6Fxc7ERpu/oluFgnHc+H+/+sXw5+4ZvvGA0Q/Qyz6lfKyRwj0 ghBRsxnlH4LtnT+bFD62QDlZzYYm5KHz3A8J0pewAD2MdRtH+HSpeSymv6zsSbYf XZswVzhK6edoG5hjlPd36WaXufSqofgtLornclyNZ5Epzd8i+6hYXra9DsxzBPOQ 5qiDN/5585QSxuzsP1/Qk6jGCwrTZQHd93WfdJ+a/vr76EIOy3/rpVqIA8OKBnOt MY28kHgwIrDxA3vm2o8/xSy6CLGtM/UOwoHkDEUQfKix+zITcxMhulwP4HebZXiV sbNbMj5H6+zim2Wn0OzHHKxZt8f5NBxL3i8F2axK1uT8/9eiNnFX+h4aC8cGRVWh /yWta8RLdY4BZBA6VDKsq1MsX1sK5LJGzQoTH8Ajw9YD186HoAlFlIBvRcRJpmw3 TvZ+tJeU3I1OqtAFRLjCHFR7vKLMw31N0w2ja0fewQfBxb8Ti8EYwn9d9GhYdHy6 tFTP9iw/S4s= =mlKD -----END PGP SIGNATURE----- --K9fy5ol1Oes4Q/ix-- From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 23:58:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EAD5106566B; Fri, 14 Mar 2008 23:58:46 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (muon.bluestop.org [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 32AB78FC1D; Fri, 14 Mar 2008 23:58:46 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from [IPv6:2a01:348:10f:0:3831:da8:862a:9c9f] (unknown [IPv6:2a01:348:10f:0:3831:da8:862a:9c9f]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id 39BC33017C; Fri, 14 Mar 2008 23:58:44 +0000 (GMT) Message-ID: <47DB112D.4090705@cran.org.uk> Date: Fri, 14 Mar 2008 23:58:37 +0000 From: Bruce Cran User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: bug-followup@FreeBSD.org, mstowe@chicago.us.mensa.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: kern/121706: "rtfree: 0xc4383870 has 1 refs" emitted repeatedly 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, 14 Mar 2008 23:58:46 -0000 The same change was made in net/route.c rev 1.120.2.3. I don't know if all calls to rtfree(rt) should be converted to RTFREE_LOCKED(rt), but those remaining are in: net/route.c:367 net/route.c:399 netinet/if_ether.c:808 netinet/if_ether.c:813 netinet/if_ether.c:831 netinet/if_ether.c:834 netinet6/in6_gif.c:373 netinet6/in6_gif.c:376 netinet6/in6_ifattach.c:768 netinet6/nd6_nbr.c:219 -- Bruce From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 00:32:06 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 673CF106566B for ; Sat, 15 Mar 2008 00:32:06 +0000 (UTC) (envelope-from kailockwood@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id 337268FC1C for ; Sat, 15 Mar 2008 00:32:06 +0000 (UTC) (envelope-from kailockwood@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so4765105waf.3 for ; Fri, 14 Mar 2008 17:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=rGnYhNQPxImi+E6AcUdg2J97DySXltYNerKQagcbQRA=; b=CFeiGzCz//HD9KAle7aH3EvaV3NLtHJ6O5d+KUA990gdYOAWdcEk4pF0e9Ehsgfonb7SGftKKlXaL+Ap2A8bmsRl1QjMLbXKYjCCFfixGBwMH+0i+NMLKwvgI96jyklKBE5tYnc26+8eD9ci3p+ydrrx+L89QKglcHx5Hy3dY5U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=auhPIsLUmGNwR5DgNLswGGkm72sg2j8R3dj9FmwVABvVeDN1KYNV6UbEPe98wfNP01V+AaE+cs0+Hu0p6nKFG3imqNV4arQAvsCN3s1RurPPsne09Fw7seT4Z5MDzchm0y/dALaVZjn3gLyxKp0XaoRr1w9Rxovkhi372QHUXdE= Received: by 10.114.135.1 with SMTP id i1mr13093268wad.88.1205539410677; Fri, 14 Mar 2008 17:03:30 -0700 (PDT) Received: from onan.local ( [71.217.152.177]) by mx.google.com with ESMTPS id a8sm1093272poa.2.2008.03.14.17.03.29 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Mar 2008 17:03:29 -0700 (PDT) From: Kai Lockwood To: freebsd-net@freebsd.org Date: Fri, 14 Mar 2008 18:03:12 -0600 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803141803.12974.kailockwood@gmail.com> Subject: SLIP slipping away 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, 15 Mar 2008 00:32:06 -0000 Hello, I am having difficulty setting up a SLIP connection between a Debian 4.0 box and FreeBSD 7.0-STABLE. I have enabled the sl driver in the kernel. I have tried using slattach on /dev/cuad0 (usually "slattach -s 115200 /dev/cuad0) only to watch slattach immediately die with no output as to why. If I give the -l option it creates the sl0 interface but will not accept traffic. Reading through the years old FAQs states that a 'netstat -i' with the sl driver installed should show sl interfaces but netstat does not list any sl interfaces. I have tried to load the kernel module if_sl but I have had no success. Has anyone on this list had any success with using SLIP? Thanks, Kai Lockwood From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 00:48:57 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18A63106566B for ; Sat, 15 Mar 2008 00:48:57 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outQ.internet-mail-service.net [216.240.47.240]) by mx1.freebsd.org (Postfix) with ESMTP id F36758FC15 for ; Sat, 15 Mar 2008 00:48:56 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Fri, 14 Mar 2008 17:48:57 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 6209D2D6A10; Fri, 14 Mar 2008 17:47:56 -0700 (PDT) Message-ID: <47DB1CBB.7010104@elischer.org> Date: Fri, 14 Mar 2008 17:47:55 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Kai Lockwood References: <200803141803.12974.kailockwood@gmail.com> In-Reply-To: <200803141803.12974.kailockwood@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: SLIP slipping away 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, 15 Mar 2008 00:48:57 -0000 Kai Lockwood wrote: > Hello, > > I am having difficulty setting up a SLIP connection between a Debian 4.0 box > and FreeBSD 7.0-STABLE. I have enabled the sl driver in the kernel. I have > tried using slattach on /dev/cuad0 (usually "slattach -s 115200 /dev/cuad0) > only to watch slattach immediately die with no output as to why. If I give > the -l option it creates the sl0 interface but will not accept traffic. > Reading through the years old FAQs states that a 'netstat -i' with the sl > driver installed should show sl interfaces but netstat does not list any sl > interfaces. I have tried to load the kernel module if_sl but I have had no > success. > > Has anyone on this list had any success with using SLIP? I somehow doubt anyone has used slip for years and years.. it COULD have been broken years ago. :-/ > > Thanks, > > Kai Lockwood > _______________________________________________ > 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 Mar 15 00:51:28 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0C50106566B for ; Sat, 15 Mar 2008 00:51:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outX.internet-mail-service.net (outX.internet-mail-service.net [216.240.47.247]) by mx1.freebsd.org (Postfix) with ESMTP id 96C208FC20 for ; Sat, 15 Mar 2008 00:51:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Fri, 14 Mar 2008 17:51:28 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 89A7A2D6EA4 for ; Fri, 14 Mar 2008 17:46:35 -0700 (PDT) Message-ID: <47DB1C6A.8050908@elischer.org> Date: Fri, 14 Mar 2008 17:46:34 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <20080314232456.GQ91152@hal.rescomp.berkeley.edu> In-Reply-To: <20080314232456.GQ91152@hal.rescomp.berkeley.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Behavior of `ipfw table n list' in 7.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2008 00:51:28 -0000 Christopher Cowart wrote: > Hello, > > I've been debugging some scripts for the better part of the hour, and > finally figured out what's going on. > > On 6.2, `ipfw table 3 list' outputs: > 169.229.127.61/32 100127061 > > But on 7.0, `ipfw table 4 list' outputs: > 10.9.156.254/32 11.237.178.84 > > They're different tables with different values, but what's shocking is > the change to dotted-quad representation on 7.0. > > I notice in ipfw(8) on 7.0, tablearg is now a valid value to fwd. The > thing is, according to the 'LOOKUP TABLES' section of the man page, > "Associated with each entry is a 32-bit unsigned value". It's very > explicitly *not* an IP address, because tablearg can be used for all > sorts of other things, like indexing pipes, specifying tag values, or in > my case, holding netgraph cookies. > > It's not a big deal -- I already had an ip_to_number function in my > shell library, and now that I know what the issue is, I can deal with > it. > > I wanted to bring it up, because printing something that's not an IP > address in dotted-quad notation seems misleading and confusing. > I think the dotted quad part is mentioned somewhere, but anyhow a patch was put in to add a specific option to ipfw(8) to request the quad notation If you get a new version of ipfw(8) it should have the fix.. Or pull the fix from the freebsd source cvs web page.. pull and apply the diff for revision 1.114 from the following page http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/ipfw/ipfw2.c and apply it and then reinstall it. that reminds me I need to merge this back to RELENG_7 From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 08:18:53 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC69B106566C; Sat, 15 Mar 2008 08:18:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A603B8FC22; Sat, 15 Mar 2008 08:18:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2F8IrrR009328; Sat, 15 Mar 2008 08:18:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2F8IrLB009324; Sat, 15 Mar 2008 08:18:53 GMT (envelope-from linimon) Date: Sat, 15 Mar 2008 08:18:53 GMT Message-Id: <200803150818.m2F8IrLB009324@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121706: [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emitted repeatedly 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, 15 Mar 2008 08:18:54 -0000 Old Synopsis: "rtfree: 0xc4383870 has 1 refs" emitted repeatedly New Synopsis: [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emitted repeatedly Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Mar 15 08:18:04 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=121706 From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 08:22:55 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6EC7106564A; Sat, 15 Mar 2008 08:22:55 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 805668FC20; Sat, 15 Mar 2008 08:22:55 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2F8MtlO009672; Sat, 15 Mar 2008 08:22:55 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2F8Mtpm009668; Sat, 15 Mar 2008 08:22:55 GMT (envelope-from linimon) Date: Sat, 15 Mar 2008 08:22:55 GMT Message-Id: <200803150822.m2F8Mtpm009668@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/121720: [wpi] wpi doesnt work if kernel has options SCHED_ULE 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, 15 Mar 2008 08:22:55 -0000 Synopsis: [wpi] wpi doesnt work if kernel has options SCHED_ULE Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Mar 15 08:22:29 UTC 2008 Responsible-Changed-Why: This sounds like an error in the individual driver to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=121720 From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 13:58:50 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5ECD1065675 for ; Sat, 15 Mar 2008 13:58:50 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id EC4D68FC24 for ; Sat, 15 Mar 2008 13:58:49 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m2FDvOUa030369; Sat, 15 Mar 2008 20:57:24 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m2FDvNco030368; Sat, 15 Mar 2008 20:57:23 +0700 (KRAT) (envelope-from eugen) Date: Sat, 15 Mar 2008 20:57:23 +0700 From: Eugene Grosbein To: Julian Elischer Message-ID: <20080315135723.GA29447@svzserv.kemerovo.su> References: <200803141803.12974.kailockwood@gmail.com> <47DB1CBB.7010104@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47DB1CBB.7010104@elischer.org> User-Agent: Mutt/1.4.2.3i Cc: Kai Lockwood , freebsd-net@freebsd.org Subject: Re: SLIP slipping away 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, 15 Mar 2008 13:58:51 -0000 On Fri, Mar 14, 2008 at 05:47:55PM -0700, Julian Elischer wrote: > >Has anyone on this list had any success with using SLIP? > I somehow doubt anyone has used slip for years and years.. > it COULD have been broken years ago. :-/ It did work for 4.11-STABLE, though. Verified :-) Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 15:07:27 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC067106564A for ; Sat, 15 Mar 2008 15:07:27 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outJ.internet-mail-service.net (outJ.internet-mail-service.net [216.240.47.233]) by mx1.freebsd.org (Postfix) with ESMTP id 9E28E8FC1A for ; Sat, 15 Mar 2008 15:07:27 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Sat, 15 Mar 2008 08:07:57 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 555D22D6021; Sat, 15 Mar 2008 08:07:25 -0700 (PDT) Message-ID: <47DBE62A.9070908@elischer.org> Date: Sat, 15 Mar 2008 08:07:22 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Eugene Grosbein References: <200803141803.12974.kailockwood@gmail.com> <47DB1CBB.7010104@elischer.org> <20080315135723.GA29447@svzserv.kemerovo.su> In-Reply-To: <20080315135723.GA29447@svzserv.kemerovo.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kai Lockwood , freebsd-net@freebsd.org Subject: Re: SLIP slipping away 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, 15 Mar 2008 15:07:28 -0000 Eugene Grosbein wrote: > On Fri, Mar 14, 2008 at 05:47:55PM -0700, Julian Elischer wrote: > >>> Has anyone on this list had any success with using SLIP? >> I somehow doubt anyone has used slip for years and years.. >> it COULD have been broken years ago. :-/ > > It did work for 4.11-STABLE, though. Verified :-) > > Eugene Grosbein That IS years ago :-) From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 16:40:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 543F8106564A for ; Sat, 15 Mar 2008 16:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 51D898FC12 for ; Sat, 15 Mar 2008 16:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2FGe2bT051774 for ; Sat, 15 Mar 2008 16:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2FGe25g051773; Sat, 15 Mar 2008 16:40:02 GMT (envelope-from gnats) Date: Sat, 15 Mar 2008 16:40:02 GMT Message-Id: <200803151640.m2FGe25g051773@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Harald Hanche-Olsen Cc: Subject: Re: kern/116747: [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile 1400 wireless card X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harald Hanche-Olsen List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2008 16:40:03 -0000 The following reply was made to PR kern/116747; it has been noted by GNATS. From: Harald Hanche-Olsen To: bug-followup@FreeBSD.org, roar.pettersen@FreeBSD.org Cc: Subject: Re: kern/116747: [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile 1400 wireless card Date: Sat, 15 Mar 2008 17:07:10 +0100 (CET) (I wasn't sure whether to append to this pr or file my own: My problem seems related but is not identical. Anyway, here goes:) I have an old-ish laptop with the Dell TrueMobile 1180 Internal 802.11b Mini PCI Card. I get a kernel panic not after kld_load bcmwl5_sys.ko, but only after trying to run ifconfig on the interface instead: System: FreeBSD odin 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [The system is freshly installed, and bcmwl5_sys.ko is freshly generated on the new system.] First, when running "kldload bcmwl5_sys.ko" I get these messages on the console: ndis0: mem 0xffc000-0xf8ffdfff irq 9 at device 3.0 on pci2 ndis0: [ITHREAD] ndis0: NDIS API version: 5.0 ndis0: NDIS ERROR: c000138d (unknown error) ndis0: NDIS ERROR: c000138d (unknown error) ndis0: using obsoleted if_watchdog interface ndis0: Ethernet address: 00:90:4b:b0:07:5b Next, when I run "ifconfig ndis0 odin ssid foonet mode 11b" I get ndis0: NDIS ERROR: c000138d (unknown error) ndis0: NDIS ERROR: c000138d (unknown error) [IIRC, I used to get these under 6.2 as well, so I assume they're harmless] and then the kernel panic. Output from kgdb below. # kgdb /boot/kernel/kernel /var/crash/vmcore.1 [...] Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0a46e7c stack pointer = 0x28:0xf0890b04 frame pointer = 0x28:0xf0890b3c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 848 (ndis0 taskq) trap number = 12 panic: page fault cpuid = 0 Uptime: 4m58s Physical memory: 755 MB Dumping 272 MB: 257 241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:195 #1 0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0754719 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a4905c in trap_fatal (frame=0xf0890ac4, eva=0) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a492e0 in trap_pfault (frame=0xf0890ac4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a49c8c in trap (frame=0xf0890ac4) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0a46e7c in memcpy () at /usr/src/sys/i386/i386/support.s:692 Previous frame inner to this frame (corrupt stack?) (kgdb) # From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 17:04:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25470106567C for ; Sat, 15 Mar 2008 17:04:22 +0000 (UTC) (envelope-from kailockwood@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id E2CB48FC25 for ; Sat, 15 Mar 2008 17:04:21 +0000 (UTC) (envelope-from kailockwood@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so1401027anc.13 for ; Sat, 15 Mar 2008 10:04:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=9IE2ZHnW2CfFPkPybWyAZqhxe4YaWsKUBX/9myRGMFc=; b=dvOTmtGzpL+guC25hk6mIQHbTxFhICYiFiD8J367IHVUwJUlXf5ZXY6+A5y1fpPnlbRY584cT5SnWyk4WZAmsYg4+P/ApqPrgKuoxX0TqRLV3R3+nbQ+rgjq8kZUoX5mdebp13oyTtlC3sGLbOJF/4Pf5TZY2N138EhQBYLr7GI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=UW9E03cIWGwDVomfE1d3900A66nXRh84clyI9vWA1r2doPlGdAzMCckEtlmev1rLl0DR+2S7ct77o3asgZFnE6bbWWVosUDjZH6gaBngrW4U6/P+msosWDXk5XtMVUoCVww4Gu/dwHqVqbe4DCBAzaBT12GReDQN8XG1s2nyoQQ= Received: by 10.100.57.6 with SMTP id f6mr26737363ana.11.1205600661203; Sat, 15 Mar 2008 10:04:21 -0700 (PDT) Received: by 10.100.208.13 with HTTP; Sat, 15 Mar 2008 10:04:21 -0700 (PDT) Message-ID: Date: Sat, 15 Mar 2008 11:04:21 -0600 From: "Kai Lockwood" To: "Julian Elischer" In-Reply-To: <47DBE62A.9070908@elischer.org> MIME-Version: 1.0 References: <200803141803.12974.kailockwood@gmail.com> <47DB1CBB.7010104@elischer.org> <20080315135723.GA29447@svzserv.kemerovo.su> <47DBE62A.9070908@elischer.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Eugene Grosbein Subject: Re: SLIP slipping away 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, 15 Mar 2008 17:04:22 -0000 Hmm, well it's not that important just frustrating. I suppose I could contact the code maintainer, if they are even alive ;-) Thanks. On Sat, Mar 15, 2008 at 9:07 AM, Julian Elischer wrote: > Eugene Grosbein wrote: > > On Fri, Mar 14, 2008 at 05:47:55PM -0700, Julian Elischer wrote: > > > >>> Has anyone on this list had any success with using SLIP? > >> I somehow doubt anyone has used slip for years and years.. > >> it COULD have been broken years ago. :-/ > > > > It did work for 4.11-STABLE, though. Verified :-) > > > > Eugene Grosbein > > That IS years ago :-) > > From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 17:43:08 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 594AE1065673 for ; Sat, 15 Mar 2008 17:43:08 +0000 (UTC) (envelope-from sinister@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id 23AD98FC15 for ; Sat, 15 Mar 2008 17:43:02 +0000 (UTC) (envelope-from sinister@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so6530616pyb.10 for ; Sat, 15 Mar 2008 10:43:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; bh=JbUReyWmluCJ85z4lF/Pueac4YvtLWHAN6hVmbgGz/0=; b=W1ppKnVc35OUGyB/26UYcGjztPK1C4eCG8GXHSXqhzMdEhzah6cfGJB0QybUV/MUrV7EsnMaxqI7+ddUd31tSNHhg7G2iiQ/btqnMI1/5BfuNc5cyzTKZc9KSqt6FoUbGaD9zXvNVWW5jvJznXvt6SE+euGLzKS/1Vpw+PVX0jo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=UPO09fzcQYDUAxoKjDCAq/YdxrH4OYBfy2GjzFmL/ZERpZxcbpeoe0c+BDnwLa8BJcCivfN0Yn2RxMzUKcjMgTvuPS6VMzQgWqctnPcYe2DJOuIFM1hztyMMoFxNOdZwq2Gj3Bc2TleIG/+quIHYEN8t4/uIHB8bQCslJ8Z+XEE= Received: by 10.35.42.18 with SMTP id u18mr20906837pyj.49.1205601431213; Sat, 15 Mar 2008 10:17:11 -0700 (PDT) Received: from dts ( [216.8.139.47]) by mx.google.com with ESMTPS id n44sm44169812pyh.26.2008.03.15.10.17.07 (version=SSLv3 cipher=RC4-MD5); Sat, 15 Mar 2008 10:17:08 -0700 (PDT) Message-ID: <004701c886c0$6c866910$0200a8c0@dts> From: "Sin" To: "Kai Lockwood" , References: <200803141803.12974.kailockwood@gmail.com> Date: Sat, 15 Mar 2008 13:17:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Cc: Subject: Re: SLIP slipping away 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, 15 Mar 2008 17:43:08 -0000 I wasn't going to ask before, but I guess curiosity got the best of me. I've been working for an ISP for the past 8 years, so PPP and SLIP talk comes up alot. I don't usually post, just read, however I am curious about what kind of application could possibly be using slip as opposed to ppp now-a-days ?? > Hello, > > I am having difficulty setting up a SLIP connection between a Debian 4.0 > box > and FreeBSD 7.0-STABLE. I have enabled the sl driver in the kernel. I have > tried using slattach on /dev/cuad0 (usually "slattach -s 115200 > /dev/cuad0) > only to watch slattach immediately die with no output as to why. If I give > the -l option it creates the sl0 interface but will not accept traffic. > Reading through the years old FAQs states that a 'netstat -i' with the sl > driver installed should show sl interfaces but netstat does not list any > sl > interfaces. I have tried to load the kernel module if_sl but I have had no > success. > > Has anyone on this list had any success with using SLIP? > > Thanks, > > Kai Lockwood From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 17:47:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2014B106564A for ; Sat, 15 Mar 2008 17:47:05 +0000 (UTC) (envelope-from kailockwood@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id E05E38FC1D for ; Sat, 15 Mar 2008 17:47:04 +0000 (UTC) (envelope-from kailockwood@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so1406537anc.13 for ; Sat, 15 Mar 2008 10:47:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=mSPx8fo2pQFeU/BxhSx1AYFkQc/pcCU9bAsm5xJo9b4=; b=Kht1Q+DhAWWAYawvc/knmFrrG5uA5aJdMmhPkCoceEOcr9nHInVlu8x4vylC38QjEK0287ojuOhtnL6SkDUvOaBtVRX7X3igFqd77DD9ODVCfZcdjrLtvdfIzIQUHSEkGpD2AsGIfMFJOCl+yXSPh7E8Kobi9KOcQ8FlvOvRLcY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=EJyVI/vN7no58dCDYQPaAlgSvtSX+23iw2GFx/WInD2nmx0omKIeZTf7rCCcH+ir1donmqXpj317N44RmAJKlxHHa2YstbkctJalT5MlNkLoXeDCgXRRfgwWi6wVGNOjiQ6PVvzKBQOHqVX7V5t+itQ2QVYuIKRfRgeykyzfr4U= Received: by 10.100.253.12 with SMTP id a12mr26659465ani.92.1205603224011; Sat, 15 Mar 2008 10:47:04 -0700 (PDT) Received: by 10.100.208.13 with HTTP; Sat, 15 Mar 2008 10:47:03 -0700 (PDT) Message-ID: Date: Sat, 15 Mar 2008 11:47:03 -0600 From: "Kai Lockwood" To: Sin In-Reply-To: <004701c886c0$6c866910$0200a8c0@dts> MIME-Version: 1.0 References: <200803141803.12974.kailockwood@gmail.com> <004701c886c0$6c866910$0200a8c0@dts> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: SLIP slipping away 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, 15 Mar 2008 17:47:05 -0000 I was just trying to setup a really simple network with a null modem cable. I looked into ppp but the documentation I read didn't help and I'm still not smart enough to figure out how to do it yet. On Sat, Mar 15, 2008 at 11:17 AM, Sin wrote: > > I wasn't going to ask before, but I guess curiosity got the best of me. > I've been working for an ISP for the past 8 years, so PPP and SLIP talk > comes up alot. I don't usually post, just read, however I am curious about > what kind of application could possibly be using slip as opposed to ppp > now-a-days ?? > > > > Hello, > > > > I am having difficulty setting up a SLIP connection between a Debian 4.0 > > box > > and FreeBSD 7.0-STABLE. I have enabled the sl driver in the kernel. I > have > > tried using slattach on /dev/cuad0 (usually "slattach -s 115200 > > /dev/cuad0) > > only to watch slattach immediately die with no output as to why. If I > give > > the -l option it creates the sl0 interface but will not accept traffic. > > Reading through the years old FAQs states that a 'netstat -i' with the > sl > > driver installed should show sl interfaces but netstat does not list any > > sl > > interfaces. I have tried to load the kernel module if_sl but I have had > no > > success. > > > > Has anyone on this list had any success with using SLIP? > > > > Thanks, > > > > Kai Lockwood > > From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 18:59:24 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E3AB1065671 for ; Sat, 15 Mar 2008 18:59:24 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from tomts30-srv.bellnexxia.net (tomts30.bellnexxia.net [209.226.175.104]) by mx1.freebsd.org (Postfix) with ESMTP id 00BC68FC15 for ; Sat, 15 Mar 2008 18:59:23 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from toip6.srvr.bell.ca ([209.226.175.125]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20080315182446.RCOP1666.tomts20-srv.bellnexxia.net@toip6.srvr.bell.ca> for ; Sat, 15 Mar 2008 14:24:46 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtAEALmx20dBX3V3/2dsb2JhbACBWqY1 Received: from bas2-toronto63-1096775031.dsl.bell.ca (HELO mg-i1200.home.wezel.com) ([65.95.117.119]) by toip6.srvr.bell.ca with ESMTP; 15 Mar 2008 14:21:48 -0400 Message-ID: <47DC146C.8000005@wezel.com> Date: Sat, 15 Mar 2008 14:24:44 -0400 From: Bruce Walker User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Sin References: <200803141803.12974.kailockwood@gmail.com> <004701c886c0$6c866910$0200a8c0@dts> In-Reply-To: <004701c886c0$6c866910$0200a8c0@dts> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: SLIP slipping away 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, 15 Mar 2008 18:59:24 -0000 Sin wrote: > > I wasn't going to ask before, but I guess curiosity got the best of > me. I've been working for an ISP for the past 8 years, so PPP and SLIP > talk comes up alot. I don't usually post, just read, however I am > curious about what kind of application could possibly be using slip as > opposed to ppp now-a-days ?? One legitimate use-case is talking to single-chip embedded CPUs, eg an Atmel AVR or Mega, or a PIC controller. Very limited code space means that the networking implementation may be limited to just UDP/IP, and PPP is way too big, but SLIP is trivially doable. -bmw From owner-freebsd-net@FreeBSD.ORG Sat Mar 15 23:13:47 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23FFF106566C for ; Sat, 15 Mar 2008 23:13:47 +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 11BBF8FC13 for ; Sat, 15 Mar 2008 23:13:47 +0000 (UTC) (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 EA59146B54; Sat, 15 Mar 2008 19:13:45 -0400 (EDT) Date: Sat, 15 Mar 2008 23:13:45 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kai Lockwood In-Reply-To: <200803141803.12974.kailockwood@gmail.com> Message-ID: <20080315231137.E80785@fledge.watson.org> References: <200803141803.12974.kailockwood@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: SLIP slipping away 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, 15 Mar 2008 23:13:47 -0000 On Fri, 14 Mar 2008, Kai Lockwood wrote: > I am having difficulty setting up a SLIP connection between a Debian 4.0 box > and FreeBSD 7.0-STABLE. I have enabled the sl driver in the kernel. I have > tried using slattach on /dev/cuad0 (usually "slattach -s 115200 /dev/cuad0) > only to watch slattach immediately die with no output as to why. If I give > the -l option it creates the sl0 interface but will not accept traffic. > Reading through the years old FAQs states that a 'netstat -i' with the sl > driver installed should show sl interfaces but netstat does not list any sl > interfaces. I have tried to load the kernel module if_sl but I have had no > success. > > Has anyone on this list had any success with using SLIP? A few years ago, I tried to find someone to test SLIP locking patches without much luck. I know of no specific reason why it shouldn't work other than age and lack of testing. If we want to continue to support SLIP, my suggestion would be that we move the implementation to userspace with if_tun, avoiding the complexities and inter-dependencies of hooking SLIP into the tty line discipline code in the kernel. If something has broken, it might well relate to that complexity. Do you know of anyone using SLIP in production who would be willing to do the legwork on testing, etc, or is this a casual "I wonder if SLIP still works" sort of thing? I don't actually know of any sites still using it, and I've not seen a report of successful or failed use in years... Robert N M Watson Computer Laboratory University of Cambridge