[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1433796075.1992197.290139129.5F4BF968@webmail.messagingengine.com>
Date: Mon, 08 Jun 2015 22:41:15 +0200
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: David Ahern <dsahern@...il.com>,
Shrijeet Mukherjee <shm@...ulusnetworks.com>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Jamal Hadi Salim <hadi@...atatu.com>, davem@...emloft.net,
Stephen Hemminger <stephen@...workplumber.org>,
netdev@...r.kernel.org
Cc: roopa@...ulusnetworks.com,
andy gospodarek <gospo@...ulusnetworks.com>,
jtoppins@...ulusnetworks.com, nikolay@...ulusnetworks.com
Subject: Re: [RFC net-next 0/3] Proposal for VRF-lite
On Mon, Jun 8, 2015, at 21:13, David Ahern wrote:
> On 6/8/15 12:35 PM, Shrijeet Mukherjee wrote:
> > 5. Debugging is built-in as tcpdump and counters on the VRF device
> > works as is.
>
> Is the intent that something like this
>
> tcpdump -i vrf0
>
> can be used to see vrf traffic?
>
> vrf_handle_frame only bumps counters; it does not switch skb->dev to the
> vrf device so for Rx path tcpdump will not get the packets. ie., tcpdump
> only shows outbound packets.
My hope initially was that the vrf interface type would be as slim as
possible. I
am not even sure if we need packet counters, as one could easily have
user
space handle that by looking up the relations and accumulating them.
Same
for VRF traffic.
But the current model does allow to add support for that easily, so why
not? It
depends on how far we can and want to move parts of the logic into the
core
stack in the end.
Would you see this as a requirement?
Thanks,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists