© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
@Michael
In this environment, -A and -U look the same:
ip netns exec qrouter-
ARPING 172.29.77.57
Timeout
--- 172.29.77.57 statistics ---
1 packets transmitted, 0 packets received, 100% unanswered (0 extra)
20:59:55.376150 fa:16:3e:82:94:ef > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 103, p 0, ethertype ARP, Request who-has 172.29.77.57 tell 172.29.77.22, length 28
root@543232-
ARPING 172.29.77.57
Timeout
--- 172.29.77.57 statistics ---
1 packets transmitted, 0 packets received, 100% unanswered (0 extra)
21:00:55.460283 fa:16:3e:82:94:ef > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 103, p 0, ethertype ARP, Request who-has 172.29.77.57 (ff:ff:ff:ff:ff:ff) tell 172.29.77.22, length 28
Both send a broadcast and are originating from the primary interface IP. It looks like the code supports both -U and -A, and may execute both. I think the issue is that the address on the interface is a /32 address and normally wouldn't be used for locally-originated outbound traffic.
According the man page, -s can be used to specify source MAC, and -S can be used to specify source IP. Using -S we can see traffic sourced from the floating IP:
root@543232-
ARPING 172.29.77.57
Timeout
--- 172.29.77.57 statistics ---
1 packets transmitted, 0 packets received, 100% unanswered (0 extra)
21:04:01.728458 fa:16:3e:82:94:ef > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 103, p 0, ethertype ARP, Request who-has 172.29.77.57 (ff:ff:ff:ff:ff:ff) tell 172.29.77.57, length 28
----------
@Brian - Yes, this is non-DVR.
>> I do see the source IP same as the destination IP.
Perhaps floating IPs are implemented differently in fip namespaces vs qrouter namespaces? I don't have an OVS environment handy to find out.