More information: Even thought it appears that the dhcp namespace has
the ip/MAC mappings in arp, is still doesn't respond to arps:
# ip netns exec qdhcp-af224f3f-8de6-4e0d-b043-6bcd5cb014c5 arp
Address HWtype HWaddress Flags MaskIface
192.168.252.3
can you try using -e with tcpdump to see the ethernet headers - it may be arps
from the router to ff:ff:ff:ff:ff:ff that are not getting across in that
direction. You should continue tcpdumping on the devices along the path to the
instance to see where the arp request (or reply) stops. You do
Well, the subject is A Grizzly apring failure. So I'm using Grizzly
:) Sorry, bad joke. I have a multi-node setup on Raring, with a
3-nic network node (public, management, vm config nets) using OVS and
GRE encapsulation. It looks like this:
In my setup I see the arp replies being answered by the instance - not dnsmasq.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
Arg, of course the arp replies come from the instance. See? I'm
easily confused.
Here's more, using tcpdump -e. So if I ping the floater (10.21.166.2
- 192.168.252.3) ) from the outside (10.21.164.10), I see this on the
tenant router's external port:
16:16:30.771776 00:22:19:65:ae:42
5 matches
Mail list logo
