I've never really ever gotten mine to work. If I run the stuff manually
I'm ok when the lease fails to renew. But I was in communicado all day
today when after 6 months or so, rcn decided to not renew at 9:30 AM :-(
Here's my current script that doesn't work. Anyone have a clue what I'm
doing
I just switched from pump to dhcpcd for my cable modem and now I see that
there's (at least) Yet Another dhcp client out there. Does anyone know
anything about possible pros and cons of dhcpcd vs. dhcp-client?
TIA
--
-Time flies like the wind. Fruit flies like a banana. [EMAIL PROTECTED
Is anyone using it? If so, could you please send me your /sbin/ifup
script?
Many thanks.
--
-Time flies like the wind. Fruit flies like a banana. [EMAIL PROTECTED]
-Stranger things have happened but none stranger than this. Steven W. Orr-
Does your driver's license say Organ Donor?Black holes
Quoting "Kenneth E. Lussier" [EMAIL PROTECTED]:
All,
Can I just rpm -e pump-0.7.2-2 and install dhcpcd-x.x-x and have my
system
work as normal? Right now, I have eth0 set up to use dhcp to obtain ip,
dns, etc. and I'm using pump. I've been having a lot of trouble with my
I didn't like pump when it was first released, so I have been removing
pump and loading dhcpcd since pump was introduced.
Edit /sbin/ifup and /sbin/ifdown so that dhcpcd is invoked instead of
pump,
when the interfaces are brought up and shutdown. On my firewall I
changed the
line that invoked
a *itch of a time getting dhcp data on startup from MediaOne, and I came
accross something I *know* someone had a conversation with earlier..
My solution was to replace "pump" with "dhcpcd". Where pump was taking
several tries to gather data, dhcpcd takes a few secon
olled by either the DHCP or BOOTP protocol". It
appears to simply be another implementation of a DHCP client. What advantages
over "dhcpcd" it is supposed to have, I don't know.
Now, a new DHCP client would be okay with me, if it worked. But pump is
currently in 0.x versions
