James Carlson wrote:
> I agree. I'm talking just about supporting networks where LLA might
> be present due to unconfigured (and thus not "server") machines
> somewhere on the net. I'm not talking about using LLA to configure
> usable interfaces on those systems classed as "servers" -- that would
> indeed be bad.
>
> I think there are two components here -- what a system with global
> addresses does when it receives packets from a system actively using
> LLA, and what a system does when it has no way of getting IP
> addresses.
>
> The latter is the dynamic addressing you're rightly pointing out as
> unhealthy. The former, though, is just supporting -- or even just
> _viewing_ -- the machines on the network that have fallen through the
> cracks.
I guess the original idea behind having LLA is for setting
up a network without the need to have a, say DHCP server.
All the machines plugged in that network can "just" work,
and all of them are using LLA. In the above scenario, are
we trying to "stretch" the LLA solution to handle something
it is not designed for? Is this case really a problem our
customers are facing?
> In addition to the trivial "how do I talk to my printer?" problem, I
> think the underlying problems it's trying to address are:
>
> - Too many people are stuck on SWAN-like networks where somebody
> else controls the infrastructure and forbids the use of
> "unauthorized" DHCP servers. If you're unable to get an address,
> LLA gives you a "degraded" mode of operation where you can still
> reach some local services and perhaps file a service desk ticket
> on your problem. ;-}
Not talking from the technical view point, the above may
actually be a violation of the network policy. In fact,
if Solaris supports this, the network admin will probably
turn off this feature in all the Solaris machines.
> - Many systems (including Solaris!) are designed so that boot time
> is "special," and if the right things don't happen then because
> one of the servers is temporarily out, then the system is in a
> lame or even semi-comatose state. If this leads to a lack of an
> address, LLA gives you a way to log in remotely and fix or at
> least restart the system.
I don't really know if this is actually an "important"
aspect of LLA. This assumes that the network is the only
way to communicate with the machine in trouble and somehow
that machine using LLA can be found. Is this a problem
our customers are facing today?
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
