On Mar 2, 2013, at 2:29 PM, Martin Mailand wrote:
> Hi Kyle,
>
> I found the patch and applied it. So far so good, gre tunnel are still
> working, but I cannot get a vxlan tunnel to work.
>
> I tried the following command.
>
> ovs-vsctl add-port br-tun vx1 -- set interface vx1 type=vxlan
> opti
Hi Kyle,
I found the patch and applied it. So far so good, gre tunnel are still
working, but I cannot get a vxlan tunnel to work.
I tried the following command.
ovs-vsctl add-port br-tun vx1 -- set interface vx1 type=vxlan
options:remote_ip=192.168.194.1
I get this error.
2013-03-02T20:10:40Z|
On Fri, Mar 1, 2013 at 3:27 PM, krishna kumar wrote:
> No, 108.x.x.x is the access point in my home. The 198.168.x.x is the subnet
> to which the VM is attached. OVS is running in the VM.
> The GRE packet arriving at 108.x.x.x cannot reach OVS in 192.168.x.x unless
> forwarded using DNAT.
> The ro
I recently began using OVS with KVM on CentOS 6.3 and ran into an
irritating issue. It appears that, on host machine startup, the custom
ifup-ovs script is prematurely calling ifconfig to assign the IP address
that is specified in the appropriate ifcfg file. I experienced this
problem with both f
