> On May 3, 2016, at 1:02 PM, Flaviof <fla...@flaviof.com> wrote: > > [cc Justin] > > Hello OVS/OVN folks, > > Using devstack and a slightly modified version of the local.conf.sample [1], > I create an all-in-one node with OVN. > > After stacking, I run a simple script [2] (attached) that creates 2 internal > subnet+networks and a OVN-L3 router with interfaces on each one of them. > > It then creates a vm in each network, which makes it look like this: > > vm1 ---- net1 ---- rtr ---- net2 ---- vm2 > 10.1.0.x 10.2.0.x > > The script adds an internal port to connect to net1 [br-int], so we get to vm1 > w/out relying on dhcp namespace. With that, I can ping from vm1 to vm2 and > also the interface of rtr on net1. However, I cannot ping [3] the rtr > interface on > net2 (i.e. 10.2.0.1) from vm1 (i.e. 10.1.0.3). > > Is that expected to work? I will dig into the flow rules to see if this is a > known > limitation, but would like to ask you guys to avoid wasting too much energy. > :) > I do understand that special rules have to be added so icmp replies [table17] > are sent on behalf of the router interface. There was a similar issue [4] in > ODL, which made some L3 tempest tests fail. It is possible that is the case > still.
That is consistent with my recollection of how pinging the router works: you can only ping the side that's adjacent to the sender. That would be nice to fix. --Justin _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss