WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 247] rsh failed between domUs on different machines

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 247] rsh failed between domUs on different machines
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 22 Sep 2005 15:12:31 +0000
Delivery-date: Thu, 22 Sep 2005 15:12:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=247





------- Additional Comments From hien1@xxxxxxxxxx  2005-09-22 15:12 -------
More info about network setup:

I can ping from the 2nd domU to 1st domU:

[root@x335-hien1-vm4 tmp]# traceroute 9.3.189.241
traceroute to 9.3.189.241 (9.3.189.241), 30 hops max, 38 byte packets
 1  x335-hien1 (10.8.1.1)  0.103 ms  0.054 ms  0.076 ms
 2  x335-sles9-vm1 (9.3.189.241)  0.228 ms  0.183 ms  0.182 ms

[root@x335-hien1-vm4 tmp]# ip addr show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether aa:00:00:17:12:6d brd ff:ff:ff:ff:ff:ff
    inet 10.8.1.2/24 brd 10.8.1.255 scope global eth0
    inet 10.8.1.2/8 brd 10.255.255.255 scope global eth0

[root@x335-hien1-vm4 tmp]# ip route show
9.3.189.0/24 via 10.8.1.1 dev eth0
10.8.1.0/24 dev eth0  proto kernel  scope link  src 10.8.1.2
169.254.0.0/16 dev eth0  scope link
10.0.0.0/8 dev eth0  proto kernel  scope link  src 10.8.1.2
default via 10.8.1.1 dev eth0
-------------
Also I can ping (or ssh to) from 1st domU to 2nd domU:

x335-sles9-vm1:~ # ping x335-hien1-vm4
PING x335-hien1-vm4.ltc.austin.ibm.com (10.8.1.2) 56(84) bytes of data.
64 bytes from x335-hien1-vm4.ltc.austin.ibm.com (10.8.1.2): icmp_seq=1 ttl=63
time=0.194 ms
64 bytes from x335-hien1-vm4.ltc.austin.ibm.com (10.8.1.2): icmp_seq=2 ttl=63
time=0.245 ms
64 bytes from x335-hien1-vm4.ltc.austin.ibm.com (10.8.1.2): icmp_seq=3 ttl=63
time=0.232 ms
 
--- x335-hien1-vm4.ltc.austin.ibm.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.194/0.223/0.245/0.027 ms

x335-sles9-vm1:~ # ip addr show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether aa:00:00:17:12:6e brd ff:ff:ff:ff:ff:ff
    inet 9.3.189.241/24 brd 9.3.189.255 scope global eth0
    inet6 fe80::a800:ff:fe17:126e/64 scope link
       valid_lft forever preferred_lft forever
5: sit0: <NOARP> mtu 1480 qdisc noqueue
    link/sit 0.0.0.0 brd 0.0.0.0

x335-sles9-vm1:~ # ip route show
9.3.189.0/24 dev eth0  proto kernel  scope link  src 9.3.189.241
10.8.1.0/24 via 9.3.189.225 dev eth0
10.8.1.0/24 dev eth0  scope link
169.254.0.0/16 dev eth0  scope link
127.0.0.0/8 dev lo  scope link
default via 9.3.189.1 dev eth0




-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>