From owner-freebsd-questions Sat Dec 5 01:17:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22551 for freebsd-questions-outgoing; Sat, 5 Dec 1998 01:17:34 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mail.AMS.Med.Uni-Goettingen.DE (ikarus.AMS.Med.Uni-Goettingen.DE [134.76.140.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22546 for ; Sat, 5 Dec 1998 01:17:33 -0800 (PST) (envelope-from Sven.Anderson@AMS.Med.Uni-Goettingen.DE) Received: from sanders (helo=localhost) by mail.AMS.Med.Uni-Goettingen.DE with local-smtp (Exim 1.92 #1) for freebsd-questions@freebsd.org id 0zmDpy-0000AY-00; Sat, 5 Dec 1998 10:17:14 +0100 Date: Sat, 5 Dec 1998 10:17:05 +0100 (MET) From: Sven Anderson To: freebsd-questions@FreeBSD.ORG Subject: Static host routes don't work? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- 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 thourght, 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) -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: latin1 iQBVAwUBNmj6Go9smRlwmxeVAQEBkwH/Urw2gpyiDvKZx1HPQZswpz5wQi4WvP6F 6DKyT28uZL9xDteMZPh/zIP/9088zF8zYV3OsjC+QZjrf4LXgxbgOg== =Pncz -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message