From: Markus Wick <markus@selfnet.de>
To: netdev@vger.kernel.org
Subject: BugReport: "ip route local ..." outside the table 255 (local)
Date: Mon, 29 Jun 2009 18:46:16 +0200 [thread overview]
Message-ID: <200906291846.20962.markus@selfnet.de> (raw)
In-Reply-To: <200906250238.40369.markus@selfnet.de>
[-- Attachment #1: Type: Text/Plain, Size: 541 bytes --]
Hello
Has anybody tried it? I think it is a bug but I don't know where.
Perhaps the mistake is in the routing decision (or in the userspace
application). iptables trace shows the packages in the filter/input table.
Perhaps socket lookout?
Please can somebody try the following example and confirm it:
sudo ip route add local 192.168.56.0/24 dev eth0 table local
ping 192.168.56.1
## *succeed*
sudo ip route add local 192.168.57.0/24 dev eth0 table main
ping 192.168.57.1
## connect: Invalid argument
Thanks
Markus
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2009-06-29 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 0:38 "ip route local ..." outside the table 255 (local) Markus Wick
2009-06-29 16:46 ` Markus Wick [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=200906291846.20962.markus@selfnet.de \
--to=markus@selfnet.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).