🚀 go-pugleaf

"Matthew McKernan" <mckernan@optushome.com.au> wrote in message
news:tBB%5.161476$e5.127124@newsfeeds.bigpond.com...
> I have set up my NIC in Red Hat 7.0. That works fine. I am at a point
where
> I can type the following and I get access:
>
> /sbin/dhcpcd -d -I coXXXXXX-a eth0
>
> Where coXXXXXXX-a is my login ID.  That all works fine. Where I have the
> problem is on bootup. During the boot though linux has a look at eth0 and
> then after about 30 seconds it comes up as failed. So it doesn't connect
to
> the net at that point. In past linux set ups some how I managed to get it
to
> connect at that point. Suggestions?
>
> As a temporary work around I just added the line above (/sbin/dhcpcd -d -I
> coXXXXXX-a eth0) to the end of rc.d and that seems to do the trick for
now.
> I would prefer to have it set so that during boot when eht0 is checked it
> can connect then. Doing it that way would also reduce boot times a fair
> bit!!!
>

It could be the eth0 at the end.  It's been a fair while since I've read the
docs, however I thought those options went into /etc/dhcpcd.conf IIRC along
a syntax like "interface eth0", then just use the command /sbin/dhcpcd -h
co1234567-a
                      ^
I thought that was how you specified host, but I could be thinking of pump.
If you still having further problems I'll see how mines setup when I get
home tonight.

-,m

Are you trying to run dhcpcd before installing the module for your
ethernet card ?  Look in the dmesg output.

Matthew McKernan <mckernan@optushome.com.au> wrote:
> I have set up my NIC in Red Hat 7.0. That works fine. I am at a point where
> I can type the following and I get access:

> /sbin/dhcpcd -d -I coXXXXXX-a eth0

> Where coXXXXXXX-a is my login ID.  That all works fine. Where I have the
> problem is on bootup. During the boot though linux has a look at eth0 and
> then after about 30 seconds it comes up as failed. So it doesn't connect to
> the net at that point. In past linux set ups some how I managed to get it to
> connect at that point. Suggestions?

> As a temporary work around I just added the line above (/sbin/dhcpcd -d -I
> coXXXXXX-a eth0) to the end of rc.d and that seems to do the trick for now.
> I would prefer to have it set so that during boot when eht0 is checked it
> can connect then. Doing it that way would also reduce boot times a fair
> bit!!!


-- 
George Durbridge

Matthew:
   Search for a file called "ifup" on your hard drive. Edit this file,
and replace the call to pump near the bottom of the file with the call
to dhcpcd exactly as it works for you. Your network settings should
configure themselves at bootup then. Let me know if this works.

    Mark W. Stroberg

On Tue, 19 Dec 2000 15:46:12 +1100, "Matthew McKernan"
<mckernan@optushome.com.au> wrote:

>I have set up my NIC in Red Hat 7.0. That works fine. I am at a point where
>I can type the following and I get access:
>
>/sbin/dhcpcd -d -I coXXXXXX-a eth0
>
>Where coXXXXXXX-a is my login ID.  That all works fine. Where I have the
>problem is on bootup. During the boot though linux has a look at eth0 and
>then after about 30 seconds it comes up as failed. So it doesn't connect to
>the net at that point. In past linux set ups some how I managed to get it to
>connect at that point. Suggestions?
>
>As a temporary work around I just added the line above (/sbin/dhcpcd -d -I
>coXXXXXX-a eth0) to the end of rc.d and that seems to do the trick for now.
>I would prefer to have it set so that during boot when eht0 is checked it
>can connect then. Doing it that way would also reduce boot times a fair
>bit!!!
>
>

If you are using RedHatLinux7.0, this may help ..

Edit the ifup script to append "-h coXXXXXXX-a" in the '..ARGS=' lines
for pump (and dhcpcd)
--
Trevor Kerr
Blackburn  Victoria  Australia