Date: Mon, 7 Dec 1998 11:54:47 -0800 (PST) From: Dan Busarow <dan@dpcsys.com> To: Sven Anderson <Sven.Anderson@AMS.Med.Uni-Goettingen.DE> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Static host routes don't work? Message-ID: <Pine.BSF.3.96.981207114646.1393N-100000@java.dpcsys.com> In-Reply-To: <Pine.LNX.3.96.981207184621.13982B-100000@ikarus.AMS.Med.Uni-Goettingen.DE>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Dec 1998, Sven Anderson wrote: > why does nobody answer me? Is it my english (it's bad, i know), is it Your English isn't bad at all. I've seen native speakers write worse. > such a newbie-question not worth answering it (but then it should > be in the FAQ), or has really nobody here ever used static host routes? > > It would be great, if you could give me at least a comment, which other > resources/mailing-lists I should use to get a solution. I think there were no answers because a) you shouldn't be doing that (putting a 192 host on a 172 net) :) b) you had a work around c) you knew the correct answer (use a subnet) Dan -- Dan Busarow 949 443 4172 Dana Point Communications, Inc. dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 > ---------- Forwarded message ---------- > Date: Sat, 5 Dec 1998 10:17:05 +0100 (MET) > From: Sven Anderson <Sven.Anderson@AMS.Med.Uni-Goettingen.DE> > To: freebsd-questions@FreeBSD.ORG > Subject: Static host routes don't work? > > Hi, > > I'm running 2.2.8-RELEASE, and I noticed, that static host routes to > directly connected hosts don't seem to work correctly. I have the > following Problem: > > 192.168.25.0/24 ------ed1 |FreeBSD| de0-------- 172.27.0.0/16 > | > ---- Host 192.168.25.224 > > where the addresses of the interfaces of the BSD-Box are: > ed1: 192.168.25.223 > de0: 172.27.10.254 > > For the single host I need a hostroute to de0, and i thought, this line > should do the job: > > # route add -host 192.168.25.224 -interface 172.27.10.254 > > After that the routingtable looks fine so far: > > 192.168.25.224 172.27.10.254 UHS 0 0 de0 > > but it doesn't work, no arp-requests for 192.168.25.224 on de0. > > Because i was not sure, if it is a netmask-problem, I tried the same with > an address out of 172.27.0.0/16, for example 172.27.1.1, which was routed > correctly before, and from this moment on the address was unreachable. It > seems that static host routes don't route but block, and no arp-requests > happen anymore for that address. > > Then i tried the -interface-option with the real device-name: > > # route add -host 192.168.25.224 -interface de0 > > and it created a permanent arp-entry, but with the ether-address of the > adapter of de0, again no arp-request was done. With arp -s I manually set > the ether-address to that of the host, and, WOW, it works! But this can't > be the way to do it, can it? I would like to have a solution, where I > don't have to set the ether-address by hand but it is determined by an > arp-request. > > Btw.: if I route a whole subnet (at least 2 IPs), there's no problem > anymore, fine arp-requests, fine connects. > > I'm really confused, and from my point of view this is a bug, but maybe > someone can explain me, what I'm doing wrong? > > Thanks in advance, > > Sven > > -- > * email: sa@kki.org * fon.net: ++49-551-35430 > * www: http://tuttle.home.pages.de/ * irc: tuttle > "Macht verrueckt, was Euch verrueckt macht!" (Blumfeld) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981207114646.1393N-100000>