OS-8279: Link-local default route support in LX zones


Issue Type:Bug
Priority:4 - Normal
Created at:2021-04-01T00:09:01.614Z
Updated at:2021-04-02T20:26:39.255Z


Created by:Dan McDonald
Reported by:Dan McDonald
Assigned to:Dan McDonald


Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2021-04-02T20:26:39.247Z)

Fix Versions

2021-04-08 obviously you are not a golfer (Release Date: 2021-04-08)

Related Links


Reflects illumos-joyent issue 356, and PR 360.


Comment by Dan McDonald
Created at 2021-04-01T18:12:40.578Z

The contributor has made the following high-level changes in LX route establishment:

The PR https://github.com/joyent/illumos-joyent/pull/360 has additional details.  The testing details are in there as well, but copied here for posterity:

Some testing notes:

I have a few nodes at OVH that use "failover" ip addresses. These addresses are handed out on a CIDR subnet different than the admin network. The default route, however, is that of the default network. So a link-local route needs to be created before the default route. That's the rationale for this change.

I've been using this patch on 10-15 native zones across multiple hosts for the past year. These zones require the link local route to be created first as the default route is on the link-local network (that isn't the same as the IP address of the interface.) Without the patch, creating the default route fails with a "no route to host" error (and the zone provisioning fails after a time), but is successful with the patch.

I've also been running platform images with this fix on multiple systems that don't have static routes at all, and these all work as expected with the the patch.

Additionally, on a dummy test system, I created a simnet device and assigned a nic tag to that. I then created a series of zones using vmadm with 2 nics each and the following combinations of routes:

These all seemed to work just fine, in that: