Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have two PCs here each one of them has Red Hat Linux installed (one version 8 and another version 9) each one of them has NICs installed and working, which I connect to each other with a crossover cable. Right now I'm stuck at pinging the boxes from each other. Still, I can ping interfaces locally with no problems.
I will paste here the output and contents of things which I suppose are responsible for network, please, correct me if I did some stupid mistake.
[root@localhost etc]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
iptables chains are empty for both:
[root@localhost network-scripts]# iptables -L -v
Chain INPUT (policy ACCEPT 1319 packets, 895K bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 1485 packets, 449K bytes)
pkts bytes target prot opt in out source destination
also this is true for both:
[root@localhost etc]# cat /proc/sys/net/ipv4/icmp_echo_ignore_all
0
and on both I always get the same result when pinging the other box:
[root@localhost etc]# ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) from 192.168.0.1 : 56(84) bytes of data.
From 192.168.0.1 icmp_seq=1 Destination Host Unreachable
From 192.168.0.1 icmp_seq=2 Destination Host Unreachable
From 192.168.0.1 icmp_seq=3 Destination Host Unreachable
Though I am able to ping locally say on Red Hat 8:
[root@localhost etc]# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) from 192.168.0.1 : 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.065 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.058 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.058 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.058 ms
--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 3999ms
rtt min/avg/max/mdev = 0.058/0.059/0.065/0.007 ms
Now, please please please, do not ignore! Please tell me why am I unable to ping one box from another? I am beginning to think that it is just a bad cable, though when I plug connector in, indicators on both NICs show it is OK.
PS I am very sorry for my poor english (need some practice ;-)
There is one more thing I would like to add. In winXP which is on the same machine where Redhat 8 is, when I plug the cable in windoze shows an icon notification. I don't know whether it means that cable is OK or not, but still I can not ping the boxes from each other.
So the question still remains. Please, can someone confirm that I still really need to change the cable?
Bloody windoze says it is OK and that was the main reason I believed the cable was good. But, I was very VERY surprised when I unplugged the cable and looked at how it was made, heh, the guys in the store just missed :-) and one wire (orange or #2 as it is shown here http://www.perfectdrivers.com/howto/crossover.html) is tied up with the blue and white one so the orange one was left unconnected. Ohhhh, that one mistake of the guys in the store and a bloody windoze icon notification keep me busy for a couple of days! ;-) Now I know the reason and can sleep calmly. He-he.
Something I've noticed ... are both your machines called "localhost" (as seen in your prompt) ... generally localhost is just a reference to the local ip address of 127.0.0.1 -- try changing the hostnames (to something different, and different from each other; such as "comp1" and "comp2") and trying again
I didn't mean change the listing of 127.0.0.1 to anything other than localhost; I mean that his computers' names appear to be "localhost" by looking at his prompt (the default Slackware install resembles [root@darkstar]# for example, with darkstar being the hostname). I'm saying if he's trying to "ping localhost" meaning the other computer, he's just going to end up pinging 127.0.0.1 -- The hostname should be different, which can be set with the "hostname" command and/or in /etc/hosts and /etc/HOSTNAME
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.