If using virtual machines, always make sure the interface in the VM
settings is set to promiscuous mode. Had many issues of packets getting
dropped because of this.
Greg
On 16/07/2014 7:05 AM, ?? wrote:
Just did a tcpdump on eth1 of host A, the PPPoE discovery packet was
actually successfully sent to interface eth1, but unfortunately I got
no response from PPPoE server.
Host A is actually a virtual machine, I'm not sure whether it's the
root cause of the problem.
On Wed, Jul 16, 2014 at 6:37 PM, ?? <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
I'm trying to setup ovs as an ethernet tunnel, so I can dial into
a private network across the Internet.
I have 2 linux hosts A, B, both running openvswitch 2.1.2,
configured with kernel support. Host A is the host which I can
dial directly into the private network. Host A has two network
adapters, eth0 & eth1, eth0 is connected to internet, eth1 is
connected to the PPPoE server. ovs setup on host A is like this:
Bridge "lan0"
Port "eth1"
Interface "eth1"
Port "lan0"
Interface "lan0"
type: internal
Port "vxlan0"
Interface "vxlan0"
type: vxlan
options: {remote_ip="host B"}
ovs setup on host B is like this:
Bridge "lan0"
Port "lan0"
Interface "lan0"
type: internal
Port "vxlan0"
Interface "vxlan0"
type: vxlan
options: {remote_ip="host A"}
With this setup, if I assign a static IP address on both "lan0"
interfaces, both A & B can ping each other, so the vxlan tunnel
probably works as expected.
I also managed to dial into private network through interface lan0
on host A, I cannot dial into the network through interface lan0
on host B.
Which part of my setup is wrong ? or openvswitch isn't designed to
do what I required ?
Thanks
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
