Hi Jaime
Thank you - I will try this and see how it works.
David
-Original Message-
From: Jaime Caamaño Ruiz [mailto:jcaam...@suse.de]
Sent: 20 July 2018 14:23
To: Lake D Mr (PG/R - Elec Electronic Eng) ;
netvirt-...@lists.opendaylight.org; openstack@lists.openstack.org
Cc: Ge C Dr (El
With “ovs-ofctl -O OpenFlow13 dump-flows br-int” I don’t see ANY entries for
packets to 48.0.0.0/8 or 16.0.0.0/8
Only this one entry (which I think is a static route which I have in the router
between the floating network and the private network).
David
From: Aswin Suryanarayanan [mailto:asur
Hi Aswin
I’ve just noticed that I don’t think the packet is ever actually making it
through to OVS.
If I do a “ovs-dpctl dump-flows” then I see the immediate drop on ingress port
5.
But if I extend that to “ovs-ofctl -O OpenFlow13 dump-flows br-int” the only
entry I see is:
cookie=0x803,
Hi Aswin
From a “ovs-dpctl dump-flows” I see this:
recirc_id(0),in_port(5),eth(src=a0:36:9f:f6:f9:98,dst=fa:16:3e:f1:8e:3d),eth_type(0x0800),ipv4(src=16.0.0.0/240.0.0.0,dst=48.0.0.0/255.0.0.0,frag=no),
packets:1438, bytes:105356, used:0.005s, flags:S, actions:drop
The src MAC address is the tr