From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2: gatewayed routes in ancillary tables
Date: Tue, 06 May 2003 14:33:15 +0000 [thread overview]
Message-ID: <marc-lartc-105223162718690@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105215601317386@msgid-missing>
Hello,
On Tue, 6 May 2003, Martin A. Brown wrote:
> : After "via" you can use local IP in addition to unicast
> : one. You know it but the kernel is not sure.
>
> For me, this is new--I struggle to imagine a case where I would use this
> sort of syntax. So, if I use "via <local-IP>", the kernel will
> essentially treat the route as though I had specified "dev <interface>",
> right?
Yes, this is sort of "find dev for this local IP and use
it as outdev".
> : But, considering the fact that GW IPs are always
> : onlink (the kernel ignores the many variants of scopes and
> : lookups only for onlink GWs),
>
> Ah-ha! And, as well as an explanation, you have given me a solution. In
> this case, I can use the following:
>
> ip route add 192.168.237.0/24 dev eth0 table 4
> ip route add 192.168.236.0/24 via 192.168.237.1 dev eth0 onlink table 4
I'm glad you saw it because I forgot about it :)
> The onlink tells the kernel what I know; that my use of "via" in this case
> is for a nexthop as a unicast destination.
The only problem is that "onlink" can succeed even if
IP is not enabled for this device (may be there is a reason for
this) but I hope this is not a big problem.
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-06 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 17:23 [LARTC] iproute2: gatewayed routes in ancillary tables Martin A. Brown
2003-05-05 23:04 ` Julian Anastasov
2003-05-06 3:33 ` Martin A. Brown
2003-05-06 8:58 ` Julian Anastasov
2003-05-06 13:56 ` Martin A. Brown
2003-05-06 14:33 ` Julian Anastasov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105223162718690@msgid-missing \
--to=ja@ssi.bg \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox