From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: ip rule suppress_prefixlength
Date: Mon, 31 Oct 2016 18:24:00 -0400 [thread overview]
Message-ID: <32577.1477952640@turing-police.cc.vt.edu> (raw)
In-Reply-To: <c0b40e3e-e181-5343-45d8-1eb3e3196e4f@uni-muenster.de>
On Sun, 30 Oct 2016 12:25:50 +0100, Matthias Peter Walther said:
> root at des1 ~ # ip rule
> 0: from all lookup local
> 32765: from all iif lo lookup ffnet suppress_prefixlength 0
> 32766: from all lookup main
> 32767: from all lookup default
> (ffnet is table 42)
> root at des1 ~ # ip r s
> default via 5.9.86.151 dev eth0
> 5.9.86.151 dev eth0 proto kernel scope link src 5.9.86.144
> root at des1 ~ # ip r s t 42
> blackhole default
> Let's say I want to ping 8.8.8.8. What I expect is, that the package is
> put into routing table 42 by the ip rule 32765. As there is no more
> specific route for 8.8.8.8 than the default route in table 42, I expect
> the suppress_prefixlength 0 option to put it back to the default routing
> table and then to be send out through eth0.
Note your table 42 is a blackhole. I suspect that using 'suppress_prefixlength
0' is acting differently than you expect - you've told it to use table 42 which
has only a blackhole, and when it suppresses that route, there is no *other*
route in table 42 to select - leaving you with a 'no route' situation. I don't
think it's supposed to make the 'lookup ffnet' part go away, only entries *IN*
that table that are longer than specified (which for 0 means "all of them").
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161031/4008132e/attachment.bin
next prev parent reply other threads:[~2016-10-31 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 11:25 ip rule suppress_prefixlength Matthias Peter Walther
2016-10-31 22:24 ` Valdis.Kletnieks at vt.edu [this message]
2016-11-01 10:58 ` Matthias Peter Walther
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=32577.1477952640@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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.