Well, I tried the ne2k driver for that soho card, and it
wouldn't
install, saying "device or resource busy". So, I tried the tulip driver, which
installed. On a reboot, eth0 was detected (woohoo!). Then, I installed dhcpcd,
and gave it eth0 as the interface. It segfaulted.
On Sat, Sep 11, 1999 at 06:43:08AM +, [EMAIL PROTECTED] wrote:
> Have you tried running dhcpcd-sv rather than dhcpcd?
>
> Bryan
>
>
>
>>
> >> Hello,
> >>
> >> I'm at the end of my wit here... I can't get my Linux box (running
> >> slink)
> >> to communicate with the DHCP server at my off
Have you tried running dhcpcd-sv rather than dhcpcd?
Bryan
On 18-Aug-99 Buter wrote:
> Used wrong email-address. Please respond to
>
> [EMAIL PROTECTED]
>
> Renald
>
>>
>> Hello,
>>
>> I'm at the end of my wit here... I can't get my Linux box (running
>> slink)
>> to communicate with th
Used wrong email-address. Please respond to
[EMAIL PROTECTED]
Renald
>
> Hello,
>
> I'm at the end of my wit here... I can't get my Linux box (running
> slink)
> to communicate with the DHCP server at my office.
>
> Windows 95 no problem.
>
> Static IP under Linux used to be no problem.
>
Hello,
I'm at the end of my wit here... I can't get my Linux box (running
slink)
to communicate with the DHCP server at my office.
Windows 95 no problem.
Static IP under Linux used to be no problem.
(I updated to kernel 2.2.10 and to the dhcpcd 1.3.x package)
Sigh
Renald
>
> Hi all:
>
> I got my cable modem installed today, and now I'm trying to get it
> running under Linux. The Cable-Modem Howto directed me to the DHCP
> Howto, and it instructed me to install the dhcpcd client. I downloaded
> dhcpcd_0.70-5.deb and when I installed it I got the followinf error
>
Hi all:
I got my cable modem installed today, and now I'm trying to get it
running under Linux. The Cable-Modem Howto directed me to the DHCP
Howto, and it instructed me to install the dhcpcd client. I downloaded
dhcpcd_0.70-5.deb and when I installed it I got the followinf error
message from dpkg
> Chris wrote:
>
> > Also every time I shut the machine off it releases the IP lease, which
> > results in the lease only lasting for the period in which the machine is
> > turned on. Why does it need to release the IP lease? Surely it should
> > hold onto it so that it can use the same IP on th
When you look at the log do you see that your dhcp client is requesting an IP
address that it isn't being granted? It's probably trying to get its old IP
and the server won't give it.
I haven't read the RFC but I'll bet that releasing the lease on shutdown is
compliant behavior. What would be the
I am having a problem with my dhcp client.
Basically the machine taking extremely long time to obtain an IP address.
The machine is sending a DHCPREQUEST allright, and this is being answered
by the server with the DHCPOFFER. However the sends several more
requests before it starts to work.
Also
10 matches
Mail list logo
