Hi, I already posted this message in the newbie forum, but I think this is a better place to post this question.

I just installed Slackware 10.2 and have trouble connecting to the local network / the internet. A little information:

Using netconfig I configured my host as followed:

ip: 192.168.1.100
gateway: 192.168.1.1 (router, set to static local IP addresses)
netmask: 255.255.255.0
dns: my dns ip address

In ifconfig I can see that eth0 is up and running with the specified ip adres.

I'm on an 'old' lap-top (compaq presario 1700) with a Conexant LANfinity ethernet card which is detected automatically at startup.

Even though everything looks fine, I don't seem to have a connection to the (local) network. I can't ping the router even though it's in the proper range. I've tested the network cable and it's fine.

Any advice on how to fix this would be appreciated!

have you tried "dhcpcd" in the terminal as root

I just tried it but it doesn't do anything. The router is also not configured for DHCP.

Perhaps my NIC's physical port is broken.. I will check with a cross-cable..
edit: the physical connection is working fine

Well, the first thing in this case is to know what your computer "believes" the eth0 configuration is. For that use:
"/sbin/ifconfig" and post the results, so we can make sure your settings did take.

the result from ifconfig for eth0:



I typed this over so mind a capital letter or a missing space here and there..

you might have a firewall?? Try /sbin/iptables -L

OK, so we can conclude that your machine does find and allocate an IP address for your card.
Now, lets find if the card finds a way out to the "outside" world. For that we use the command:
/sbin/route.
You should get something like this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.148.0 * 255.255.255.0 U 0 0 0 vmnet8
172.16.188.0 * 255.255.255.0 U 0 0 0 vmnet1
default it2web 0.0.0.0 UG 0 0 0 eth0 <-- That is the important line.
In your case you may have an IP address instead of a name (it2web), but that is OK.
If unsure post the result and we will keep going from there.

Rick

LuggerHouse: I don't have a firewall running, ip-tables -L doesn't give me any rules.

ralvez: This is the result of /sbin/route:
ps. Remember that I am unable to ping 192.168.1.1!
ps2. I use the [code] tags to keep the layout readable, hope that that's ok.

So the cable is good. Are the link lights illuminated on the router as well as the PC?
What is the output of the command mii-tool (may not work with this adapter)? Does it show the link good? What is the mode(full duplex) and speed (100mbs)?

Try disabling Plug and Play in the computers BIOS.

So far so good. Like michaelk says issue the command "mii-tool" (you must be root for this test to work) this will test the connection of eth0 (actually any number of cards connected to the system under test).
You should get something like this for response:
eth0: negotiated 100baseTx-FD flow-control, link ok
If there is a problem between the card and the switch, be it the cable, the card itself or the switch box ( I'm guessing you use a switch box to connect the two machines) you would get something like this: eth0: no link
Now, if you confirm your card and cables, switch box are OK, then use the command "ping 192.168.1.1" and take a look at the connection lights on the NIC card, the switch box and the NIC card in the router. Do the lights blink?
If they all do, then your router is ignoring the queries. It is possible that your hosts.allow, hosts.deny in the router are blocking your machine.
So, lets do those tests and then we will continue troubleshooting based on what you find.

Rick

Hi,
Ping is working at network layer of OSI model, so let first try to check if the physical layer is responding or not by checking the reply for arping.
I m not much sure about arping command in Slackware ;in redhat you can do it something like this : arping -I eth0 192.168.1.1
Just check if that works or not. Then we can further think whether any firewall may be blocking or some other prb may be there.

mii-tool:
eth0: negotiated 100baseTx-FD, link ok

arping:
ARPING 192.168.1.1 from 192.168.1.100 eth0
Unicast reply from 192.168.1.1 [00:A0:C5:78:B4:EA] 4.102ms
Unicast reply from 192.168.1.1 [00:A0:C5:78:B4:EA] 1.064ms
Unicast reply from 192.168.1.1 [00:A0:C5:78:B4:EA] 1.073ms
......

so.. what to do next?

ps. normal ping to 192.168.1.1 does not work!

OK. It seems to me that there is a firewall in your router that does not allow your machine to communicate with it.
Remember what LuggerHouse suggested? His idea was to log in into your router as root and issue the command : "iptalbles -L "
If there is a firewall setup it will display the rules ... that is likely your problem.
Try that.

R

The router is a hardware router without firewall rules and I am sure it allows me to connect to it. If I put the cable into my windows xp pc (with the same ip 192.168.1.100 as the linux box) it works perfectly.