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-users

[Xen-users] Dom0 and DomU can connect only to local network

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Dom0 and DomU can connect only to local network
From: Toshinao Ishii <ishii.toshinao@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 31 Jan 2007 20:14:37 +0900
Delivery-date: Wed, 31 Jan 2007 03:15:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello.

I'd appreciate comments to solve the following problem.

The problem is that Dom0 as well as DomU can communicate only to
the machines in localnetwork. One strange status of Dom0 is that
there are two set of lines, one for eth0 and the other for xenbr0, are
shown by `netstat -r`.


The hardware is IBM System x3650 which has two Broadcom NetXtreme II
BCM5708 1000Base-T network interfaces. OS is Debian etch with its xen
packages.

  linux-image-2.6.18-3-xen-amd64
  linux-modules-2.6.18-3-xen-amd64
  xen-hypervisor-3.0.3-1-amd64
  xen-tools
  xen-utils-3.0.3-1
  xen-utils-common
  bridge-utils

Network related lines in /etc/xen/xend-config.sxp are like the following.

  (network-script 'network-bridge bridge=xenbr0 netdev=eth0')
  #(network-script network-dummy)
  (vif-script vif-bridge)

Debian network interface setting (/etc/network/interfaces) of Dom0 is like
the following.

  auto lo
  iface lo inet loopback

  # The primary network interface
  auto xenbr0
  iface xenbr0 inet static
        address 10.140.2.84
        netmask 255.255.254.0
        network 10.140.1.0
        broadcast 10.140.2.255
        gateway 10.140.2.254
        bridge_ports eth0

The last part shows the network states of Dom0. Notice that we have network of 23bit mask and eth0 have inet addr 10.140.1.23, which is one of the dhcp server prividing address and it is not specified (as far as I know) anywhere in Dom0.

Is it necessary to have one IP address for eth0 and another for xenbr0 ?
If not, how can one to stop eth0 to have IP address ?

Again, I appreciate any comments for solving this problem.

Thank you.

--- ici


  # xm list
Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 4007 2 r----- 24.1

  # netstat -r
  Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface localnet * 255.255.254.0 U 0 0 0 xenbr0 localnet * 255.255.254.0 U 0 0 0 eth0
stops several seconds
default 10.140.1.254 0.0.0.0 UG 0 0 0 eth0 default 10.140.1.254 0.0.0.0 UG 0 0 0 xenbr0

  # brctl show
  bridge name     bridge id               STP enabled     interfaces
  xenbr0          8000.00145e18c59f       no              eth0

  # ifconfig
  eth0      Link encap:Ethernet  HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.1.23 Bcast:10.140.2.255 Mask: 255.255.254.0
            inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:5392 errors:0 dropped:0 overruns:0 frame:0
            TX packets:1431 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:809942 (790.9 KiB)  TX bytes:230888 (225.4 KiB)
            Interrupt:16 Memory:ce000000-ce011100
  eth1      Link encap:Ethernet  HWaddr 00:14:5E:18:C5:A1
            UP 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:17 Memory:ca000000-ca011100

  lo        Link encap:Local Loopback
            inet addr:127.0.0.1  Mask:255.0.0.0
            inet6 addr: ::1/128 Scope:Host
            UP LOOPBACK RUNNING  MTU:16436  Metric:1
            RX packets:570 errors:0 dropped:0 overruns:0 frame:0
            TX packets:570 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0
            RX bytes:53824 (52.5 KiB)  TX bytes:53824 (52.5 KiB)
  xenbr0    Link encap:Ethernet  HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.2.84 Bcast:10.140.2\.255 Mask: 255.255.254.0
            inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:5282 errors:0 dropped:0 overruns:0 frame:0
            TX packets:1357 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0
            RX bytes:702528 (686.0 KiB)  TX bytes:215701 (210.6 KiB)

  # ipaddr list
  1: lo: <LOOPBACK,UP,10000> 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: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
      link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
      inet 10.140.1.23/23 brd 10.140.1.255 scope global eth0
      inet6 fe80::214:5eff:fe18:c59f/64 scope link
         valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
      link/ether 00:14:5e:18:c5:a1 brd ff:ff:ff:ff:ff:ff
  4: sit0: <NOARP> mtu 1480 qdisc noop
      link/sit 0.0.0.0 brd 0.0.0.0
  5: xenbr0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
      link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
      inet 10.140.2.84/23 brd 10.140.1.255 scope global xenbr0
      inet6 fe80::214:5eff:fe18:c59f/64 scope link
         valid_lft forever preferred_lft forever
  6: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  7: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
  8: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  9: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
  10: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  11: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
  12: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  13: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
      link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  # xm create Dom1.cfg
  ...

  # xm list
Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 4007 2 r----- 27.2 Dom1 2 1024 1 - b---- 1.

  # brctl show
  bridge name     bridge id               STP enabled     interfaces
  xenbr0          8000.00145e18c59f       no              eth0
                                                          vif2.0






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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Dom0 and DomU can connect only to local network, Toshinao Ishii <=