On 12 March 2015 at 05:33, Fredy Neeser fredy.nee...@solnet.ch wrote:
2. I'm using policy routing on my hosts to steer VXLAN traffic (UDP
dest. port 4789) to interface br-ex.12 -- all other traffic from
192.168.1.14 is source routed from br-ex.1, presumably because br-ex.1 is a
On 11.03.2015 19:31, Ian Wells wrote:
On 11 March 2015 at 04:27, Fredy Neeser fredy.nee...@solnet.ch
mailto:fredy.nee...@solnet.ch wrote:
7: br-ex.1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
noqueue state UNKNOWN group default
link/ether e0:3f:49:b4:7c:a7 brd
On 11 March 2015 at 04:27, Fredy Neeser fredy.nee...@solnet.ch wrote:
7: br-ex.1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state
UNKNOWN group default
link/ether e0:3f:49:b4:7c:a7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.14/24 brd 192.168.1.255 scope global br-ex.1
- Original Message -
From: Fredy Neeser fredy.nee...@solnet.ch
To: openstack-dev@lists.openstack.org
Sent: Friday, March 6, 2015 6:01:08 PM
Subject: [openstack-dev] [neutron] VXLAN with single-NIC compute nodes:
Avoiding the MTU pitfalls
Hello world
I recently created a VXLAN test setup
To: openstack-dev@lists.openstack.org
Sent: Friday, March 6, 2015 6:01:08 PM
Subject: [openstack-dev] [neutron] VXLAN with single-NIC compute nodes:
Avoiding the MTU pitfalls
Hello world
I recently created a VXLAN test setup with single-NIC compute nodes
(using OpenStack Juno on Fedora 20
Hello world
I recently created a VXLAN test setup with single-NIC compute nodes
(using OpenStack Juno on Fedora 20), conciously ignoring the OpenStack
advice of using nodes with at least 2 NICs ;-) .
The fact that both native and encapsulated traffic needs to pass through
the same NIC does
with single-NIC compute nodes:
Avoiding the MTU pitfalls
Hello world
I recently created a VXLAN test setup with single-NIC compute nodes
(using OpenStack Juno on Fedora 20), conciously ignoring the OpenStack
advice of using nodes with at least 2 NICs ;-) .
The fact that both native
