From owner-freebsd-questions Fri Feb 16 03:42:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA00403 for questions-outgoing; Fri, 16 Feb 1996 03:42:19 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA00396 for ; Fri, 16 Feb 1996 03:41:58 -0800 (PST) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id NAA14060; Fri, 16 Feb 1996 13:44:48 +0200 Date: Fri, 16 Feb 1996 13:44:47 +0200 (EET) From: Narvi To: questions@freefall.freebsd.org Subject: Re: proxy ARP on ethernet?? In-Reply-To: <199602152236.OAA29441@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG Precedence: bulk > ------------------------------ > > From: "matthew c. mead" > Date: Thu, 15 Feb 1996 14:29:22 -0500 (EST) > Subject: Re: proxy ARP on ethernet?? > > Garrett A. Wollman wrote: > > > >> No you should not be able to do so. It might be possible, but only > > >> because of insufficient error checking in the kernel. > > > > > Proxy arping with packet forwarding having two interfaces on the same > > > subnet is not supposed to be a valid option? I've know a lot of people to do > > > this when the provider has hubs that only allow one mac address per port... > > > IP addresses name interfaces, not hosts. It is not valid to assign > > I know what IP addresses name :-) > > > the same IP address to two interfaces. (We actually sort-of support a > > configuration called a ``half-router'' where this is not true, but > > only one of the interfaces can be multiple-access; the others have to > > be point-to-point. I would just as soon not support this either, but > > enough people use it to make desupporting in politically impossible.) > > What I'm talking about is an alternative that will allow him to do what > he wants - having two separate ip addresses for on his "pseudo-router" machine, > both on the same subnet... This would allow forwarding between the two > interfaces, and proxy arping so that the hosts on the internal wire could get > to the rest of the net as well. This can be done - though it is not too simple. Let's assume he has got a regular class C net: x.y.z.0...255. nad he wants, for some reason do it so that half the adresses were on one wire and half on the other, yet so that no-one else should bother about it. So - split the adress space into two - the parts need not be equal, but one of them must be in the upper part of the other - the first from x.y.z.0 - x.y.z.191 and the second from x.y.z.192 - x.y.z.255. Please don't argue about the sizes of the subnets yet - read a bit on. The trick is to have the FreeBSD router have one IP address from the first subnet and the other one from the second. Now you tell to the FreeBSD router and the hosts on the second subnet the real subnet and broadcast address, enable proxy arp on the FreeBSD router and don't tell the hosts/routers on the first subnet anything about the changes - if one of them want's to talk to a host on the second one, it just asks for it's ethernet address, it does so and the FreeBSD router proxy answers and fowards the packet. Pros and cons: 1) may require to rename/renumber some hosts 2) if you can't have space at the end of the first subnet's address space, you will loose 2 IP addresses, if you can, still 1 IP. 3) Lets you do what you want > - -matt > Sander.