http://defect.opensolaris.org/bz/show_bug.cgi?id=12253
amaguire <alan.maguire at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan.maguire at sun.com
--- Comment #1 from amaguire <alan.maguire at sun.com> 2009-10-28 09:51:27 UTC
---
(In reply to comment #0)
> With the fix for 11866, it's now possible to associate a static route with an
> ip ncu. However, on upgrade, an existing /etc/defaultrouter file is ignored.
> It would be really nice if data contained in that file could be pulled into
> the
> nwam configuration.
>
> The only real problem with doing this is deciding which ncu the static route
> should be associated with. I think a reasonable algorithm would be to apply
> it
> to the ncu created for the first llp file entry which contains a static ip
> address that's on the same subnet as the defaultrouter value.
My only worry here is that this will solve some non-NWAM users problems and not
others. Consider users with no /etc/defaultrouter file, or anny route delivered
via the Router DHCP parameter - they likely obtain a route via IPv4 router
discovery done by network/route (in.routed), and initiated by
network/routing-setup.
My suggestion (and there may be problems with this approach, I seem to recall
we rejected it before) is to restart network/routing-setup if an IP NCU goes
online and no default route is set (either via the NCU ipv4(6)-default-route or
via DHCP). The routing-setup svc has no dependents, so the restart won't have
unwanted side-effects, and the routing-setup service already picks up routes
specified in /etc/defaultrouter, and if none is found, it'll start dynamic
routing. The only problem is that at present, it flushes already-set default
routes (which is why it likely causes problems for punchin). So with a few "is
NWAM running?" tweaks, I think we could solve this issue at runtime by
devolving the responsibility of gathering a usable route to
network/routing-setup.
There's a few things that need to be fixed in the script though:
1. we use the intial netstrategy to determine if /etc/defaultrouter is to be
read. We may need to tweak the logic here in the NWAM case.
2. we delete any default routes already present. We probably don't want to do
that in the NWAM case.
What do you think?
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
