how to connect two machines?

I connect the RJ-45 cable between two machines.
On machine 1 I do ifconfig eth0 192.168.0.1
On machine 2 I do ifconfig eth0 192.168.0.2
At this point on machine 2
$ ping 192.168.0.1
should work and visa versa, but why not?
The Linux Ethernet HOWTO doesn't say.

Dan Jacobson wrote:
> I connect the RJ-45 cable between two machines.

try using a crossover cable:
http://www.homenethelp.com/web/expla...-crossover.asp


--
Let's not complicate our relationship
by trying to communicate with each other.

On 2005-07-22, johnny bobby bee <(E-Mail Removed)> wrote:
> Dan Jacobson wrote:
>> I connect the RJ-45 cable between two machines.
>
> try using a crossover cable:
> http://www.homenethelp.com/web/expla...-crossover.asp

....or use a switch or hub.

--keith

--
kkeller-(E-Mail Removed)
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
see X- headers for PGP signature information

Dan Jacobson wrote:

> I connect the RJ-45 cable between two machines.
> On machine 1 I do ifconfig eth0 192.168.0.1
> On machine 2 I do ifconfig eth0 192.168.0.2
> At this point on machine 2
> $ ping 192.168.0.1
> should work and visa versa, but why not?
> The Linux Ethernet HOWTO doesn't say.

Did you use a crossover cable? It's required for 10 & 100 Mb ethernet.

Dan Jacobson wrote:
> I connect the RJ-45 cable between two machines.
> On machine 1 I do ifconfig eth0 192.168.0.1
> On machine 2 I do ifconfig eth0 192.168.0.2
> At this point on machine 2
> $ ping 192.168.0.1
> should work and visa versa, but why not?
> The Linux Ethernet HOWTO doesn't say.

In order for this to work the cable must be a crossover cable, which is
wired differently than regular networking cables.

--
mail: teeuu at qwest dot net

On Sat, 23 Jul 2005 05:35:35 +0800, Dan Jacobson wrote:

> I connect the RJ-45 cable between two machines.
> On machine 1 I do ifconfig eth0 192.168.0.1
> On machine 2 I do ifconfig eth0 192.168.0.2
> At this point on machine 2
> $ ping 192.168.0.1
> should work and visa versa, but why not?
> The Linux Ethernet HOWTO doesn't say.

As has been said, use a crossover cable if you go directly from one to
another, usual network cables if you go through a router/hub.

Moreover, both machines must know what to do with the packets, so you
must set up routes to each other in the routing table. E.g. on
192.168.0.2 do something like

route add -host 192.168.0.1/32 eth0

etc.

On Sat, 23 Jul 2005 01:33:53 -0400, Amadeus W. M. wrote:

> On Sat, 23 Jul 2005 05:35:35 +0800, Dan Jacobson wrote:
>
>> I connect the RJ-45 cable between two machines.
>> On machine 1 I do ifconfig eth0 192.168.0.1
>> On machine 2 I do ifconfig eth0 192.168.0.2
>> At this point on machine 2
>> $ ping 192.168.0.1
>> should work and visa versa, but why not?
>> The Linux Ethernet HOWTO doesn't say.
>
> As has been said, use a crossover cable if you go directly from one to
> another, usual network cables if you go through a router/hub.
>
> Moreover, both machines must know what to do with the packets, so you
> must set up routes to each other in the routing table. E.g. on
> 192.168.0.2 do something like
>
> route add -host 192.168.0.1/32 eth0
>
> etc.

Oh, yeah, and try without a firewall first.

Tommy Willoughby wrote:

> In order for this to work the cable must be a crossover cable, which is
> wired differently than regular networking cables.

Except for gigabit.

Amadeus W. M. wrote:

> Moreover, both machines must know what to do with the packets, so you
> must set up routes to each other in the routing table. E.g. on
> 192.168.0.2 do something like
>
> route add -host 192.168.0.1/32 eth0

That shouldn't be necessary, as both computers are on the same subnet. When
both the source and destination, are on the same subnet, the computer uses
the sends the packets directly to the destination.

Dan Jacobson wrote:

> I connect the RJ-45 cable between two machines.
> On machine 1 I do ifconfig eth0 192.168.0.1
> On machine 2 I do ifconfig eth0 192.168.0.2
> At this point on machine 2
> $ ping 192.168.0.1
> should work and visa versa, but why not?
> The Linux Ethernet HOWTO doesn't say.

If /etc/sysctrl.conf includes
net/ipv4/icmp_echo_ignore_all=1
then the nic will not respond to a ping.