On 10/22/09 10:40, Sebastien Roy wrote:
> 11. Add default-route properties to IP Interface NCUs
> Two new properties, ipv4-default-route and ipv6-default-route, allow
> the user to specify statically configured default router address(es),
> to be associated with a specific interface. This provides a static
> alternative to a DHCP-specified default router, which may be associated
> with an interface if DHCP is in use.
>
alternative to the DHCP-specified default router (returned by dhcpinfo I
presume) or in addition to it, as a second default router?
> 17. Change upgrade behavior
> Upon upgrade, earlier nwam link and interface configuration will be
> imported into the User NCP. However, the Automatic NCP will be active
> by default. The rationale for this change is that the default config
> implemented in earlier nwam versions is the same as the Automatic NCP
> behavior, and we expect that most users will not have made changes, and
> therefore will want the Automatic NCP. The previously discussed change
> with respect to automatic addition/removal of inserted/removed links
> makes this especially desirable. Users who actually modified their
> earlier configuration (which should be a small minority) can switch to
> the User NCP to get their changes.
>
> There is one exception: if any static addresses are specified in the
> llp file, it is very clear that the user did in fact modify that file;
> therefore, if a static address is found, the User NCP will be active
> upon upgrade.
>
> Location profiles did not exist in earlier versions of NWAM, so any
> configuration that NWAM does based on Location specifications may
> overwrite previous system configuration. On upgrade, the existing
> configuration will be saved into a User location. This location will
> be activated if it includes an nsswitch.conf file which uses a nameservice
> other than DNS (i.e. a nameservice that cannot be configured by NWAM
>
you mean other tan DNS *and* files, ?
> based solely on information obtained from the network).
>
Kais
