jim Walker writes: > Dan McDonald wrote: > > > > I don't know how NWAM would interact with it, but if you use the "-p" option > > to route, things persist across boots. > > > > route -p add default <some-next-hop> > > > > Dan > > > I'm already doing that. Is there a race or something at boot time > that causes the default router to be lost? I see this on multiple > Sun servers running OpenSolaris.
"route -p" assumes that the next hop is reachable at boot time. NWAM configures interfaces later. If I had to guess, I'd say that's the problem you're seeing. It's entirely possible that the existing NWAM code just doesn't work right with static routes configured in the usual way. I don't think it was any part of the original design consideration. The next step would be to create an /etc/nwam/ulp/check-conditions script that invokes "route add" (without the -p) when necessary. -- James Carlson, Solaris Networking <[email protected]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
