From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: JP Abgrall <jpa@google.com>
Cc: netdev@vger.kernel.org
Subject: Re: Question about default route handling/lookup in a custom table
Date: Tue, 23 Jul 2013 15:47:15 +0200 [thread overview]
Message-ID: <20130723134715.GC32523@order.stressinduktion.org> (raw)
In-Reply-To: <CAKP4w2Q_5V=2CdyUpeXrHg=dTv1LNynp87gy6nrQYWYyBuA39A@mail.gmail.com>
Hello!
On Mon, Jul 22, 2013 at 06:20:18PM -0700, JP Abgrall wrote:
> The following sequence fails when adding the default route:
> (wlan0 is up, nothing is trying to manage,...)
>
> ip route flush dev wlan0 table all
> ip route flush table 60
> ip route add 1.1.1.1/32 dev wlan0 table 60
I am not sure but would have expected that you needed to add a rule e.g. ip
rule add oif wlan0 table 60 to successfully match the next route insertion.
> ip route add default via 1.1.1.1 dev wlan0 table 60
Otherwise another rule lookup could alter the fib_lookup in such a way that the
nexthop is not resolveable and the routing table in its entirty could have
unresolveable holes.
I did not check the code, this is just my intuition.
Greetings,
Hannes
next prev parent reply other threads:[~2013-07-23 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 1:20 Question about default route handling/lookup in a custom table JP Abgrall
2013-07-23 13:47 ` Hannes Frederic Sowa [this message]
2013-07-23 17:58 ` JP Abgrall
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=20130723134715.GC32523@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=jpa@google.com \
--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).