From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: Re: Strange routing with VRF and 5.2.7+
Date: Tue, 10 Sep 2019 18:08:47 -0700 [thread overview]
Message-ID: <51aae991-a320-43be-bf73-8b8c0ffcba60@candelatech.com> (raw)
In-Reply-To: <91749b17-7800-44c0-d137-5242b8ceb819@candelatech.com>
On 9/10/19 3:17 PM, Ben Greear wrote:
> Today we were testing creating 200 virtual station vdevs on ath9k, and using
> VRF for the routing.
Looks like the same issue happens w/out VRF, but there I have oodles of routing
rules, so it is an area ripe for failure.
Will upgrade to 5.2.14+ and retest, and try 4.20 as well....
Thanks,
Ben
>
> This really slows down the machine in question.
>
> During the minutes that it takes to bring these up and configure them,
> we loose network connectivity on the management port.
>
> If I do 'ip route show', it just shows the default route out of eth0, and
> the subnet route. But, if I try to ping the gateway, I get an ICMP error
> coming back from the gateway of one of the virtual stations (which should be
> safely using VRFs and so not in use when I do a plain 'ping' from the shell).
>
> I tried running tshark on eth0 in the background and running ping, and it captures
> no packets leaving eth0.
>
> After some time (and during this time, my various scripts will be (re)configuring
> vrfs and stations and related vrf routing tables and such,
> but should *not* be messing with the main routing table, then suddenly
> things start working again.
>
> I am curious if anyone has seen anything similar or has suggestions for more
> ways to debug this. It seems reproducible, but it is a pain to
> debug.
>
> Thanks,
> Ben
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2019-09-11 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 22:17 Strange routing with VRF and 5.2.7+ Ben Greear
2019-09-11 1:08 ` Ben Greear [this message]
2019-09-20 15:57 ` Ben Greear
2019-09-22 19:23 ` David Ahern
2019-09-30 18:45 ` Ben Greear
2019-10-14 17:33 ` Ben Greear
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=51aae991-a320-43be-bf73-8b8c0ffcba60@candelatech.com \
--to=greearb@candelatech.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