From owner-freebsd-hackers Sun Jan 4 10:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14777 for hackers-outgoing; Sun, 4 Jan 1998 10:51:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14744; Sun, 4 Jan 1998 10:51:15 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id TAA17725; Sun, 4 Jan 1998 19:51:04 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id TAA19192; Sun, 4 Jan 1998 19:31:38 +0100 (MET) Message-ID: <19980104193137.01479@uriah.heep.sax.de> Date: Sun, 4 Jan 1998 19:31:37 +0100 From: J Wunsch To: Brian Somers Cc: Greg Lehey , John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point Reply-To: Joerg Wunsch References: <19980104110521.14399@uriah.heep.sax.de> <199801041629.QAA04727@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199801041629.QAA04727@awfulhak.demon.co.uk>; from Brian Somers on Sun, Jan 04, 1998 at 04:29:33PM +0000 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As Brian Somers wrote: > Not quite. I was suggesting that instead of the first, we have the > second, or in fact > > route add 1.2.3.4 -netmask 0xffffff00 1.4.5.6 > > If you specify a 0xffffffff netmask, you get the same as the existing > stuff *always* does. However, since most people don't bother messing with the netmask on p2p interfaces at all (why should they), they'll always catch the default netmask, so the above will violate the principle of least surprise for them (configurations that used to work would no longer work). > The real purpose, as you've already suggested, is that you get the > associated broadcast address. With this broadcast address, all sorts > of other things work (timed, rwhod, nmbd etc.), assuming that you've > got a proxy arp setup on the other end. Proxy arp is a hack. We shouldn't encourage using hacks. If people are interested in using hacks, they should have more work to be done than those who are interested in clean setups. (Sure, like all hacks, there are situations why proxy arp can be useful. vfork() is another example of a useful hack. Recommending proxy arp as a general method is ugly. Setup correct IP routing instead.) > Of course, this implies that the destination address isn't actually > required - as with a real network. `Real' networks have broadcast addresses, but aren't point-to-point. `Real' networks can't share the same local adress for different interfaces, p2p interfaces can. `Real' networks have native broadcasting, p2p interfaces don't. p2p interfaces always connect to just one remote address, that's why they are called by this name. ;) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)