From owner-freebsd-isp Wed Oct 7 05:00:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08014 for freebsd-isp-outgoing; Wed, 7 Oct 1998 05:00:27 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07998 for ; Wed, 7 Oct 1998 05:00:19 -0700 (PDT) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.8.7/8.8.7) id WAA26831; Wed, 7 Oct 1998 22:00:11 +1000 Received: from tar-ppp-177.tpgi.com.au(203.26.26.177), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpda26811; Wed Oct 7 22:00:06 1998 Message-ID: <361B579C.69089B21@tpgi.com.au> Date: Wed, 07 Oct 1998 21:59:24 +1000 From: Eddie Irvine X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Stephan Mantler CC: freebsd-isp@FreeBSD.ORG Subject: Re: fun with route(8) ... References: <361A4ACF.E61A54AA@imagination.at> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephan Mantler wrote: > I'm experiencing a surprising amount of trouble with our local routing > configuration. Basically, we have a freebsd box with three interfaces: > 192.168.1.1/24 and 192.168.2.1/24 to the local subnets and one for > the uplink. The problem is that the next-hop router is on a different > class C subnet than the gateway's uplink interface (which is a /32 > address). > > the gateway is running 2.2CAM-19980716-SNAP (on top of 2.2.7). > > Let's say the gateway's external interface was 194.123.123.250, and > the uplink 194.123.128.10/24. > > So what we tried was: > route add -host 194.123.128.10 194.123.123.250 -interface > route add -net default 194.123.128.10 > > result: couldn't even ping the uplink. second route doesn't work, > 'network unreachable' (why is that? according to the man pages, > -interface specifies that the dst is directly reachable!). specifying > the interface name as the gateway address (ie. route add -host > 194.128.128.10 -interface xl2) didn't work either. > > after endless hours of poking around, i finally found a way to trick > freebsd into doing the right thing: > > - ifconfig the uplink interface to /16 > - add routes (works now, bsd believes they are on the same subnet) > - ifconfig interface back to /32 > > what am i missing out? (this ugly hack can't be the only way, right?) > > thanks in advance for any comments/help, > -step. Umm, since no one else has replied yet... I kinda thought that the IP router closest to you HAD to be on the same IP subnet as your interface. What IP number is at the other end or your gateway interface? Let me know how you get on. Eddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message