On Tue, Sep 16, 2014 at 9:14 AM, samantha Andares <[email protected]> wrote: > Hi, > > I have a node with 3 physical ports (2 are part of an OVS bridge, 1 is not). > > The OVS bridge and data is getting data from an other node. But I want this > data to go out to the 3rd port on that node that is not part of the bridge. > I created a rule with actions=NORMAL which I thought would use the default > ip forwarding table... but it doesn't work.... I see the rule being hit for > every single packet but the packets are not making it to that other port... > how can I achieve that?
I don't think you can achieve that. NORMAL action will only work on ports of a bridge. There are some options that I can think of (whether it is of any use to you, depends on your use case): * You can create a tunnel on the bridge such that the remote_ip of the tunnel is reachable via your third port. In that case, your remote end point should be capable of decapsulating the tunnel header. * You can create another OVS bridge and attach the independent interface as a port of that bridge and then use a patch port to connect them. You can also use a veth pair like openstack does. (http://docs.openstack.org/grizzly/openstack-network/admin/content/under_the_hood_openvswitch.html) > > thanks > > samantha > > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
