Eucalyptus instance IP has been a 0.0.0.0 solution

How to solve it.

When the instance is started, first use euca-describle-instances to view the state of the instance, and if it is still in the pending state, it will take a while to wait.

If you are in a running state. First go to the node where you start the instance, use Brctl show to see if there is any problem with the bridge, see this blog for details. Then log on to your route to see if the route has a DHCP service, or to provide a DHCP server machine to view the DHCP log. In a route, you can see whether DHCP has been assigned to the IP in the System state record. If your DHCP log says that you have already allocated IP. That is to use euca-describle-instances to check again. If the IP has not been assigned. Then log in to your head node and then ping the IP you just assigned. Then use the euca-describle-instances to see the IP.

If the IP under your route may conflict with the IP outside of your route, you can also unplug the interface between the router and the extranet to try.

But there's something weird about it. Routing DHCP is set to 8~252, which means that the address between 8 and 252 should be assigned. The resulting instances are all addresses that are less than 8. I don't know if I'm routing dhcp or where I set up the wrong.