netlink

[Benjamin Minshall]

If I remember correctly, the "random" IP assignment assumes a 255.255.255.255
netmask, so the card really can't do anything without a static route entry.  The
address is generally in the 169.* range, which I believe is reserved.

Jeff Goeke-Smith wrote:

> > -----Original Message-----
> > From: linux-user-admin@egr.msu.edu
> > [mailto:linux-user-admin@egr.msu.edu]On Behalf Of Ben Pfaff
> > Sent: Sunday, April 23, 2000 8:30 PM
> > To: Jeff Goeke-Smith
> > Cc: linux-user@egr.msu.edu
> > Subject: Re: netlink
> >
> >
> > "Jeff Goeke-Smith" <jeff@goeke.net> writes:
> >
> > > Be aware that some cards ( or perhaps this is true for all
> > > cards under windows) have a mode called IPautoconfig.  This
> > > causes the card to pick up a random IP if it can't pick up an
> > > address from a DHCP server.  [...]
> >
> > That's a funny "feature".  Is it ever useful?
>
> Hmmm,  Let's just say I've never seen it be useful.  I'm certain that in
> some very strange situations where 1) the person setting up a network has no
> idea how to assing IPs, 2) they would of course not know how to set up a
> DHCP server, and 3) they were not connecting to a external network, this
> might be useful.
>
> Otherwise, It's generally just a pain in the butt because it hides the real
> problem. ( The network card isn't connecting to the network)  Unless you
> know what sort of IPs your expecting to get winipcfg doesn't help you much.
>
> So, there you go, yet another feature that might have been useful (sometime)
> gone wrong.
>
> --Jeff Goeke-Smith
>
> _______________________________________________
> linux-user mailing list
> linux-user@egr.msu.edu
> http://www.egr.msu.edu/mailman/listinfo/linux-user

--
-------------------

Benjamin Minshall
minshal1@pilot.msu.edu