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@xxxxxx>
