[ovs-discuss] Not able to ping the OVS from a remote host
jhon.masschelein at surfsara.nl
Mon Oct 6 06:49:35 UTC 2014
To answer my own question:
I was assuming (yup, bad idea) that the "dummy" controller that comes with OVS was smart enough to do some low-level flow control.
Alas, I learned I really need to set up a controller in order to get non-local routing.
Information assimilated, problem solved.
On 3 okt. 2014, at 14:32, Jhon Masschelein <jhon.masschelein at surfsara.nl> wrote:
> I am new to OVS and with everything I found, I cannot get (what I consider) a simple setup to work:
> - I create an OVS on a host, setting an IP on the default internal interface
> - I can now ping from this host to any other host on that subnet
> - But I cannot ping to the OVS interface from any remote host
> Am I missing something?
> I am starting from a situation where em1 on each host is configured with an 192.168.12.XXX address and both hosts are able to ping each other.
> Next on host 1 I do:
> ip a del 192.168.12.10 dev em1
> ip link set em1 down
> ovs-vsctl add-br br0
> ovs-vsctl add-port br0 em1
> ip link set em1 up
> ip a add 192.168.12.10/24 dev br0
> ip link set onebr up
> ovs-vsctl show
> Bridge onebr
> Port "em1"
> Interface "em1"
> Port br0
> Interface br0
> type: internal
> ovs_version: "2.3.0"
> ping from host 1 to 192.168.12.11 works
> ping from 192.168.12.11 to host 1 gives "Destination unreachable"
> Standard ipforwarding is on:
> sysctl net.ipv4.ip_forward
> net.ipv4.ip_forward = 1
> Setting the br0 device UP creates an ip route as expected.
> The only strange think I notice is that the br0 device never goes to RUNNING state, it goes from DOWN to UNKNOWN and stays there.
> But from what I was able to find, that should not neccesarily be an issue?
> Any advise?
> discuss mailing list
> discuss at openvswitch.org
More information about the discuss