FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 01-22-2010, 06:32 PM
Rodolfo Medina
 
Default rsync with crossover cable connection

Michael Mohn <mailinglists@uberleet.de> writes:

> sorry for my post... i didn't look right... seems...
>
> network is still broken.


>From what do you see the network is broken?

Rodolfo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 06:52 PM
Rodolfo Medina
 
Default rsync with crossover cable connection

Michael Mohn <mailinglists@uberleet.de> writes:

> Am 22.01.2010 um 19:24:43 schrieb Rodolfo Medina:
>
>> 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?


Well, no. Should I install the ssh-server?

Rodolfo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 07:14 PM
Sven Joachim
 
Default rsync with crossover cable connection

On 2010-01-22 19:24 +0100, Rodolfo Medina wrote:

> Still needing your help:
>
> following the suggestion come from the list, I edited /etc/network/interfaces
> on the first pc as follows:
>
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
> address 192.168.0.1
> netmask 255.255.255.0
>
> , 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:
>
> # ifconfig
> eth0 Link encap:UNSPEC HWaddr 00-03-0D-53-25-5C-86-16-00-00-00-00-00-00-00-00

This is bad, it should look like the line from your other machine
instead.

What do you get from `ifconfig -a'?

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 07:25 PM
Rodolfo Medina
 
Default rsync with crossover cable connection

Sven Joachim <svenjoac@gmx.de> writes:

> On 2010-01-22 19:24 +0100, Rodolfo Medina wrote:
>
>> Still needing your help:
>>
>> following the suggestion come from the list, I edited /etc/network/interfaces
>> on the first pc as follows:
>>
>> auto eth0
>> allow-hotplug eth0
>> iface eth0 inet static
>> address 192.168.0.1
>> netmask 255.255.255.0
>>
>> , 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:
>>
>> # ifconfig
>> eth0 Link encap:UNSPEC HWaddr 00-03-0D-53-25-5C-86-16-00-00-00-00-00-00-00-00
>
> This is bad, it should look like the line from your other machine
> instead.
>
> What do you get from `ifconfig -a'?


Here's the output of `ifconfig -a':

# ifconfig -a
eth0 Link encap:UNSPEC HWaddr 00-03-0D-53-25-5C-86-16-00-00-00-00-00-00-00-00
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth1 Link encap:Ethernet HWaddr 00:03:0D:33:02:17
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:201 Base address:0xd800

lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ppp0 Link encap:Point-to-Point Protocol
inet addr:151.83.190.177 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1409 errors:38 dropped:0 overruns:0 frame:0
TX packets:1547 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:911548 (890.1 KiB) TX bytes:268897 (262.5 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


Rodolfo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 07:43 PM
Sven Joachim
 
Default rsync with crossover cable connection

On 2010-01-22 21:25 +0100, Rodolfo Medina wrote:

> Here's the output of `ifconfig -a':
>
> # ifconfig -a
> eth0 Link encap:UNSPEC HWaddr 00-03-0D-53-25-5C-86-16-00-00-00-00-00-00-00-00
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> eth1 Link encap:Ethernet HWaddr 00:03:0D:33:02:17
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:201 Base address:0xd800

It may be that eth1 is the right device. Can you please show the
contents of /etc/udev/rules.d/70-persistent-net.rules ?

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 08:02 PM
Rodolfo Medina
 
Default rsync with crossover cable connection

Sven Joachim <svenjoac@gmx.de> writes:

> It may be that eth1 is the right device. Can you please show the
> contents of /etc/udev/rules.d/70-persistent-net.rules ?


There is /etc/udev/rules.d/z25-persistent-net.rules, and here is its content:

# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.

# Firewire device 00030d53255c8616 (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:03:0d:53:25:5c:86:16", NAME="eth0"

# PCI device 0x1039:0x0900 (sis900)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:03:0d:33:02:17", NAME="eth1"



But, know what? I thought that eth1 might be the right one and replaced eth0
with eth1, and now... it works!! But only from the other pc onto this one, not
viceversa. Can you please suggest...?

Thanks
Rodolfo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 08:05 PM
Rodolfo Medina
 
Default rsync with crossover cable connection

Rodolfo Medina <rodolfo.medina@gmail.com> writes:

> Sven Joachim <svenjoac@gmx.de> writes:
>
>> It may be that eth1 is the right device. Can you please show the
>> contents of /etc/udev/rules.d/70-persistent-net.rules ?
>
> But, know what? I thought that eth1 might be the right one and replaced eth0
> with eth1, and now... it works!! But only from the other pc onto this one,
> not viceversa. Can you please suggest...?



I spoke to early! Now it does not work any more. What's that?!

Rodolfo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 08:46 PM
Sven Joachim
 
Default rsync with crossover cable connection

On 2010-01-22 22:02 +0100, Rodolfo Medina wrote:

> Sven Joachim <svenjoac@gmx.de> writes:
>
>> It may be that eth1 is the right device. Can you please show the
>> contents of /etc/udev/rules.d/70-persistent-net.rules ?
>
>
> There is /etc/udev/rules.d/z25-persistent-net.rules, and here is its content:

Are you still running etch?

> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, probably run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single line.
> # MAC addresses must be written in lowercase.
>
> # Firewire device 00030d53255c8616 (ohci1394)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:03:0d:53:25:5c:86:16", NAME="eth0"

Ethernet via firewire, or what is that?

> # PCI device 0x1039:0x0900 (sis900)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:03:0d:33:02:17", NAME="eth1"

This looks like a network card, fine.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 08:48 PM
Sven Joachim
 
Default rsync with crossover cable connection

On 2010-01-22 22:05 +0100, Rodolfo Medina wrote:

>> But, know what? I thought that eth1 might be the right one and replaced eth0
>> with eth1, and now... it works!! But only from the other pc onto this one,
>> not viceversa. Can you please suggest...?
>
>
>
> I spoke to early! Now it does not work any more. What's that?!

What does not work? Can you ping one host from the other? Don't bother
with ssh and rsync yet.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 09:06 PM
Rodolfo Medina
 
Default rsync with crossover cable connection

Sven Joachim <svenjoac@gmx.de> writes:

> On 2010-01-22 22:05 +0100, Rodolfo Medina wrote:
>
>>> But, know what? I thought that eth1 might be the right one and replaced
>>> eth0 with eth1, and now... it works!! But only from the other pc onto this
>>> one, not viceversa. Can you please suggest...?
>>
>>
>>
>> I spoke to early! Now it does not work any more. What's that?!
>
> What does not work? Can you ping one host from the other? Don't bother
> with ssh and rsync yet.


ssh and rsync from computer B complain the Network is unreachable, whereas an
hour ago I copied a directory from B to A! The same with `ping 192.186.0.1'
from pc B.

What do you suggest? I'm running Etch on A and Lenny on B. Do you think it's
a hardware problem (cable or ethernet port)?

Thanks!
Rodolfo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 09:33 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org