If the answer is "destination host unreachable", then probably the problem
is not the NIC neither the driver.
In order to successfully communicate (without routers), two machines must
join the same network. In other words, if machine A has an internet address
192.168.1.y, and if machine B has an internet address 192.168.2.x, they
will not be able to talk one with another because they belong to different
network, even being in the same physical hub, or crossover cable etc. You
will receive exactly this error: "destination host unreachable". So, if
this is your case, just change the IP addresses to match the same network.
Other tip: avoid using the "zeroes" addresses, because they are reserved
for the network. So, do not use 192.168.0.2, but 192.168.1.2.
After configuring the IPs for the two boxes, you do not have to configure
routes. I have this situation in my lab: two boxes linked through a cross
over cable, and it runs without any further configuration.
Regards,
Hime
At 19:32 03/01/00 +0000, Steve Maughan wrote:
>[My first post to this list... Hi all!]
>
>I've got a little problem with my 3c509. I've asked around on
>comp.os.linux.networking and other newsgroups as well as people on IRC
>but so far I've had no luck with fixing the problem.
>
>The situation is I have two RH 5.2 (kernel 2.2.10) linux boxes. They
>each have a 3com 3c509 ISA card in them. I know the cards do work and
>the RJ45 crossover cable connecting them is wired correctly and works
>properly. But when I try to get my two machine to connect, nothing much
>happens.
>
>The problem seems to be with Machine A. If I ping machine A from Machine
>B, machine B reports "destination host unreachable". But if I run
>"ifconfig", on Machine A I can see that Machine A is recieving the
>packets and is also sending another packet. I assume this other packet
>to be the ping response packet. But for some reason, the packet doesn't
>get to Machine B.
>
>I figure it is some sort of routing problem. I compiled the drivers into
>the kernel on each system and I set up the link using "ifconfig eth0
>192.168.0.2 netmask 255.255.255.0 up" and "route add -net 192.168.0.0
>netmask 255.255.255.0 dev eth0". The output from "ifconfig" and "netstat
>-rn" is correct, so the problem doesn't seem to be there - could it be
>lower level?
>
>If anyone has any ideas on why this isn't working, could you pass them
>on?
>
>Thanks
>
>--
>Steve Maughan
>
> Don't run away from your problems
> Riding is much faster.
>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-net" in
>the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
