From owner-freebsd-net Wed Mar 5 10:28: 8 2003 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D519A37B405 for ; Wed, 5 Mar 2003 10:28:06 -0800 (PST) Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3213A43FA3 for ; Wed, 5 Mar 2003 10:28:05 -0800 (PST) (envelope-from jwb@homer.att.com) Received: from ulysses.homer.att.com ([135.205.193.8]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h25IS0Fl024919; Wed, 5 Mar 2003 12:28:01 -0600 (CST) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.212.39]) by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id NAA24922; Wed, 5 Mar 2003 13:28:00 -0500 (EST) Received: from akiva.homer.att.com (localhost [127.0.0.1]) by akiva.homer.att.com (8.11.6+Sun/8.9.3) with ESMTP id h25IRxF05514; Wed, 5 Mar 2003 13:27:59 -0500 (EST) Message-Id: <200303051827.h25IRxF05514@akiva.homer.att.com> X-Mailer: exmh version 2.6.1 02/18/2003 with nmh-1.0.4 To: Kevin_Stevens@pursued-with.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: route pointing to a gateway that's not on net In-reply-to: Your message of "Wed, 05 Mar 2003 09:57:55 PST." <30622.192.85.47.1.1046887075.squirrel@new.host.name> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Mar 2003 13:27:59 -0500 From: "J. W. Ballantine" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Well it's not the way I wanted it, but it's the way I have to try and work with. I tried the route add net 10.0.0.0 -interface (whatever) and that didn't work for me. ---------- In Response to your message ------------- > Date: Wed, 5 Mar 2003 09:57:55 -0800 (PST) > To: > From: "Kevin Stevens" > Subject: Re: route pointing to a gateway that's not on net > > > > > I was recently following a thread on tech-netbsd that was discussing the > > routing tables when the gateway address was on a 10.x.x.x network while > > the machine was assigned a 209.122.66.x address. The long and short of > > the discussion (as I understand the discussion) was that this was that > > while it can be accessed via windose and Linux ( > > > > On Linux, we could do this to get around that minor problem: > > route add -host 192.168.14.88 dev eth0 > > ) that is was an evil, ugy illegal network route and that it not > > possible, will not be implemented in NetBSD. > > It is all of that. ;) I've used this in a network setup where there were > multiple local links that terminated at a remote router, and the desire > was that traffic be able to flow over any of them. But it leaves a bad > taste in my brain, like when Cisco refers to "layer three switching". > > > Now since my cable ISP has me provised it this manner, and since I can't > > find a method to get out from FreeBSD using the route command. I was > > wondering if a) I missed something and there is some option for the > > route command that allows to route to be setup, or if not will netgraph > > allow me to setup this route? > > I think you do it the same way. Can't you create a route to the 10.x.x.x > subnet that simply points to the outbound interface? (rummaging around > for network access to router...) > > Yes, you can use the -interface option with the route command. Try this: > route add -net 10.0.0.0 -interface (whatever). Worked for me in at least > adding the route, I don't have a ready way to test it at the moment. > > KeS > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message