LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   slack 9.1 and dhcp (https://www.linuxquestions.org/questions/slackware-14/slack-9-1-and-dhcp-127110/)

ummmm.... 12-18-2003 09:01 PM

slack 9.1 and dhcp
 
I am having problems getting dhcp to work on a new install (this doesn't seem uncommon from what I've read). I've tried everything I've found so far to fix it but to no avail. I have Slackware 9.1 (full install) with a 3c905x network card. My router is serving as the dhcp server. I have two WinXP machines on the same network and both work fine. I had this machine working with 9.0 running a sof2 server before with no problems. I've tried netconfig several times, nothing. I've tried manually editing rc.inet1, resolv.conf, and others I cannot think of. When booting I get:

dhcpcd: MAC address = (myMACaddress)
dhcpcd[71]: broadcasting DHCP_DISCOVER

dhcpcd[71]: timed out waiting for a valid DHCP server response

This is what I get when I run ifconfig:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

and if I run ifconfig eth0 up i get:

eth0 Link encap:Ethernet HWaddr 00:50:04:E3:3D:24
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:1180 (1.1 Kb)
Interrupt:10 Base address:0xd800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

I tried forcing an ip on eth0 (192.168.0.5), but when I attempted to ping another computer(192.168.0.2) on the network, it pinged itself (192.168.0.5).

What else can I try? This is becomming annoying.

miaviator278 12-19-2003 12:35 AM

( post #22) mark_booze

Well team, you will be glad to hear that I am typing this on my linux box. I found the DHCP configuration on a freeBSD site (www.freebsd.peon.net/quickies/14/) It is buried in etc/sysconfig/network-scripts/ifcfg-eth0. It seemed to require a re-boot (I thought linux didn't need those) to enable connection, but it seems fine now.

-------------------------
that information may help, it may help to search for and read that entire thread. if not keep posting...

DavidPhillips 12-20-2003 12:04 AM

I don't think a reboot is required.

Maybe restarting the service or interface would be required.

DavidPhillips 12-20-2003 12:09 AM

ummmm...

It sounds like you need to set a default gateway along with the ip address
Code:

ifconfig eth0 192.168.0.5
route add default gw 192.168.0.1

also the nameservers need to be added to /etc/resolv.conf
Code:

nameserver 192.168.0.1  # your dns server ip

I'm not sure what's in Slack these days but maybe this will work
Code:

dhclient eth0
or
Code:

dhcpcd eth0

ummmm.... 12-20-2003 10:51 AM

Thanks for the help. I entered dhcp -G 192.168.0.1 and all is well now. I guess it just needed some help finding the gateway. It now works even after a reboot.


All times are GMT -5. The time now is 02:48 PM.