From: Sandro Dentella <sandro@e-den.it>
To: iptables <netfilter@lists.netfilter.org>
Subject: ip ro get problem
Date: Wed, 15 Sep 2004 12:45:01 +0200 [thread overview]
Message-ID: <20040915104501.GA10207@bluff> (raw)
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",
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
*:-)
--
Sandro Dentella *:-)
e-mail: sandro@e-den.it
http://www.tksql.org TkSQL Home page - My GPL work
next reply other threads:[~2004-09-15 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 10:45 Sandro Dentella [this message]
2004-09-15 11:53 ` ip ro get problem Jason Opperisano
2004-09-15 13:51 ` Alistair Tonner
2004-09-15 14:03 ` Sandro Dentella
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=20040915104501.GA10207@bluff \
--to=sandro@e-den.it \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.