Date: Sat, 17 Jun 2000 18:34:01 +0200 From: Anders Nordby <anders@fix.no> To: Luigi Rizzo <luigi@info.iet.unipi.it> Cc: freebsd-net@FreeBSD.ORG Subject: Re: Dummynet instability Message-ID: <20000617183401.A16130@totem.fix.no> In-Reply-To: <200006171604.SAA02716@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Sat, Jun 17, 2000 at 06:04:27PM %2B0200 References: <20000617121648.A9857@totem.fix.no> <200006171604.SAA02716@info.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 17, 2000 at 06:04:27PM +0200, Luigi Rizzo wrote: > am looking at the cvs logs to understand what was going on, > but at first sight the code seems the same (functionally speaking) > that fixed the problem in november. > > anyways, this problem was related with route entries changing/going > away while the packet is stored in the dummynet (which does not > last long, usually a few seconds). So, what is your underlying network > structure, do you have multiple interfaces or routes that change etc ? It's a one NIC machine, only having a route for it's own subnet, and a default route to a gateway there. Plus for loopback. In the kernel I have the following network options in addition to GENERIC: options IPFIREWALL options DUMMYNET options BRIDGE options "ICMP_BANDLIM" options IPDIVERT options IPFIREWALL_FORWARD (I don't need BRIDGE and IPDIVERT though.) -- Anders. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000617183401.A16130>