Ask Your Question

Revision history [back]

A quick look at https://visibilityspots.org/vlan-flat-neutron-provider.html
Clearly demonstrate, that all tricks related with "core fix"
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.simple.html
are completely needless in case when vlan enabled bridges are configured properly.

UPDATE 05/10/2016
What exactly I meant OVS vlan enabled bridge br-salida is not supposed to have IP at all
as underlying vlan enabled device http://www.cyberciti.biz/tips/howto-configure-linux-virtual-local-area-network-vlan.html

yum -y install epel-release
yum -y install vconfig

# ovs-vsctl add-br br-salida
# ovs-vsctl add-port br-salida em1
# vconfig add br-salida 90

Under /etc/sysconfig/network-scripts

# cat ifcfg-em1
DEVICE="em1"
ONBOOT=yes
OVS_BRIDGE=br-salida
TYPE=OVSPort
DEVICETYPE="ovs"

# cat ifcfg-br-salida
DEVICE=br-salida
BOOTPROTO=none
ONBOOT=yes
TYPE=OVSBridge
DEVICETYPE="ovs"

# cat ifcfg-br-salida.90
BOOTPROTO="none"
DEVICE="br-salida.90"
ONBOOT="yes"
IPADDR="192.168.90.14"
PREFIX="24"
GATEWAY="192.168.90.1"
DNS1="8.8.8.8"
VLAN=yes
NOZEROCONF=yes
USERCTL=no

Then run script :-

#!/bin/bash -x
chkconfig network on
systemctl stop NetworkManager
systemctl disable NetworkManager
service network restart

END UPDATE
A quick look at https://visibilityspots.org/vlan-flat-neutron-provider.html
Clearly demonstrate, that all tricks related with "core fix"
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.simple.html
are completely needless in case when vlan enabled bridges are configured properly.

UPDATE 05/10/2016
What exactly I meant OVS vlan enabled bridge br-salida is not supposed to have IP at all
as underlying parent vlan enabled device http://www.cyberciti.biz/tips/howto-configure-linux-virtual-local-area-network-vlan.htmlhttps://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html

yum -y install epel-release
yum -y install vconfig

# ovs-vsctl add-br br-salida
# ovs-vsctl add-port br-salida em1
# vconfig add br-salida 90

Under /etc/sysconfig/network-scripts

# cat ifcfg-em1
DEVICE="em1"
ONBOOT=yes
OVS_BRIDGE=br-salida
TYPE=OVSPort
DEVICETYPE="ovs"

# cat ifcfg-br-salida
DEVICE=br-salida
BOOTPROTO=none
ONBOOT=yes
TYPE=OVSBridge
DEVICETYPE="ovs"

# cat ifcfg-br-salida.90
BOOTPROTO="none"
DEVICE="br-salida.90"
ONBOOT="yes"
IPADDR="192.168.90.14"
PREFIX="24"
GATEWAY="192.168.90.1"
DNS1="8.8.8.8"
VLAN=yes
NOZEROCONF=yes
USERCTL=no

Then run script :-

#!/bin/bash -x
chkconfig network on
systemctl stop NetworkManager
systemctl disable NetworkManager
service network restart

END UPDATE
A quick look at https://visibilityspots.org/vlan-flat-neutron-provider.html
Clearly demonstrate, that all tricks related with "core fix"
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.simple.html
are completely needless in case when vlan enabled bridges are configured properly.

UPDATE 05/12/2016
@Sacha_m wrote :-

Now both IP are responding. This changes are not persistent. To make them persistent, we have to do this. What means that he did a trick and both IPs 192.168.70.14 && 192.168.90.14 are responding now

Here I am loosing a point . Per ovs-ofctl dump-flows br-salida requested by Andrew Shvartz bridge br-salida became VLAN enabled after reboot and makes egress traffic vlan tagged (90).Then it should not be able any more to work as external bridge for flat network . How 192.168.70.14 can respond after conversion been done if ingress traffic is untagged. Please, clarify this moment. Via my experience if first external network is flat (vxlan) and second is vlan tagged I need two physical NICs . NIC1 supporting external flat network, NIC2 supporting external vlan network and NIC0 ( third ) for MGMT network ( em2 interface). I believe that both IPs may respond only if ingress traffic is vlan tagged 90.

END UPDATE

UPDATE 05/10/2016
What exactly I meant OVS vlan enabled bridge br-salida is not supposed to have IP at all
as parent vlan enabled device https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html

yum -y install epel-release
yum -y install vconfig

# ovs-vsctl add-br br-salida
# ovs-vsctl add-port br-salida em1
# vconfig add br-salida 90

Under /etc/sysconfig/network-scripts

# cat ifcfg-em1
DEVICE="em1"
ONBOOT=yes
OVS_BRIDGE=br-salida
TYPE=OVSPort
DEVICETYPE="ovs"

# cat ifcfg-br-salida
DEVICE=br-salida
BOOTPROTO=none
ONBOOT=yes
TYPE=OVSBridge
DEVICETYPE="ovs"

# cat ifcfg-br-salida.90
BOOTPROTO="none"
DEVICE="br-salida.90"
ONBOOT="yes"
IPADDR="192.168.90.14"
PREFIX="24"
GATEWAY="192.168.90.1"
DNS1="8.8.8.8"
VLAN=yes
NOZEROCONF=yes
USERCTL=no

Then run script :-

#!/bin/bash -x
chkconfig network on
systemctl stop NetworkManager
systemctl disable NetworkManager
service network restart

END UPDATE
A quick look at https://visibilityspots.org/vlan-flat-neutron-provider.html
Clearly demonstrate, that all tricks related with "core fix"
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.simple.html
are completely needless in case when vlan enabled bridges are configured properly.

UPDATE 05/12/2016
@Sacha_m @sacha-m wrote :-

Now both IP are responding. This changes are not persistent. To make them persistent, we have to do this. What means that he did a trick and both IPs 192.168.70.14 && 192.168.90.14 are responding now

Here I am loosing a point . Per ovs-ofctl dump-flows br-salida requested by Andrew Shvartz bridge br-salida became VLAN enabled after reboot and makes egress traffic vlan tagged (90).Then it should not be able any more to work as external bridge for flat network . How 192.168.70.14 can respond after conversion been done if ingress traffic is untagged. Please, clarify this moment. Via my experience if first external network is flat (vxlan) and second is vlan tagged I need two physical NICs . NIC1 supporting external flat network, NIC2 supporting external vlan network and NIC0 ( third ) for MGMT network ( em2 interface). I believe that both IPs may respond only if ingress traffic is vlan tagged 90.

END UPDATE

UPDATE 05/10/2016
What exactly I meant OVS vlan enabled bridge br-salida is not supposed to have IP at all
as parent vlan enabled device https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html

yum -y install epel-release
yum -y install vconfig

# ovs-vsctl add-br br-salida
# ovs-vsctl add-port br-salida em1
# vconfig add br-salida 90

Under /etc/sysconfig/network-scripts

# cat ifcfg-em1
DEVICE="em1"
ONBOOT=yes
OVS_BRIDGE=br-salida
TYPE=OVSPort
DEVICETYPE="ovs"

# cat ifcfg-br-salida
DEVICE=br-salida
BOOTPROTO=none
ONBOOT=yes
TYPE=OVSBridge
DEVICETYPE="ovs"

# cat ifcfg-br-salida.90
BOOTPROTO="none"
DEVICE="br-salida.90"
ONBOOT="yes"
IPADDR="192.168.90.14"
PREFIX="24"
GATEWAY="192.168.90.1"
DNS1="8.8.8.8"
VLAN=yes
NOZEROCONF=yes
USERCTL=no

Then run script :-

#!/bin/bash -x
chkconfig network on
systemctl stop NetworkManager
systemctl disable NetworkManager
service network restart

END UPDATE
A quick look at https://visibilityspots.org/vlan-flat-neutron-provider.html
Clearly demonstrate, that all tricks related with "core fix"
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.simple.html
are completely needless in case when vlan enabled bridges are configured properly.