, and on the second the same but with `192.168.0.2' in place of `192.168.0.1'.
Then I did `/etc/init.d/networking restart' on both, and `ifconfig' on the
first gives:
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
01-22-2010, 05:38 PM
Michael Mohn
rsync with crossover cable connection (was: Synchronize two computers)
Am 22.01.2010 um 19:24:43 schrieb Rodolfo Medina:
> Johannes Wiedersich <johannes@physik.blm.tu-muenchen.de> writes:
>
>> Check and possibly post the output of "/sbin/ifconfig"
>>
>> "ssh -v user@192.168.0.2" might also help to diagnose your problem.
>
>
>
> Still needing your help:
>
> following the suggestion come from the list, I edited /etc/network/interfaces
> on the first pc as follows:
>
{ network ok }
> But rsync does not seem to work between the two. From first pc:
>
> $ rsync -vr --delete test1 192.168.0.2:/home/rodolfo
>
> , but nothing happens.
>
what do you want to accomplish with that command?
do you have the ssh-server installed on both hosts and does it work?
bye,
Michael.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
01-22-2010, 05:51 PM
"Boyd Stephen Smith Jr."
rsync with crossover cable connection (was: Synchronize two computers)
On Friday 22 January 2010 12:24:43 Rodolfo Medina wrote:
> Johannes Wiedersich <johannes@physik.blm.tu-muenchen.de> writes:
> > Check and possibly post the output of "/sbin/ifconfig"
> >
> > "ssh -v user@192.168.0.2" might also help to diagnose your problem.
>
> Still needing your help:
> The `ping' command from first machine:
>
> $ ping 192.168.0.2
> PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
>
> --- 192.168.0.2 ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4000ms
>
> , and analogously from second.
Most likely, the two computers still can't send packets to each other. Make
sure you are using the correct type of cable. You'll need a crossover cable
if neither side is a 1Gbit card. You should probably use a crossover cable
anyway.
Make sure the cable runs to/from the physical port that is eth0 on both side.
There could be some routing issues, too. But that would only be if one of
your other ports was using a 192.168.0.x address as well, or if you've got
some routing customizations.
Until you can get the pings to work ("X packets transmitted, X received, 0%
packet loss") any other sort of network protocol is not going to work either.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
01-22-2010, 05:52 PM
Michael Mohn
rsync with crossover cable connection (was: Synchronize two computers)
Am 22.01.2010 um 19:51:00 schrieb Boyd Stephen Smith Jr.:
> On Friday 22 January 2010 12:24:43 Rodolfo Medina wrote:
>> Johannes Wiedersich <johannes@physik.blm.tu-muenchen.de> writes:
>>> Check and possibly post the output of "/sbin/ifconfig"
>>>
>>> "ssh -v user@192.168.0.2" might also help to diagnose your problem.
>>
>> Still needing your help:
>> The `ping' command from first machine:
>>
>> $ ping 192.168.0.2
>> PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
>>
>> --- 192.168.0.2 ping statistics ---
>> 5 packets transmitted, 0 received, 100% packet loss, time 4000ms
>>
>> , and analogously from second.
>
> Most likely, the two computers still can't send packets to each other. Make
> sure you are using the correct type of cable. You'll need a crossover cable
> if neither side is a 1Gbit card. You should probably use a crossover cable
> anyway.
>
> Make sure the cable runs to/from the physical port that is eth0 on both side.
>
> There could be some routing issues, too. But that would only be if one of
> your other ports was using a 192.168.0.x address as well, or if you've got
> some routing customizations.
>
> Until you can get the pings to work ("X packets transmitted, X received, 0%
> packet loss") any other sort of network protocol is not going to work either.
sorry for my post... i didn't look right... seems...
network is still broken.
sorry,
bye.
Michael.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
rsync with crossover cable connection (was: Synchronize two computers)
