[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJmoNQFMdN5purj9TsUAmuEExQy0tmENjS2CyTrkbqWneb+ziQ@mail.gmail.com>
Date: Mon, 8 Jun 2015 12:51:04 -0700
From: Shrijeet Mukherjee <shm@...ulusnetworks.com>
To: David Ahern <dsahern@...il.com>
Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Jamal Hadi Salim <hadi@...atatu.com>,
David Miller <davem@...emloft.net>,
Stephen Hemminger <stephen@...workplumber.org>,
Netdev <netdev@...r.kernel.org>,
Roopa Prabhu <roopa@...ulusnetworks.com>,
Andy Gospodarek <gospo@...ulusnetworks.com>,
Jon Toppins <jtoppins@...ulusnetworks.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Subject: Re: [RFC net-next 0/3] Proposal for VRF-lite
Good catch, as you know I used to have the device getting modified in
the RX path and that made it all work
generic ip_rcv will need a fix to make RX visible to tcpdump, but yes,
that is the goal.
On Mon, Jun 8, 2015 at 12:13 PM, David Ahern <dsahern@...il.com> 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.
--
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