Hi all,

I was wondering if anyone else had problems with gre, or capwap, tunnels over 
the loopback interface.  (We're doing some automated tests which test tunnels.) 
 What I'm seeing is that one packets gets through, and subsequent packets are 
dropped, somewhere before the gre_rcv is called.

Here's the setup: 

create 2 bridges:
ovs-vsctl add-br a
ovs-vsctl add-br b

create 2 tunnel ports, one on each bridge:
ovs-vsctl add-port a t1 -- set interface t1 type=capwap 
options:local_ip=127.0.0.1 options:remote_ip=127.0.0.2 options:key=12345
ovs-vsctl add-port b t2 -- set interface t2 type=capwap 
options:local_ip=127.0.0.2 options:remote_ip=127.0.0.1 options:key=12345

create 2 internal interfaces, one on each bridge
ovs-vsctl add-port a p1 -- set interface p1 type=internal
ovs-vsctl add-port b p2 -- set interface p2 type=internal
ip link set p1 up
ip link set p2 up

add a route to some network to via p1
ip route add 10.0.0.0/24 dev p1

add an arp entry so that the kernel doesn't arp
arp -s 10.0.0.1 00:11:22:33:44:55

send traffic into p1
ping 10.0.0.1


We can see the gre, or capwap udp, packets when doing tcpdump on lo, but 
gre_rcv, or capwap_rcv, is called just once, and packets don't make it into 
bridge b, nor are stats updated on the t2 interface.

Has anyone had this experience?

Cheers,
Dan

_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev

Reply via email to