Click to See Complete Forum and Search --> : debian install dhcp failing
bigskinnee
01-22-2001, 04:33 AM
I have now done 2 complete installs of debian 2.2r2 and both have gone fairly smooth except for the network config. I have a DSL connection that goes into a hub and all my machines DHCP to get the IP info.
I have installed debian on a machine with a 3com 3c509b and on another machine with a netgear FA310TX.
For the 3com I used the 3com driver and for the netgear I used the tulip driver. But each time the DHCP connection fails.
This is the last step in me switching to Debian from Redhat.
DJ-dOoK
01-22-2001, 07:17 AM
Is the DSL connection connected directly into the hub or into a router or another machine? Please be more specific about that, as directly into the hub would not work.
And a bit more on what errors you get would be better as well.
Oh BTW. Are you using DHCPCD or DHCP-client? It is better to use DHCP-client.
------------------
One day, the DJ declared! Let this OS be taken to the world, and Linux was introduced to many frustrated windows users!
bigskinnee
01-22-2001, 10:56 AM
OK
my DSL connection comes out of my phone line and into a Cisco 675 router. The router is connected to the hub with cat 5.
As far as I know Im not using any of the dhcp things you mentioned.
In my /etc/network/interfaces i have the line
iface eth0 dhcp
Its not exactly that but Im not looking at it right now.
As far as errors go im not really getting any errors other that it says it failed to configure the eth0 during install.
Thanks
paully1
01-22-2001, 11:59 AM
Originally posted by bigskinnee:
OK
my DSL connection comes out of my phone line and into a Cisco 675 router. The router is connected to the hub with cat 5.
As far as I know Im not using any of the dhcp things you mentioned.
In my /etc/network/interfaces i have the line
iface eth0 dhcp
Its not exactly that but Im not looking at it right now.
As far as errors go im not really getting any errors other that it says it failed to configure the eth0 during install.
Thanks
I've never used debian (i run slack 7.1) and my dhcpcd fails to connect on bootup everytime. But when i log on i do
dhcpcd -h <hostname> as root and it connects.
I know little about networking, I just know that works for me in slack. But I'm still a bit of a newbie so who knows http://www.linuxnewbie.org/ubb/smile.gif
I'm sure you'll get answers from people who know what the hell they're talkin about. Instead of people like me, who prolly dont know what the hell they're talking about.
paul
[This message has been edited by paully1 (edited 22 January 2001).]
bigskinnee
01-23-2001, 01:48 AM
I have tried both dhcpcd and dchp-client and neither can find a dhcpserver. However I know one exists cause this is a dual boot machine and windows obtains and IP just fine.
Again I have a netgear FA310 tx using the tulip driver on Debian 2.2r2
The nic is eth0 and appears to be on IRQ 10
I have disabled PnP in the bios
I have had Redhat on this exact same machine and it had no problems accessing the net through DHCP.
DJ-dOoK
01-23-2001, 04:29 AM
If it is using the tulip driver I don't think it is NE2000 compatible anyway, but is it? Do you know exactly what the I/O range of the card is? Sometimes this needs to be given to the module at boot time. You can find this in windows.
Hope this helps.
------------------
One day, the DJ declared! Let this OS be taken to the world, and Linux was introduced to many frustrated windows users!
bigskinnee
01-23-2001, 12:08 PM
Im not really sure. The Netgear card is in the tulip list that is found here on Linux Newbie.
I was able to get the I/O range from windows but how does this help me in linux?
This same machine dual boots Redhat. Is there any way that I can find out what driver it is using and how it is configured/called and transfer that info to my debian install?
bigskinnee
01-25-2001, 01:06 PM
Well I was able to get this to work but it wasnt pretty. Since the kernel/modules, from the debian install, for my network card were not working I used a 2.4 kernel with tulip compiled into that I had compiled for a redhat system. I brought it over disk by disk and booted it. Worked like a charm.
Must have been something wrong with the default modules that come with 2.2r2