Christine Tran wrote: > On Mon, Jan 25, 2010 at 4:44 PM, James Carlson <carlsonj at workingcode.com> > wrote: > >> That said, have you tried using the "defrouter" property in zonecfg? I >> thought it was designed for just this case. (Or is the problem that you >> need multiple network routes per zone?) > > I needed a couple of different static network routes per zone, and we > are not using active routing so we don't have a way to get route > information and metrics.
Have you filed an RFE for whatever it is you're trying to do? > This box is also mobile, so the networking information can be expected > to change. I think the easiest, if not the most elegant way is to > wait for zones to boot and then re-run route-setup. Actually, I think the temporary interface hack is the simpler solution in this case. Just create a custom service that creates those interfaces and configures the routes, and make the zones service dependent on that (instead of on routing-setup). This depends on a long-standing oddity in Solaris: once the static routes are in the kernel, the system doesn't really care if the interface they point to goes away, and it'll correctly associate the route with any viable interface when one is later created, but the system "helpfully" rejects routes that have a missing output interface when initially installed. Thus, lying to the system works. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
