On Thu, Sep 03, 2015 at 09:26:17AM -0700, ALeX Wang wrote: > tried this out, looks useful,
Yeah, try on a openstack compute node with some tenants. It uses namespaces, veth pairs, ovs bridges, internal ports, tunnels, linux bridges, etc. Of course, it's possible to trace the path of a packet, but it's time consuming and the names aren't exactly human friendly :) The tool helps a lot with those sophisticated scenarios. fbl > > Look good to me, > > Thanks, > Alex Wang, > > On 3 September 2015 at 07:53, Flavio Leitner <f...@sysclose.org> wrote: > > > The plotnetcfg is an open source tool to visualy represent > > relationship between network interfaces on a single host. > > > > It helps to understand the path of a packet on a host. > > > > Signed-off-by: Flavio Leitner <f...@sysclose.org> > > --- > > FAQ.md | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/FAQ.md b/FAQ.md > > index 5ce42b9..631f6a4 100644 > > --- a/FAQ.md > > +++ b/FAQ.md > > @@ -1623,6 +1623,9 @@ A: To debug network behavior problems, trace the > > path of a packet, > > that's correct, then trace the path of the response packet back to > > the origin. > > > > + The open source tool called "plotnetcfg" can help to understand the > > + relationship between the networking devices on a single host. > > + > > Usually a simple ICMP echo request and reply ("ping") packet is > > good enough. Start by initiating an ongoing "ping" from the origin > > host to a remote host. If you are tracking down a connectivity > > -- > > 2.1.0 > > > > > > _______________________________________________ > > dev mailing list > > dev@openvswitch.org > > http://openvswitch.org/mailman/listinfo/dev > > > > > > -- > Alex Wang, > Open vSwitch developer > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev