arping Interface "lo" is not ARP

遇到一个比较奇怪的arp的问题

假设有3个pod

A 在A中telnet S的ip和端口不正常，定位发现是arp冲突，而代答是B代答的，但是B并没有这个IP
B 代答
S 实际IP所在pod

进入B中查看，该pod访问外网是正常的，但是arp的功能看起来有点问题

``` bash
bash-5.1# ip -d link show net1
2: net1@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether ba:88:56:df:49:9f brd ff:ff:ff:ff:ff:ff link-netnsid 0 promiscuity 0 minmtu 68 maxmtu 9600
    macvlan mode bridge addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
bash-5.1# ping 114.114.114.114
PING 114.114.114.114 (114.114.114.114) 56(84) bytes of data.
64 bytes from 114.114.114.114: icmp_seq=1 ttl=63 time=24.2 ms
64 bytes from 114.114.114.114: icmp_seq=2 ttl=65 time=23.6 ms
^C
--- 114.114.114.114 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 23.641/23.908/24.176/0.267 ms
bash-5.1# ping 10.122.193.70
PING 10.122.193.70 (10.122.193.70) 56(84) bytes of data.
64 bytes from 10.122.193.70: icmp_seq=1 ttl=64 time=0.019 ms
64 bytes from 10.122.193.70: icmp_seq=2 ttl=64 time=0.018 ms
^C
--- 10.122.193.70 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1048ms
rtt min/avg/max/mdev = 0.018/0.018/0.019/0.000 ms
bash-5.1# ping 10.122.193.73
PING 10.122.193.73 (10.122.193.73) 56(84) bytes of data.
64 bytes from 10.122.193.73: icmp_seq=1 ttl=64 time=0.018 ms
64 bytes from 10.122.193.73: icmp_seq=2 ttl=64 time=0.013 ms
^C
--- 10.122.193.73 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1030ms
rtt min/avg/max/mdev = 0.013/0.015/0.018/0.002 ms
bash-5.1# arping 10.122.193.73
Interface "lo" is not ARPable

bash-5.1# arping -I net1 10.122.193.73
ARPING 10.122.193.73 from 10.122.193.73 net1


# 重复确认下不是arp 关闭导致的，如果关闭了，其实公网应该都通不了
bash-5.1# ip link set dev net1 arp on
bash-5.1#
bash-5.1#
bash-5.1#
bash-5.1# arping -I net1 10.122.193.73
ARPING 10.122.193.73 from 10.122.193.73 net1



# 10.122.193.73  这里应该是这个ip在本地，所以会出现arp无应答的情况

而A的arping是正常的

[root@hci-ctrl-1 script]# kubectl  exec -it -n kube-system            vpc-nat-gw-yealink-europe-pod-7bc46795cb-7t47g -- bash
bash-5.1#  arping -I net1 10.122.193.73
ARPING 10.122.193.73 from 10.122.193.2 net1
Unicast reply from 10.122.193.73 [BA:73:72:65:86:F6]  0.588ms  # mac冲突
Unicast reply from 10.122.193.73 [BA:88:56:DF:49:9F]  0.601ms
Unicast reply from 10.122.193.73 [BA:88:56:DF:49:9F]  0.570ms
^CSent 2 probes (1 broadcast(s))
Received 3 response(s)
bash-5.1# ip -d link show net1
2: net1@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether 62:18:d9:75:29:45 brd ff:ff:ff:ff:ff:ff link-netnsid 0 promiscuity 0 minmtu 68 maxmtu 9600
    macvlan mode bridge addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535

重建B pod 后，mac代答的情况消失，应该还是mac代答的问题。 但是正常创建出来的pod 不会出现mac代答的情况，一般只在ip在本地网卡上时，才会响应arp