Date: Sat, 20 May 1995 05:13:27 +1000 From: Mark Treacy <mark@labtam.oz.au> To: freebsd-hackers@freefall.cdrom.com Subject: Re: More on "Hmm.. Strange..." Message-ID: <199505191913.FAA01726@labtam.labtam.OZ.AU>
next in thread | raw e-mail | index | archive | help
>>I personally think there is a bug in the FreeBSD lookups somewhere, >>perhaps as part of the Multicast merge.. 4.4BSD networking can't suck that >>badly, can it? Especially after the measures that 4.3BSD and 4.4BSD has >>taken to make sure that it does work.. > Perhaps, but I've never been able to get multiple SLIP links working when >the local end was in the same subnet...and this dates back to the early >days of 386BSD. > All I can say is that I've never seen it work. If it worked at one time, it >must have been long ago (before Net/2?). Just to clarify, we're talking about the situation where an ethernet interface and a bunch of ppp interfaces all share a common ip address ? If we are, then in my experience this has worked in 4.3bsd-tahoe, 4.3bsd-reno, and 4.3bsd-net2. I don't remember anything in 4.2 or 4.3 that would prevent sharing either. I haven't used 4.4bsd-lite based code in this setup, but I would be very surprised if it didn't work. A useful command to use when diagnosing these type of problems is route(1). Along with the radix tree routing introduction came a rewritten route command. One of the new keywords is "get". Get uses the route socket to get the kernel to do a route lookup. Try, route -vn get nn.mm.oo.pp Another useful variant is, route -vn get nn.mm.oo.pp -ifa 11 Which gets the kernel to return the AF_LINK address of the interface (which when printed out by route(1) conveniently tells you the interface name). The -ifa argument is just a bogus address to put in the message it stuffs down the route socket. - Mark.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505191913.FAA01726>