Re: ip ro get problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2004-09-15 at 06:45, Sandro Dentella wrote:
> Hi all,
> 
> I'm using ip route get to debug a routing probelm and I get:
> 
>     root@fw-euronet argo # ip route get 192.168.254.10 
>     192.168.254.10 dev eth0  src 192.168.254.1 
> 	cache  mtu 1500 advmss 1460
>     root@fw-euronet argo # ip route get 192.168.254.10 from 192.168.5.2
>     RTNETLINK answers: Invalid argument
> 
> 
> What does really mean "RTNETLINK answers: Invalid argument", 

means that the IP address 192.168.254.10 does not exist on this host.

> 
> 
> I get the same error w/
> 
>     root@fw-euronet argo # ip route get 192.168.254.10 iif tun0
>     RTNETLINK answers: Invalid argument
> 
> My rules are:
>     root@fw-euronet argo # ip ru li
>     0:      from all lookup local 
>     30:     from all iif tun0 lookup adsl 
>     38:     from 192.168.254.10 lookup hdsl 
>     40:     from 217.58.51.160/27 lookup hdsl 
>     41:     from 81.121.243.248/30 lookup adsl 
>     52:     from all iif eth0 lookup adsl 
>     53:     from all iif eth2 lookup adsl 
>     32766:  from all lookup main 
>     32767:  from all lookup default 
> 
> where you can see that tun0, where 192.168.5.0/24 is, should look table adsl
> that is define this way:
> 
>     root@fw-euronet argo # ip ro ls table adsl
>     81.121.243.248/30 dev eth3  scope link  src 81.121.243.250 
>     217.58.51.160/27 dev eth1  scope link  src 217.58.51.162 
>     192.168.5.0/24 dev tun0  scope link 
>     192.168.1.0/24 dev eth2  scope link  src 192.168.1.1 
>     192.168.254.0/24 dev eth0  scope link  src 192.168.254.1 
>     default via 81.121.243.249 dev eth3 
> 
>    
> TYA
> sandro
> *:-)
-- 
Jason Opperisano <opie@xxxxxxxxxxx>



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux