[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] networking problems on second DomU IP / bridge on Dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Niels Dettenbach <nd@xxxxxxxxxxxx>
  • Date: Tue, 01 Nov 2011 09:50:53 +0100
  • Delivery-date: Tue, 01 Nov 2011 01:52:25 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Dear all,


since several days i run Xen 4.1.2 Dom0 (Gentoo Linux x86_64) with several 
Gentoo Linux (x86_64) and a "historic" NetBSD 5.99.39 (x86) DomU (guests) - 
bridged setup.

I've set up a second bridge on Dom0 and gave each DomU a second network 
interface connected to this bridge with a private subnet ip. The private 
subnet has no gateway. Connectivity between the Linux hosts (DomU -> DomU and 
DomU -> Dom0) works as expected, but communication from/to the NetBSD Domu did 
not work properly with "crazy" effects:

I can ping (!) from / to the NetBSD DomU without packet loss, but if i try to 
open any TCP connection (ssh, http, smtp) the connection just "hangs".


examples:
========
- If i try to connect a SMTP service at the DomU i get the SMTP banner and two 
lines out, can put in i.e. QUIT or help but nothing more happens.

- If i try i.e. mysqlshow against the NetBSD DomU i get an answer if the 
output is short - on longer requests i get a auth package error.


Alternatively i tried to set up a second (private) subnet as aliases on the 
first interfaces / bridge with same effect.

The interesting thing is that exactly these had worked properly with an older 
Dom0 setup with XEN 3.4.2 and 2.6.34-xen-r2 x86_64 kernel (Gentoo Linux).

Here is the config of the second netbsd DomU interface:

--- snip ---
xennet1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 
1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 00:0c:6e:40:38:b2
        inet 10.10.10.2 netmask 0xffffff00 broadcast 10.10.10.255
        inet6 fe80::20c:6eff:fe40:38b2%xennet1 prefixlen 64 scopeid 0x3
--- snap ---

And here the bridge configuration:

--- snip ---
xen ~ # brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.001cc441f06a       no              eth1
                                                        vif1.0
                                                        vif10.0
                                                        vif4.0
                                                        vif5.0
xenint0         8000.001cc441f07e       no              eth0
                                                        vif10.1
                                                        vif4.1 (-> NetBSD 
DomU)


xen ~ # ifconfig xenint0
xenint0   Link encap:Ethernet  HWaddr 00:1c:c4:41:f0:7e  
          inet addr:10.10.10.1  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::fc20:77ff:fee7:5fd6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2103 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3486 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:124835 (121.9 KiB)  TX bytes:297380 (290.4 KiB)
--- snap ---

Is this a problem of the NetBSD DomU build or the newer Xen 4.1.2 software 
version?

Any help or hint is welcome here?


Many thanks in advance.
best regards,


Niels.
-- 
---
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com/

Attachment: signature.asc
Description: This is a digitally signed message part.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.