Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Jul 2001 16:54:29 +0300 (EEST)
From:      Iasen Kostoff <tbyte@tbyte.org>
To:        Ruslan Ermilov <ru@FreeBSD.ORG>
Cc:        freebsd-net@FreeBSD.ORG
Subject:   Re: adding a route to host via interface
Message-ID:  <Pine.BSF.4.21.0107031644290.35452-100000@shadow.otel.net>
In-Reply-To: <20010703162556.E39090@sunbay.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On Tue, 3 Jul 2001, Ruslan Ermilov wrote:

> On Tue, Jul 03, 2001 at 03:34:14PM +0300, Iasen Kostoff wrote:
> > 
> > 
> > On Tue, 3 Jul 2001, Ruslan Ermilov wrote:
> > 
> > > On Tue, Jul 03, 2001 at 02:30:48PM +0300, Iasen Kostoff wrote:
> > > > 
> > > > 
> > > > On Tue, 3 Jul 2001, Ruslan Ermilov wrote:
> > > > 
> > > > > On Mon, Jul 02, 2001 at 05:40:07PM +0300, Iasen Kostoff wrote:
> > > > > > 
> > > > > > 	Problem is that adding a route to host throw interface adds
> > > > > > inerface as gateway (iface's lladdr). And you should manualy change lladdr
> > > > > > of this route to the real lladdr.
> > > > > > 
> > > > > > this is it:
> > > > > > 
> > > > > > route add -host foo -iface bar
> > > > > > arp -s foo real_lladdr_of_foo
> > > > > > 
> > > > > > Is that realy a problem or I'm missing something ?
> > > > > > 
> > > > > Try this:
> > > > > 
> > > > > route add -host foo -link bar:real_lladdr_of_foo -llinfo -interface
> > > > > 
> > > > But if I don't know the lladdr - because now I should use tcpsump(1) with
> > > > -i iface -e to see the lladdr of the client and when they change their GW
> > > > computer or its Lan card I should do that again (and if am not around they
> > > > don't have inet ofcourse) but if they are connected on cisco router that
> > > > do not hapen because I'm not routing to lladdr but throw iface.
> > > > 
> > > > Can that be fixed some how ?
> > > > 
> > > I apparently lost the context here.  What are you trying to do?
> > > You want the host ``foo'' to be resolved through ARP?  If that
> > > is the case, this is somewhat tricky, but still possible:
> > > 
> > > route add foo/32 -iface bar -cloning
> > > 
> > > 
> > I tried - route add foo -iface bar -cloning and it didin't work ofcourse :).
> > 
> Yup, should be ``arp: couldn't allocate llinfo for <foo>rt''.
> 
> > I think route(8) or /sys/net/route.c should reject that kind of route.
> > I tried to set or convert it to -net route - foo/32(I think the second way is
> > better, what you think ?).
> > 
> You can't change host route to network route, or vise versa; destination
> is the Patricia's tree key, and it can't be changed.  The only possible
> way is like I suggested: ``route add foo/32 -iface bar -cloning''.

Yes I know, but ``route add foo -iface bar -cloning`` is meanless, I
think, because host route could not be cloned and I kernel should auto set
foo to foo/32 because of meanlessness of -host foo. And is route add -host
foo -iface bar (without -cloning) could be used for something ?

>
> <PS>
> You still did not tell me what are you trying to do.  :-)
> </PS>
>

I'm trying to make routing on FreeBSD as easier and streight forward as it
is in cisco's routers(and may be better). :-)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" 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.4.21.0107031644290.35452-100000>