>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.
Actually, adding a simple route telling machine A to use it's interface on
network, for example, 10.10.1 to access network 10.10.2 will accomplish the
same. For example, on a machine with IP address 10.10.1.1, to communicate
with a machine connected to the same hub (switch with properly configured
VLAN, etc...) use the command: (don't quote me on this - I'm doing it off
the top of my head)
route add -net 10.10.2.0 gw 10.10.1.1
You would do the same on the machine with an ip address of 10.10.2.1 to
allow it to access machine 10.10.1.1:
route add -net 10.10.1.0 gw 10.10.2.1
This isn't optimal, but is necessary in some circumstances to simplify test
beds.
>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.
Actually, zero can be used in octets B and C, but not A or D. Therefore
"10.0.0.1" would be legal as would "10.0.1.1" and "10.1.10.1", however
"0.10.10.1" and "10.10.1.0" would not be vailid host ip addresses.
>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.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
