Date: Fri, 29 Dec 1995 09:59:40 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: guido@IAEhv.nl (Guido van Rooij) Cc: freebsd-hackers@freebsd.org Subject: Re: bug in UDP stack with our aliasing scheme :-( Message-ID: <199512291559.JAA08145@brasil.moneng.mei.com> In-Reply-To: <199512291149.MAA13378@iaehv.IAEhv.nl> from "Guido van Rooij" at Dec 29, 95 12:49:46 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I discovered a problem with our ip aliasing implementation: > > Suppose you have an interface, ed0, with ip 192.1.1.1 netmask 0xffffff00. > Further there is an alias 192.1.1.2, with netmask 0xffffffff. > > Run the program attached below with argument 192.1.1.1. Send an UDP > packet to 192.1.1.1. The program will only receive the data on fd1. > When the program is run with argument 192.1.1.2 it receives input > both on fd1 and fd2. > > When the alias is set to an ip on another subnet, say 192.1.2.1 with > netmask 0xffffffff, this bug can be seen again. But when the netmask is > changed to 0xffffff00, the UDP data will be deliverd correctly to only > fd1. This (other than that last bit) is consistent with a BIND (named) server problem that I've been tracking for a while. I would be happy to test any suggested fixes :-) ... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512291559.JAA08145>