Slackware Network prob...Close to solving
 

OK, I think I am close, but I am not sure what the final ingredient is:

I just installed Slack 9.1, and I am trying to configure my network. I have an HP Pavillion Laptop, with a National Semiconductor card, connectied to a router to a cable modem. Slack recognizes my card at boot, reading, eth0: link up. When I run lsmod, the card is on there, and when I run ifconfig eth0 up, it lists my eth0 setup BUT, it doesn't appear to be assigning me an ip address. Here is the output of ifconfig eth0:

Code:
LinK encap: Ethernet HWaddr 00:0D:9D:C9:94:0E
BROADCAST MULTICAST MTU: 1500 Metric: 1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collision:0 txqueuelen:100
RX bytes:1017 (1017.0 b) TX bytes:8260 (8.0 Kb)
Interrupt:11 Base address:0xc000


I have tried to run netconfig and dhcpcd, but it hasn't helped. When I run ifconfig eth0 up, my eth0 gets displayed, but then if I run dhcpcd eth0, afterwards, ifconfig then displays only LO again. Any suggestions? Thanks a lot!! Also, when I boot, it brings up the eth0 interface and says link up: remaining active for wake-on LAN.

This will probably help.

Well, it sounds like I have the exact same problem as that guy did, but that still didn't work. AAAAAHHHHHHHHHHHHHHHHHHH!!!!!!!!

Since you're using a router you might have better luck assigning a static ip

Like jarib says, give yourself a staic IP and is less headaches than DHCP.

Assign the machines an IP address of your choice from the private range (102.168.xxx.xxx) and set the router as your default Gateway. For the Gateway, look in the router's documentation and look for its default IP address and use that. (should be something along the lines of 198.162.0.1 or 192.168.1.1, etc. Each brand uses a diff default) If you have no default in the manual/docs, just assign 198.168.0.1 to the router and tell Slack to use that as the Gateway. After that you're set.

HTH
Best regards...

err. typo? S/B 192.168.xxx.xxx

actually, to put yourself on the same subnet as router s/b 192.168.0.xxx

Definitely a TYPO!!!!! LOL thanks for the catch . Fatter fingers than usual this evening :D

Regards...

Thanks for the reply's. I will attempt your advice and check back here. Also, is it possible there is a problem because I have both pcmcia and the regular network both installed? Should I get rid of the pcmcia stuff? Thanks.

AWSOME!! Thanks for the help. A few quick points/questions though:

- I think what threw me off was the fact that the first time I connected the computer to the router,, I was installing Gentoo, and the connection worked without a hitch, via DHCP. A few days later, due to some problems, I had to do a re-install, and since then, the ethernet connection has not worked until now(with the Static IP) That's basically the reason I didn't try it with Static, although now, I guess that was foolish. Well, I restarted and all is still good, so hopefully I will be good from here.

- Immediately after I changed the settings, I noticed on my Desktop, where I am using this forum, running WinXP, it suddenly said there is no connection, and I got worried, but after closing IE and reopening it, it works now. Any ideas why this is? Did my settings in Slack affect my router, which in turn affected my connection on my desktop?

Anyways, thanks a lot for the help. It is very much appreciated!! Now, do I dare say that I am about to try and configure wireless??? Here we go.....

You might have used the ip assigned to xp. You could assign a static ip to xp through network connections and tcp/ip properties just to prevent xp from grabbing the ip assigned to slack.

I thought that might have something to do with it, but I specifically took the next ip, so my Win machine is ....101, and my slack, I assigned ....102. Could this be a problem?

I don't think it should be

disclaimer, I'm not a network admin by any stretch so can't say for sure.

I use a DLink DI 604 & had a similar problem.
Linux is a bit, shall we say aggressive in it's use of TCP/IP
It would occasionally force a reboot in the router, the only indication was a popup on a windows machine across the room saying no connection... A firmware upgrade on the router fixed it & now there's no problem