[KLUG Members] chartermi cable

Adam Tauno Williams members@kalamazoolinux.org
Fri, 05 Oct 2001 08:45:14 -0400 (EDT)


>>>>So what is the advantage of dhcpcd over pump?
>>>1)  dhcpcd doesn't crash my laptop, pump does about half the time.
>>Now that's a feature!
>I have a very flaky PCMCIA NIC.  I can also crash my system
>if I start paying around with manual commands like ifconfig.
>It also doesn't work with the new kernel PCMCIA support, I 
>had to compile the old pcmcia drivers.
>I don't have these problems with other PCMCIA NIC's.  I only
>keep this flaky one because it's really fast (when it works :) 
>and it connects on a long TP cable I have that's over specs, 
>where other PCMCIA NIC's won't.  And when using dhcpcd, the NIC 
>is usually not a problem.

Fast is good.  I have Dlink, Linksys, and Xircom PCMCIA NICS,  and while the
Xircom is faster than either the Dlink and Linksys they all tempt me to glance
behind the laptop to see if I'm plugged into the network via a NULL modem
cable.  The Dlink is the worst,  a 10/100Mb card that can barely manage
2-3Mb/s,  on a fast brand new laptop and plugged into the same switch as the
server.  It is like swimming in a huge vat of honey,  only not as sweet.

On the Dlink and the Linksys,  if you have "start at boot" enabled,  any attempt
to shutdown the interface hangs.  If you disable "start at boot" and manually
turn it on via the applett, you can turn it on/off all day long without
incident.  Very strange,  but at least I'm not alone.

Maybe I should just buy a wireless NIC?! :)  Would probably be about the same
speed.....

>>>2)  Hostname changes as sent from DHCP server on dhcpcd, not pump.
>>>    (at least with the default Redhat parameters on each)
>>This is for DNS update I presume?  Does anyone use the DHCP-DNS update
>>hook?  I haven't since Samba does that too and we had Samba before we
>>installed DHCP.
>All I know is the hostname (as displayed by the console getty's)
>change to the name dhcpd dishes out when using dhcpcd, and it
>doesn't change when I use pump.

Ah, the name comes down to the client from the DHCP server,  not vice-versa. 
I've never used that either.

>>>3)  dhcpcd seems to work from DHCP servers where pump won't.
>>Hmmmmm.
>Sorry I can't be more specific, but I don't remember which
>servers I had problems with.

No problem,  I can't remember exactly where dhcpcd didn't work anymore either.

Systems and Network Administrator
Morrison Industries
1825 Monroe Ave NW
Grand Rapids, MI. 49505