[ovs-discuss] Pointers needed

[Raymundo Vega]

After several tests, look to me like ovs use the kernel routing engine for
next hop packet delivery, even in vlaned network, so behavior on this
issue is same as with 8021q kernel module.

Just in case somebody hits same problem, i had to modify kernel routing
engine, to force it to use on packet delivery the interface that has source
IP used in the packet and then honor the vlan tag in deliveries.

Thanks and happy holidays

raymundo



On Thu, Dec 11, 2014 at 2:04 PM, Scott Lowe <scott.lowe at scottlowe.org>
wrote:

> Policy routing can help with this issue. I wrote a post about it a while
> ago. I'm sitting on a plane and therefore can't paste the link directly,
> but do a Google search for "policy routing site:scottlowe.org" and see
> what comes up.
>
> Good luck!
>
> --
> Scott
>
> Sent from my mobile device
>
> > On Dec 11, 2014, at 4:59 PM, Raymundo Vega <rvega at sansay.com> wrote:
> >
> > Hi all,
> >
> > Apologies if this has come up before, but I were unable to find any
> useful info yet.
> >
> > Problem can be summarized like this. Two networks with IP addresses from
> RFC1918 need
> > to be connected to a single Linux host, it is very possible that there
> is IP overlapping on the
> > two networks, i tried using 821q kernel module and configured two vlans
> with one interface in
> > each vlan, delivery always use first route in routing table, so kernel
> does not honor vlan tag.
> >
> > I'm not sure if OVS can help in this scenario, if anyone have info that
> may help (or pointers)
> > that can be shared, please let me know.
> >
> > Thanks in advance
> >
> > raymundo
> > _______________________________________________
> > discuss mailing list
> > discuss at openvswitch.org
> > http://openvswitch.org/mailman/listinfo/discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20141223/cafa739e/attachment-0002.html>