Use : route add -net 10.17.47.37/32 -cloning -iface xl0
that sould work. On Wed, 5 Mar 2003, J. W. Ballantine wrote: > > Sorry, my typo. I did try > route add -net 10.0.0.0 -interface xl0 > and > route add -net 10.17.47.37 -interface xl0 > > As I recall both didn't respond with a error message, but when I tried to > get out it didn't work. > > I'll try again tonight and see what happens. > > Thanks > > ---------- In Response to your message ------------- > > > Date: Wed, 5 Mar 2003 10:47:30 -0800 (PST) > > To: <[EMAIL PROTECTED]> > > From: "Kevin Stevens" <[EMAIL PROTECTED]> > > Subject: Re: route pointing to a gateway that's not on net > > > > > > > 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. > > > > That's not the syntax I gave you, and obviously it needs to have your > > local interface information inserted. I can confirm that the command: > > > > route add -net 10.0.0.0 -interface em0 > > > > does parse and operate correctly on my 4.7 system, as confirmed by netstat > > -nr. That is the general approach for directing traffic out a local > > interface rather than to a same-subnet gateway. > > > > Try looking at man route for the details, or perhaps someone else will > > respond with a higher level of hand-holding. > > > > KeS > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
