Re: [ovs-discuss] Issue with OVS Patch port

2017-12-13 Thread Ben Pfaff
On Wed, Dec 13, 2017 at 09:24:49PM -0500, Vasu S wrote:
> I'm trying to connect two OVS bridges via patch ports, however, as soon as
> I add the ports as type=patch, they disappear from the ifconfig and I'm
> unable to check any traffic hits on either of the patch interfaces. 

Patch ports aren't real interfaces and will not appear in ifconfig.

> Of course, I'm not able to get the ping going with the patched
> interfaces Only one OVS amongst the two is connected to the outside
> network via GRE tunnel.
> 
> Topology roughly looks like as the attached document.
> 
> Problem: Unable to ping VM1 from VM2
> Expected route: VM2->ovsbr-ext->GRE Tunnel->ovsbr1->patchlink->ovsbr2->VM1.
> 
> Patch config on the bridges ovsbr1 and ovsbr2 are as follows:

I suggest tracing the path of a packet.  The FAQ has some suggestions
for how to do this.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


Re: [ovs-discuss] Issue with OVS Patch port

2017-12-13 Thread Shivaram Mysore
The phrase is "patch port" and not "patch bridge"

I have said enough!

/Shivaram
::Sent from my mobile device::

> On Dec 13, 2017, at 6:24 PM, Vasu S  wrote:
> 
> Hi All, 
> 
> I'm trying to connect two OVS bridges via patch ports, however, as soon as I 
> add the ports as type=patch, they disappear from the ifconfig and I'm unable 
> to check any traffic hits on either of the patch interfaces. Of course, I'm 
> not able to get the ping going with the patched interfaces Only one OVS 
> amongst the two is connected to the outside network via GRE tunnel. 
> 
> Topology roughly looks like as the attached document. 
> 
> Problem: Unable to ping VM1 from VM2 
> Expected route: VM2->ovsbr-ext->GRE Tunnel->ovsbr1->patchlink->ovsbr2->VM1. 
> 
> Patch config on the bridges ovsbr1 and ovsbr2 are as follows:
> 
> ovs-vsctl add-port ovsbr1 port1 
> ovs-vsctl add-port ovsbr2 port2
> 
> ovs-vsctl set interface port1 type=patch
> ovs-vsctl set interface port2 type=patch
> 
> ovs-vsctl set interface port1 options:peer=port2 
> ovs-vsctl set interface port2 options:peer=port1 
> 
> 
> OpenVSwitch version on physical host 1 : 2.0.2
> OPenVSwitch version on physical host 2 : 2.5.2
> 
> Any help or pointers would be appreciated. 
> 
> -regards, 
>  Vasu. 
> 
>  
> 
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


[ovs-discuss] Issue with OVS Patch port

2017-12-13 Thread Vasu S
Hi All,

I'm trying to connect two OVS bridges via patch ports, however, as soon as
I add the ports as type=patch, they disappear from the ifconfig and I'm
unable to check any traffic hits on either of the patch interfaces. Of
course, I'm not able to get the ping going with the patched interfaces Only
one OVS amongst the two is connected to the outside network via GRE tunnel.

Topology roughly looks like as the attached document.

Problem: Unable to ping VM1 from VM2
Expected route: VM2->ovsbr-ext->GRE Tunnel->ovsbr1->patchlink->ovsbr2->VM1.

Patch config on the bridges ovsbr1 and ovsbr2 are as follows:

ovs-vsctl add-port ovsbr1 port1
ovs-vsctl add-port ovsbr2 port2

ovs-vsctl set interface port1 type=patch
ovs-vsctl set interface port2 type=patch

ovs-vsctl set interface port1 options:peer=port2
ovs-vsctl set interface port2 options:peer=port1


OpenVSwitch version on physical host 1 : 2.0.2
OPenVSwitch version on physical host 2 : 2.5.2

Any help or pointers would be appreciated.

-regards,
 Vasu.


topology.pdf
Description: Adobe PDF document
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss