Anyone have a good dhcpcd-ethX.exe?
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 wrong? TIA #!/bin/bash exec /tmp/dhcpd.log 21 echo $* cat EOF $(date) PATH = $PATH Ip Address has changed. It is now $1. Please run the following commands: service sendmail stop service xntpd stop service pmfirewall stop Then run: service pmfirewall start service xntpd start service sendmail start Ok. I will do it. Also: service fetchmail stop % EOF date echo PATH=$PATH service sendmail stop service ntpd stop service pmfirewall stop service pmfirewall start service ntpd start service sendmail start #su -c 'fetchmail -q' -l steveo #su -c 'fetchmail -f ~/.fetchmailrc-rcn' -l steveo mail -s DHCP IP address change to $1. steveo EOF Your ip address has just changed to $1. See /tmp/dhcpd.log for details. EOF ddclient -nodaemon exit 0 -- -Time flies like the wind. Fruit flies like a banana. Stranger things have - -happened but none stranger than this. Does your driver's license say Organ -Donor?Black holes are where God divided by zero. Listen to me! We are all- -individuals! What if this weren't a hypothetical question? [EMAIL PROTECTED] * To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *
dhcpcd vs. dhcp-client?
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] -Stranger things have happened but none stranger than this. Steven W. Orr- Does your driver's license say Organ Donor?Black holes are where God \ ---divided by zero. Listen to me! We are all individuals!- ** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **
Need an ifup that know about dhcpcd instead of pump.
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 are where God \ ---divided by zero. Listen to me! We are all individuals!- ** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **
Re: dhcpcd
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 connection lately, and I think that pump may be the problem. I'm just not sure if I need to do anything other than remove one and install the other. TIA, Not if you're using RedHat. RedHat specifically calls pump as part of the ifup-interface and ifdown-interface scripts. And the command lines aren't compatible. The best idea I'd have is to create a script named pump, that calls dhcpcd instead. MINOR differences, really, as pump would be called: pump -i interface, and dhcpcd as dhcpd interface. Can;t remember the command line to bring pump down, but it's dhcpcd -k interface for dhcpcd.. --- Thomas Charron Wanted: One decent sig Preferably litle used and stored in garage. ? ** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **
Re: dhcpcd
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 pump to
PUMPARGS="-h $DHCP_HOSTNAME"
fi
echo -n "Determining IP information for $DEVICE..."
if /sbin/dhcpcd -d -D -H -c /etc/rc.d/rc.firewall $DEVICE ; then
echo " done."
else
echo " failed."
exit 1
and In my ifdown I changed the line that kills pump to
fi
if [ "$BOOTPROTO" = bootp -o "$BOOTPROTO" = dhcp ]; then
dhcpcd -k ${DEVICE}
fi
JDF
Thomas Charron wrote:
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
connection lately, and I think that pump may be the problem. I'm just not
sure if I need to do anything other than remove one and install the other.
TIA,
Not if you're using RedHat. RedHat specifically calls pump as part of the
ifup-interface and ifdown-interface scripts. And the command lines aren't
compatible.
The best idea I'd have is to create a script named pump, that calls dhcpcd
instead. MINOR differences, really, as pump would be called: pump -i
interface, and dhcpcd as dhcpd interface. Can;t remember the command line
to bring pump down, but it's dhcpcd -k interface for dhcpcd..
---
Thomas Charron
Wanted: One decent sig
Preferably litle used
and stored in garage. ?
**
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**
**
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**
Pump vs dhcpcd
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 seconds. It still failed at times, but not *NEARLY* as often as pump did.. When I kicked in the -t option to like 60 seconds, it *NEVER* failed.. What's up with pump? Is there some secret to it, or does it just not that great at times with certain dhcp servers? Does RH 6.2 update this? ** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **
Re: Pump vs dhcpcd
On Sun, 9 Apr 2000, Thomas Charron wrote: What's up with pump? Is there some secret to it, or does it just not that great at times with certain dhcp servers? Does RH 6.2 update this? pump is, according to the documentation, a "a daemon that manages network interfaces that are controlled 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, and doesn't appear to be ready for prime time. Why Red Hat decided to replace dhcpcd with it, I don't know. When I was setting up the Linux Lab at NHCTC, I found that the version of pump distributed with RHL 6.1 did not work with their DHCP server. I needed to get an updated RPM out of the *maintainer's home directory* on people.redhat.com to get it to work. RHL 6.2 does ship with a newer version then 6.1, and it does fix several bugs (especially hangs). -- Ben Scott [EMAIL PROTECTED] | "...it is important to realize that any lock can be picked with a big | | enough hammer" -- Sun System Network Admin manual | ** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **
