Date: Wed, 19 Aug 2009 11:05:17 -0700 From: "Li, Qing" <qing.li@bluecoat.com> To: "Denis Ahrens" <denis@h3q.com>, <freebsd-current@freebsd.org> Cc: Luiz Otavio O Souza <lists.br@gmail.com> Subject: RE: network problems Message-ID: <B583FBF374231F4A89607B4D08578A4304673682@bcs-mail03.internal.cacheflow.com> References: <18104823-CB3F-42DA-9DE8-E6692D81E96B@h3q.com> <B583FBF374231F4A89607B4D08578A430467367F@bcs-mail03.internal.cacheflow.com> <35FF00562E814F08BE71B6407FB6C1BF@adnote989> <C4F11EE5-98C1-4093-B667-6C09E395621E@h3q.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A4304673682>