Shulou(Shulou.com)06/02 Report--

Environment: openstack Q version, allinone,linuxbridge+vxlan

Phenomenon: virtual machine can get the address, but ping can not access the gateway and dhcp server

Because it is an allinone environment, the tap of the virtual machine is directly linked to the bridge, and the interface between the dhcp and the gateway is also directly linked to the bridge. According to reason, the virtual machine can directly access the dhcp and the gateway, but the virtual machine does not work. By grabbing the packet, it is found that the tap connecting the dhcp has no message, as if linuxbridge did not forward the message, there is no way to delete the vxlan interface from the bridge, and the virtual machine can ping, restart linuxbridge agent, and continue debugging. Found bridge fdb show vxlan-xx, there are two entries

{Gateway mac} dst 127.0.0.1 self

{dhcp server mac} dst 127.0.0.1 self

Remember that the local_ip of vxlan is configured with 127.0.0.1, which is changed to the physical address of the network port. Restart the physical machine test. There are no extra entries for bridge fdb show vxlan-xx, and the virtual machine can communicate with ping normally.

The suspect point is that although the gateway and the tap of dhcp and the tap of virtual machine are connected to the same bridge, because it is a vxlan network, the bridge forwards the vxlan interface for processing after receiving this message, and because dst is 127.0.0.1, an exception occurred in the access

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.