Hey, I have a slack 10 installation. Seems to be working fine...but I plugged it into my network, and I can't get it to work.
I ran the network setup thing that Setup itself ran, but wasn't sure what to put in for domain, name, etc, so I used arbitrary values (hfl for both. the name is what I want it to be, I have no idea what to do w/r/t the domain...is it like my windows workgroup?)...I'm just running a simple home network, DHCP on a D-link DI-524. My 2 windows computers aren't having any trouble, so I think the network isn't the problem.

When I hit the commandline as root and run "ifconfig", only lo shows up. If I run "ifconfig -a" lo and eth0 shows (my ethernet card is something like a Kingston kne-100tx or the like. Not sure off the top of my head, but eth0 exists, so I don't think that's the problem.)

Eth0, as shown by "ifconfig -a", has no IP address--not 0.0.0.0 as the linux wiki suggested might happen, but none at all.
the ifconfig entry looks *something* like this. (this was just copy/pasted from the wiki with the relevant lines removed, so not actually.)
eth0 Link encap:Ethernet HWaddr 00:90:F5:03:4B:69
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:911573 errors:0 dropped:0 overruns:0 frame:0
TX packets:656393 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:604721438 (576.7 Mb) TX bytes:58964684 (56.2 Mb)
Interrupt:10 Base address:0xf000

I tried pinging my router's IP (192.168.0.1), but got a "network is unreachable" error.

What am I doing wrong, and how can I fix it? What should I put in for my domain? How can I get the box to hit my router, pick up dhcp, and reach the internet? Thanks.

try ifconfig etho up
if you then type ifconfig and you see lo and eth0 .. try this.
dhcpcd eth0

Does the link light show up on your router when you type ifconfig eth0 up?
Does your router support 10 and 100? Does the card as well? Have you swapped network cables?

A friend of mine gave me some help...I seemed to have gotten it up with a static IP address by typing...
ifconfig eth0 192.168.0.200 broadcast 192.168.0.255 netmask 255.255.255.0
followed by...
then route add -net default gw 192.168.0.1 netmask 0.0.0.0 eth0
and adding my comcast nameserver to /etc/resolv.conf
Don't know if this is the best solution, but it seems to work...I can load websites, the like........anything else I should do? (I seem to remember hearing something about /etc/rc.d/rc.inet1 or the like w/r/t getting this to work after a reboot....am I correct?

Well you can do two things now, or configure /etc/rc.d/rc.inet1.conf to put the ip for you or put the ifconfig command in /etc/rc.d/rc.local.

Hi!

I am having the same problem. After booting Slack-10.0, the eth0 gets no IP adress from the my Router (Netgear FR114P) and there is the same "network is unreachable" error message.
But after manually running '/etc/rc.d/rc.inet1 restart' (as root) eth0 gets a proper IP adress.

For now I have put the folllowing line to /etc/rc.d/rc.local: '/etc/rc.d/rc.inet1 restart' and now everything is right. This seems to be a Slack-10.0 problem only, because neither Slack-9.1 nor Win2000 did make any problems.

phase9: same here. I had created a batch file wirelessh and wirelessw (home and work) with different keys and settings so I could run them manually.. wirelessh runs by default and all is well.

I wonder if it's a timing issue .. something isn't loading quick enough so dhcpcd times out only to work later?

Probably the timeout set by Slackware rc.inet1 script is too short. You can edit the /etc/rc.d/rc.inet1 script to change that. The default is 10 secs.
That should give the dhcp server more time to respond to the DHCP request.

Hi!

Oderus and rotvogel: It seems you both where right about the timing issue with dhcpd.
I changed, as rotvogel suggested, the timeout to 30s and the problem didn't occur anymore when starting slack-10.0

Thanks to both of you.