[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-discuss
Subject:    [ovs-discuss] Behavior when ping "internal" bridge interface ip with dpdk port attached
From:       fan.du () intel ! com (Du, Fan)
Date:       2015-08-26 14:27:52
Message-ID: 55DDCCE8.30502 () intel ! com
[Download RAW message or body]

After creating a user space ovs bridge, and assign an valid ip address
after the "internal" bridge name, then add a physical interface, e.g. 
ens806f1 to the bridge. Ping the internal bridge ip address from the 
other host will work ok.

But once I prevent all the packets reaching ens806f1 by iptable rules,
Ping from the other host will not work. So my understanding is kernel
network stack responds to the ARP request, in which case bypass ovs user
space bridge.
iptables -A INPUT -i ens806f1 -j DROP
iptables -A FORWARD -i ens806f1 -j DROP

But when attaching a dpdk type port(instead of the physical interface
like ens806f1) to the bridge,I can tcpdump ARP_REPLY from the dummy
mirroring port, but the ARP_REPLY packet didn't reach from the other host.

So I'm puzzled, in scenario of dpdk port attached:
a. which part of code build the ARP_REPLY packet?
b. why the arp reply packet didn't hit on wire after setting arp with
    normal action flow?





[prev in list] [next in list] [prev in thread] [next in thread]