Date: Thu, 31 Oct 1996 17:52:17 -0100 From: Darius Moos <moos@degnet.baynet.de> To: "Daniel O'Callaghan" <danny@panda.hilink.com.au> Cc: FreeBSD-questions <questions@freebsd.org>, freebsd-hackers <freebsd-hackers@freebsd.org>, rkw@dataplex.net, jmg@nike.efn.org Subject: Re: Is this network possible with FreeBSD ??? Message-ID: <3278F561.5140@degnet.baynet.de> References: <Pine.BSF.3.91.961031230206.3907T-100000@panda.hilink.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, that did the trick. The FreeBSD-box is up and running and everything works as it should. Now i'm glad that the FreeBSD-box will not be trashed :) and Linux won't find it's way to this customer. I've written a little script that cycles through ranges of IP-adr.es and arp's them to a specific ethernet-adr. (the one of the router) at bootup. Thanks again to all the people on this list for their help. Special thanks to: Daniel O'Callaghan Gary Palmer Joe Greco John-Mark Gurney Julian Elischer Mattias Pantzare Michael Smith Narvi Ollivier Robert Pedro Giffuni Richard Wackerbarth Thinker Li Darius Moos. And yes Richard W., i am an idiot. Daniel O'Callaghan wrote: > > On Thu, 31 Oct 1996, Darius Moos wrote: > > > > > It has just a simple ifconfig like: > > ifconfig ed1 inet 1.2.3.36 > > route add 1.2.3.253 ed1 > > route add 1.2.3.0 isdn > > > > It really adds a route with the destination being a device instead of > > an IP-adr. > > OK, you can do this with FreeBSD using ipfilter by Darren Reed. > > YOu could also use a netmask of 255.255.255.0 for 1.2.3.253 ed0, and > arp -s all of the other 1.2.3.x hosts onto the router. THat would work. > > I still think the ISP is in error in assigning you two separate IPs on > the same network. > > Danny -- email: moos@degnet.baynet.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3278F561.5140>