From owner-freebsd-net@FreeBSD.ORG Wed Sep 22 18:17:20 2010 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 ED0BE1065670; Wed, 22 Sep 2010 18:17:20 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 818518FC08; Wed, 22 Sep 2010 18:17:20 +0000 (UTC) Received: by gwb15 with SMTP id 15so329673gwb.13 for ; Wed, 22 Sep 2010 11:17:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=SoUI2wh+6uQXHNRJSVWT0JDseodO8JlaCaOR2NB+udw=; b=qv9mYrTJ2LpOWxX4E2v+NoB0TguJezQUYFjTj8Q+8n4gKGEb+38WvsCUM5xVdVHtYS dIqoteqjNiQxNCquVtxdGlMsmxnerygOvygv7E959ApM2O+umgMooHYXkGGlHM9hLuWK avlxhTLoBciHb/KO8laiAmezGvTsO033gwruw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=KaSHzwPAlQp+AMbeAXykbQ+Gu50WVy6WeqR5adkFwhW5jK03E+pMx7XO5D7LxMZOq+ yLK4uhGUWmizuCyrUnwoaGEE2QctRCW/A+EDtVKRva1/uq8qjRMWySKVn0gi1U67lch+ OWJGsHta9fYdSJpeTkkLQKm5gJ2Od/TDDpEAc= Received: by 10.150.74.11 with SMTP id w11mr1589242yba.164.1285179439687; Wed, 22 Sep 2010 11:17:19 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id i6sm10720362iba.2.2010.09.22.11.17.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 22 Sep 2010 11:17:17 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 22 Sep 2010 11:16:23 -0700 From: Pyun YongHyeon Date: Wed, 22 Sep 2010 11:16:23 -0700 To: Josh Endries Message-ID: <20100922181623.GG10299@michelle.cdnetworks.com> References: <200804301320.m3UDK3cK034832@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200804301320.m3UDK3cK034832@freefall.freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, bug-followup@FreeBSD.org Subject: Re: kern/123172: [bce] Watchdog timeout problems with if_bce 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: Wed, 22 Sep 2010 18:17:21 -0000 On Wed, Apr 30, 2008 at 01:20:03PM +0000, Josh Endries wrote: > The following reply was made to PR kern/123172; it has been noted by GNATS. > > From: Josh Endries > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: kern/123172: [bce] Watchdog timeout problems with if_bce > Date: Wed, 30 Apr 2008 08:58:23 -0400 > > It's been working well for a while, so I might have fixed whatever was > causing the problem to manifest. I converted my lo0 jails to use real > IPs, and removed my pf config that was routing things around, so I > suspect that had something to do with it. I can't change it back right > now, later this week/weekend I should be able to. > > I had jails on 127.0.0.x (a couple still are), namely the BIND jail, but > my switch was load balancing it so the machine was BINATing the 10.0.0 > address the switch was talking to with the local 127.0.0.3 address > (iirc). The switch was NATing the 10 address to a real IP. > > The problem was that I also have some real IPs on this box, so the > machine wanted to route packets out that interface, so I had to use > route-to/reply-to for the BIND jail to get things to go back out the way > they came in, instead of using the x.x.164/24 route or default route. It > did work in the configuration, but had the watchdog errors. I think this > might have something to do with the issue; I'll put things back and test > it some more when I have some time. > > I did see that other PR, but since this is a newer version of FreeBSD, > and I have no ACPI problems or problems booting (that I've noticed, at > least), I decided to submit. They certainly could be related (we're both > using amd64; unfortunately I can't change that to test i386). Here is > some more info... > > jls: > > JID IP Address Hostname Path > 5 x.x.164.7 smtp /jails/smtp/root > 4 127.0.0.5 mx /jails/mx/root > 3 x.x.164.4 ns /jails/ns/root > 2 127.0.0.4 pkg /jails/pkg/root > 1 127.0.0.2 mysql /jails/mysql/root > > /etc/pf.conf: > > nat on vlan2 from to any -> x.x.164.123 > binat on vlan8 from $jail_mysql_ip to any -> $jail_mysql_exip > > block log (user) all > pass in log (user) quick on vlan2 inet proto { tcp, udp } from any to > $jail_ns_ip port domain keep state > pass out log (user) quick on vlan2 inet proto { tcp, udp } from > $jail_ns_ip to any port domain keep state > pass quick log (user) on lo0 inet proto udp from to > port domain keep state > pass quick log (user) on lo0 inet proto tcp from to > $jail_mysql_ip port 3306 keep state > pass out log (user) quick on vlan8 inet proto tcp from $jail_mysql_exip > to 10.0.1.2 port 3306 keep state > pass in log (user) quick on vlan11 inet proto tcp from to > vlan11 port 55185 keep state > pass log (user) quick inet proto icmp all icmp-type $icmp_types keep state > pass out log (user) quick on vlan2 inet proto tcp from x.x.164.123 to > any keep state > > uname -a: > > FreeBSD hathor 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Tue Mar 24 13:36:33 > EDT 2009 root@hathor:/jails/src/usr/obj/jails/src/usr/src/sys/ULEMAC > amd64 > > kernel config: > > include GENERIC > ident ULEMAC > nooptions SCHED_4BSD > options SCHED_ULE > options MAC > > ifconfig: > > bce0: flags=8843 metric 0 mtu 1500 > > options=1bb > ether 00:1f:29:06:d9:e2 > media: Ethernet autoselect (100baseTX ) > status: active > lagg: laggdev lagg0 > bce1: flags=8843 metric 0 mtu 1500 > > options=1bb > ether 00:1f:29:06:d9:e2 > media: Ethernet autoselect (100baseTX ) > status: active > lagg: laggdev lagg0 > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > inet 127.0.0.2 netmask 0xffffffff > inet 127.0.0.4 netmask 0xffffffff > inet 127.0.0.5 netmask 0xffffffff > lagg0: flags=8843 metric 0 mtu 1500 > > options=1bb > ether 00:1f:29:06:d9:e2 > media: Ethernet autoselect > status: active > laggproto lacp > laggport: bce1 flags=1c > laggport: bce0 flags=1c > vlan2: flags=8843 metric 0 mtu 1500 > options=3 > ether 00:1f:29:06:d9:e2 > inet x.x.164.123 netmask 0xffffff00 broadcast x.x.164.255 > inet x.x.164.4 netmask 0xffffffff broadcast x.x.164.4 > inet x.x.164.7 netmask 0xffffffff broadcast x.x.164.7 > media: Ethernet autoselect > status: active > vlan: 2 parent interface: lagg0 > vlan8: flags=8843 metric 0 mtu 1500 > options=3 > ether 00:1f:29:06:d9:e2 > inet 10.0.1.6 netmask 0xfffffff8 broadcast 10.0.1.7 > media: Ethernet autoselect > status: active > vlan: 8 parent interface: lagg0 > vlan11: flags=8843 metric 0 mtu 1500 > options=3 > ether 00:1f:29:06:d9:e2 > inet 10.0.2.11 netmask 0xffffff00 broadcast 10.0.2.255 > media: Ethernet autoselect > status: active > vlan: 11 parent interface: lagg0 > vlan12: flags=8843 metric 0 mtu 1500 > options=3 > ether 00:1f:29:06:d9:e2 > inet 10.0.0.10 netmask 0xfffffff8 broadcast 10.0.0.15 > media: Ethernet autoselect > status: active > vlan: 12 parent interface: lagg0 > pflog0: flags=141 metric 0 mtu 33160 > > I'll post again after I change it back and try what you suggested. > Is this still issue on more recent FreeBSD release(8.1-RELEASE or 7.3-RELEASE)?