<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV> </DIV>
<DIV>>> On Sep 28, 2017, at 8:50 AM, O Alabeatrix
<oalabeatrix@gmail.com>> wrote:</DIV>
<DIV>>> </DIV>
<DIV>>> Hi</DIV>
<DIV>>> </DIV>
<DIV>>> I’m a network admin starting to learn Open vSwitch. I don’t manage
to make it functionning.</DIV>
<DIV>>> I’m using Debian 9 with three physical interfaces:</DIV>
<DIV>>> . enp0s3: management interfaces</DIV>
<DIV>>> . enp0s8: physical interface on vswitch0</DIV>
<DIV>>> . enp0s9: physical interface on vswitch1</DIV>
<DIV>>> </DIV>
<DIV>>> vswitch0 (LOCALE) IP: 192.168.1.200</DIV>
<DIV>>> </DIV>
<DIV>>> Theorically, as there is an IP on vswitch0, it shouldn’t matter
wether it’s enp0s8 or enp0s9 that is plugged into the 192.168.1.0/24
network.</DIV>
<DIV>>> Alas, it’s only when enp0s9 is used that the ping to the outter
physical IP succeed.</DIV>
<DIV>>> An both in default L2 and OpenFlow3 mode.</DIV>
<DIV>>> </DIV>
<DIV>>> Here are the config and status files:</DIV>
<DIV>>> </DIV>
<DIV>>> Debian9 config:</DIV>
<DIV>>> </DIV>
<DIV>>> sudo apt-get update</DIV>
<DIV>>> sudo apt-get dist-upgrade</DIV>
<DIV>>> sudo apt-get install openvswitch-switch openvswitch-common</DIV>
<DIV>>> sudo ovs-vsctl add-br vswitch0</DIV>
<DIV>>> sudo ip link set vswitch0 up</DIV>
<DIV>>> sudo ip addr flush dev enp0s8</DIV>
<DIV>>> sudo ip addr flush dev enp0s9</DIV>
<DIV>>> sudo ovs-vsctl add-port vswitch0 enp0s8</DIV>
<DIV>>> sudo ovs-vsctl add-port vswitch0 enp0s9</DIV>
<DIV>>> sudo ip link set enp0s8 up</DIV>
<DIV>>> sudo ip link set enp0s9 up</DIV>
<DIV>>> sudo ip addr add 192.168.1.200/24 dev vswitch0</DIV>
<DIV>>> </DIV>
<DIV>>> Normal default L2 Test:</DIV>
<DIV>>> </DIV>
<DIV>>> ping -c 3 192.168.1.1 --->> Fails, unless I swap the
interfaces used</DIV>
<DIV>>> </DIV>
<DIV>>> Status:</DIV>
<DIV>>> </DIV>
<DIV>>> sudo ovs-vsctl show</DIV>
<DIV>>> bf88303a-48cb-48b6-bd07-af1b8eaaca89</DIV>
<DIV>>> Bridge "vswitch0"</DIV>
<DIV>>> Port
"enp0s9"</DIV>
<DIV>>>
Interface "enp0s9"</DIV>
<DIV>>> Port
"vswitch0"</DIV>
<DIV>>>
Interface "vswitch0"</DIV>
<DIV>>>
type: internal</DIV>
<DIV>>> Port
"enp0s8"</DIV>
<DIV>>>
Interface "enp0s8"</DIV>
<DIV>>> ovs_version: "2.6.2"</DIV>
<DIV>>> </DIV>
<DIV>>> --</DIV>
<DIV>>> sudo ovs-ofctl show vswitch0</DIV>
<DIV>>> OFPT_FEATURES_REPLY (xid=0x2): dpid:0000080027c5c636</DIV>
<DIV>>> n_tables:254, n_buffers:256</DIV>
<DIV>>> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS
ARP_MATCH_IP</DIV>
<DIV>>> actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan
mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src
mod_tp_dst</DIV>
<DIV>>> 1(enp0s8): addr:08:00:27:f4:a5:b9</DIV>
<DIV>>> config:
0</DIV>
<DIV>>> state:
0</DIV>
<DIV>>> current: 1GB-FD
COPPER AUTO_NEG</DIV>
<DIV>>> advertised: 10MB-HD 10MB-FD 100MB-HD
100MB-FD 1GB-FD COPPER AUTO_NEG</DIV>
<DIV>>> supported: 10MB-HD 10MB-FD
100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG</DIV>
<DIV>>> speed: 1000 Mbps now, 1000 Mbps
max</DIV>
<DIV>>> 2(enp0s9): addr:08:00:27:c5:c6:36</DIV>
<DIV>>> config:
0</DIV>
<DIV>>> state:
0</DIV>
<DIV>>> current: 1GB-FD
COPPER AUTO_NEG</DIV>
<DIV>>> advertised: 10MB-HD 10MB-FD 100MB-HD
100MB-FD 1GB-FD COPPER AUTO_NEG</DIV>
<DIV>>> supported: 10MB-HD 10MB-FD
100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG</DIV>
<DIV>>> speed: 1000 Mbps now, 1000 Mbps
max</DIV>
<DIV>>> LOCAL(vswitch0): addr:08:00:27:c5:c6:36</DIV>
<DIV>>> config:
0</DIV>
<DIV>>> state:
0</DIV>
<DIV>>> speed: 0 Mbps now, 0 Mbps max</DIV>
<DIV>>> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal
miss_send_len=0</DIV>
<DIV>>> --</DIV>
<DIV>>> sudo ovs-ofctl dump-flows vswitch0</DIV>
<DIV>>> NXST_FLOW reply (xid=0x4):</DIV>
<DIV>>> cookie=0x0, duration=686.922s, table=0, n_packets=224,
n_bytes=28746, idle_age=1, priority=0 actions=NORMAL</DIV>
<DIV>>> ----</DIV>
<DIV>>> </DIV>
<DIV>>> OpenFlow3 mode and tests:</DIV>
<DIV>>> </DIV>
<DIV>>> sudo ovs-vsctl set bridge vswitch0 protocols=OpenFlow13</DIV>
<DIV>>> sudo ovs-ofctl -O Openflow13 dump-flows vswitch0</DIV>
<DIV>>> </DIV>
<DIV>>> OFPST_FLOW reply (OF1.3) (xid=0x2):</DIV>
<DIV>>> cookie=0x0, duration=1334.814s, table=0, n_packets=398,
n_bytes=66282, priority=0 actions=NORMAL</DIV>
<DIV>>> </DIV>
<DIV>>> ping 192.168.1.1 –>> Fail ( functions if I swap the
interfaces cables)</DIV>
<DIV>>> </DIV>
<DIV>>> I just can’t figure out what is going wrong here, even after
compairing the status files ( ip link show, ip addr show).</DIV>
<DIV>>> thanks for any help <wlEmoticon-smile[1].png></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>>In this instance, I think it's appropriate to ask about the upstream
switch configuration. I don't see anything immediately odd about your
>configuration, so we'll need to determine how OVS is interacting with the
upstream physical switch (things like VLANs, tagging, etc.).</DIV>
<DIV> </DIV>
<DIV>>Also, since you have 2 NICs added to the OVS bridge and don't appear to
be connected to an OpenFlow controller, you'll need to address bridging
>loops and Spanning Tree. Specifically, you'll want to either a) place the
physical interfaces in different broadcast domains, or b) use some form >of
link aggregation.</DIV>
<DIV>></DIV>
<DIV>>--</DIV>
<DIV>>Scott</DIV>
<DIV> </DIV>
<DIV>Only 1 NIC is plugged int the 192.168.1.0/24 L2 domain at a time, so there
is no STP/bridging loop involved.</DIV>
<DIV>The other cable is always plugged in another L2 domain:</DIV>
<DIV> </DIV>
<DIV>Actually, the Debian 9 Open vSwitch is a VirtualBox VM.</DIV>
<DIV>enp0S8 is bridged on the physical network</DIV>
<DIV>enp0s9 is on another plane (inet)</DIV>
<DIV> </DIV>
<DIV>I’ll investigate your suggestion pointing to a weird interaction between
Open vSwitch and VirtualBox networking.</DIV>
<DIV>But if one cable is plugged into ‘nowhere land’ (inet), that shouldn’t
prevent the Open vSwitch from trying to use the other port, sending ARP request,
...</DIV>
<DIV>I’ll add that I’m very skilled with Virtualized networking so .. hum ..
this is intriguing ...</DIV>
<DIV>Thanks for having checked my config files and giving me an input. It’s my
first steps with Open vSwitch, I’m a real rookie over this subject</DIV>
<DIV>I go back wiresharking all this <IMG class="wlEmoticon wlEmoticon-smile"
style="BORDER-TOP-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none; BORDER-RIGHT-STYLE: none"
alt=Sourire src="cid:9DA1353CAC644264A61743A2FC1AFC78@ACERPC"></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></DIV><div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 18px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
<td style="width: 470px; padding-top: 17px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Garanti sans virus. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a> </td>
</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></BODY></HTML>