just an update on my networking fun from lastnight, indeed going from etherstub to phy is what caused the reordering of interfaces

if i run zonecfg export the wrong ordering is shown, for some reason if the nictag changes it dirtys all of the vnics assigned to zones so they are appended the next time vmadmd updates (on boot I suppose?)

aha

Reinhilde: do you know how dhcpagent works? I have a joyent branded zone that is being a bit picky about DHCP addresses

I don't. Treat me like the 8 year old you invited to the data centre because she wanted to see the blinkenlights, although by saying that I substantially undersell my technical competences.

I packet captured the machine and the client is saying "hey give me address X" which belongs to the wrong subnet, the dhcp server is refusing to respond to such a rude request so the zone assigns itself the address it wasn't issued

who makes leases persistent between boots? not even windows does this

I don't think I've ever had to configure that program.

you have, it's indirectly used by ifconfig/ipadm

right.

I (on OmniOS, so it's not the same) statically configured my IPv4 addresses. I don't know if my VM host didn't have DHCP or if I just couldn't finaggle 8/dhcpagent into working.

you're probably missing if the allow_ip_spoofing flag assuming the DHCP server lives outside

thanks for the tip. I hope your joyent zone gets its head into gear.

what kind of wrong subnet? 169.x.x.x?

thetooth: I'll be able to help in about an hour-ish.

thetooth: Set VERIFIED_LEASE_ONLY=yes in /etc/default/dhcpagent and it'll discard the current lease if the server doesn't respond.

Or you can delete /etc/dhcp/<interface>.dhc and restart the agent.

interesting.... CacheGrande ! thenewstack.io/cachegrand-a-fast-sc…store-for-data-oriented-development