From owner-freebsd-current@FreeBSD.ORG Wed Aug 19 18:08:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAA1D106568D for ; Wed, 19 Aug 2009 18:08:16 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 7030B8FC51 for ; Wed, 19 Aug 2009 18:08:16 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n7JI6VsP007959; Wed, 19 Aug 2009 11:08:14 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 19 Aug 2009 11:05:17 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: network problems Thread-Index: Acog9Awam8jkpd1iRUa3ms1hMeFmlQAA49bO References: <18104823-CB3F-42DA-9DE8-E6692D81E96B@h3q.com> <35FF00562E814F08BE71B6407FB6C1BF@adnote989> From: "Li, Qing" To: "Denis Ahrens" , Cc: Luiz Otavio O Souza Subject: RE: network problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 18:08:16 -0000 >> >> Qing, >> >> yes, disabling the flowtable (sysctl net.inet.flowtable.enable=3D0) =20 >> fix the problem (no more IPv4 is not on the network). But here, =20 >> everything is working fine, even with that annoying message (no =20 >> crashes). > > My network is also working fine, but it crashes when I ping the =20 > endpoint of the tunnel interface. > When you say your network is working fine, do you actually mean traffic flows across the tunnel ? > > When I turn flowtable off it does not crash but I get no ping reply =20 > back. > Okay, so there is probably another bug lurking somewhere. I am=20 traveling right now and will dig into it once I get back at the end of this week, if someone else hasn't already fixed it by then. -- Qing