Another similar question:
p0: type=internal, tag=100, vlan_mode=access, ip=192.168.1.100/24, br0,
namespace ns0
p1: type=internal, tag=100, vlan_mode=access, ip=192.168.1.200/24, br0,
namespace ns1
p2: type=internal, vlan_mode=trunk, trunks=100,200, br0
use tool scapy send ARP pkt from p2:
<Ether dst=ff:ff:ff:ff:ff:ff src=0a:c0:6e:45:5f:8a type=n_802_1Q |<Dot1Q
vlan=100 type=ARP |<ARP op=who-has hwsrc=0a:c0:6e:45:5f:8a psrc=192.168.1.1
pdst=192.168.1.100 |>
If I send one packet a time with sendp(pkt, "p2"), then I can receive the ARP
reply(use tcpdump in p0, and the pkt does not have vlan tag)
but if I send packet repeatedly with sendp(pkt, 1,1,"p2"), then no ARP reply
can be received(tcpdump in p0 shows that the pkt still have vlan tag 100)
use ovs-dpctl dump-flows, the above 2 steps displays the same flow:
recirc_id(0),skb_priority(0),in_port(2),eth(src=0a:c0:6e:45:5f:8a,dst=ff:ff:ff:ff:ff:ff),eth_type(0x8100),vlan(vid=100,pcp=0),encap(eth_type(0x0806),arp(sip=192.168.1.1/255.255.255.255,tip=192.168.1.100/255.255.255.255,op=1/0xff,sha=0a:c0:6e:45:5f:8a/00:00:00:00:00:00,tha=00:00:00:00:00:00/00:00:00:00:00:00)),
packets:21, bytes:966, used:0.080s,
actions:pop_vlan,4,push_vlan(vid=100,pcp=0),1,pop_vlan,3
port 0: ovs-system (internal)
port 1: br0 (internal)
port 2: p2 (internal)
port 3: p1 (internal)
port 4: p0 (internal)
you see, pop_vlan action is applied to port p0, but why when I send repeated
packet, the vlan tag can not be removed?
my ovs version is 2.3.0, and linux kernel version is 3.14.9
At 2014-09-22 20:06:50, "ychen" <ychen103...@163.com> wrote:
HI,
I found that internal port and netdev port can not ping each other, can you
tell me why?
The topology is like this:
p0: type=internal, tag=100, vlan_mode=access, ip=192.168.1.100/24, br0,
namespace ns0
eth0: type=netndev, tag=100, vlan_mode=access, ip=192.168.1.1/24, br0
then from netns ns0 port p0 ping 192.168.1.1, I can see that eth0 received
the arp packet with tcpdump, but no arp reply from eth0
but if I add port p2 (internal access port, tag=100, ip=192.168.1.2/24), then
down/up eth0
after the above step, we can ping from p0 to eth0.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
