I''ve got this straight issue with xenbr0 working and internal-br0 not
working between dom0 and a domU on the same machine. Also a domU on a
different machine works to that domU.
[nic@wuwei:/etc/xen] ssh rails.plumtree.co.nz
Linux rails 2.6.12.6-xenU #3 SMP Sun Jan 22 12:05:59 NZDT 2006 x86_64 GNU/Linux
....
Last login: Thu Feb 16 17:04:06 2006 from 131.203.110.4
nic@rails:~$ logout
[nic@wuwei:/etc/xen] ping rails.internal
PING rails.internal (10.X.0.103) 56(84) bytes of data.
64 bytes from rails.internal (10.X.0.103): icmp_seq=1 ttl=64 time=0.049 ms
64 bytes from rails.internal (10.X.0.103): icmp_seq=2 ttl=64 time=0.024 ms
--- rails.internal ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.024/0.036/0.049/0.013 ms
[nic@wuwei:/etc/xen] ssh rails.plumtree.co.nz
[nic@wuwei:/etc/xen] ssh -v rails.internal
OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to rails.internal [10.X.0.103] port 22.
debug1: Connection established.
debug1: identity file /home/nic/.ssh/identity type -1
debug1: identity file /home/nic/.ssh/id_rsa type -1
debug1: identity file /home/nic/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version
OpenSSH_3.8.1p1 Debian-8.sarge.4
debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4
debug1: SSH2_MSG_KEXINIT sent
Connection stalls here.
Whereas, from another physical machine (running 2.0 still):
[nic@shell:~] ssh rails.internal
Linux rails 2.6.12.6-xenU #3 SMP Sun Jan 22 12:05:59 NZDT 2006 x86_64 GNU/Linux
...
nic@rails:~$ logout
Connection to rails.internal closed.
Its even worse from the domU to the dom0:
nic@rails:~$ ssh -v wuwei.internal
OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to wuwei.internal [10.X.0.252] port 22.
debug1: Connection established.
debug1: identity file /home/nic/.ssh/identity type -1
debug1: identity file /home/nic/.ssh/id_rsa type -1
debug1: identity file /home/nic/.ssh/id_dsa type -1
Tcpdump hasn''t got me anywhere.
[nic@wuwei:/etc/xen] brctl show
bridge name bridge id STP enabled interfaces
internal-br 8000.00093d1349bf yes eth1
vif10.1
xenbr0 8000.feffffffffff no peth0
vif0.0
vif10.0
[nic@wuwei:~] cat /etc/network/interfaces
...
auto internal-br
iface internal-br inet static
address 10.X.0.252
netmask 255.255.0.0
network 10.X.0.0
broadcast 10.X.255.255
bridge_ports eth1
bridge_fd 0
bridge_hello 1
bridge_stp on
nic@rails:~$ cat /etc/network/interfaces
...
auto eth1
iface eth1 inet static
address 10.X.0.103
netmask 255.255.0.0
network 10.X.0.0
broadcast 10.X.255.255
[nic@wuwei:~] cat /etc/xen/rails
vif = [ ''mac=aa:00:00:00:01:03, bridge=xenbr0'',
''mac=aa:00:00:01:01:03, bridge=internal-br'' ]
Thoughts?
--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Nicholas Lee
2006-Feb-16 04:31 UTC
[Xen-users] Re: internal-br vs xenbr0. networking issue
Sorry forgot to include this for the dom0. Xen version 3.0.0 (nic@localdomain) (gcc version 3.3.5 (Debian 1:3.3.5-13)) Sun Jan 22 12:04:30 NZDT 2006 Latest ChangeSet: Tue Dec 13 07:47:47 2005 +0100 8270:4ad23e798798 [nic@wuwei:~] uname -a Linux wuwei 2.6.12.6-xen0 #3 Sun Jan 22 12:04:56 NZDT 2006 x86_64 GNU/Linux SunFire v20z with debian/sarge. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Markus Hochholdinger
2006-Feb-18 23:05 UTC
Re: [Xen-users] internal-br vs xenbr0. networking issue
Hi, Am Donnerstag, 16. Februar 2006 05:24 schrieb Nicholas Lee:> I''ve got this straight issue with xenbr0 working and internal-br0 not > working between dom0 and a domU on the same machine. Also a domU on a > different machine works to that domU.sounds to me like a similar problem i had have. Just check arp! Each layer two deivce must have a unique mac address. Check if you have not specified one mac address twice. -- greetings eMHa _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nicholas Lee
2006-Feb-19 10:07 UTC
Re: [Xen-users] internal-br vs xenbr0. networking issue
On 19/02/06, Markus Hochholdinger <Markus@hochholdinger.net> wrote:> > sounds to me like a similar problem i had have. Just check arp! Each layer two > deivce must have a unique mac address. Check if you have not specified one > mac address twice.I had that problem before when I specified a 13 digit MAC address. So that was one of the things I checked a copule times. Plus since its a (mulitple) bridge, duplicate MACs would cause the same problem for all systems on the same subnet. Ping would also have some issues. No I think its something wrong on the tcp layer. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users