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] Multiple physical interfaces problems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Multiple physical interfaces problems
From: Andrew McGlashan <andrew.mcglashan@xxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 13 Mar 2011 04:26:30 +1100
Delivery-date: Sat, 12 Mar 2011 09:28:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Affinity Vision Australia Pty Ltd
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (Windows/20100228)
Hi,

I'm running the following on Debian stable (squeeze);

 libxenstore3.0                      4.0.1-2
 linux-image-2.6.32-5-xen-amd64      2.6.32-30
 xen-hypervisor-4.0-amd64            4.0.1-2
 xen-tools                           4.2-1
 xen-utils-4.0                       4.0.1-2
 xen-utils-common                    4.0.0-1
 xenstore-utils                      4.0.1-2Xen


Dom0 can communicate perfectly well with two distinct networks via two physical Ethernet ports, one going to any Internet location, the other routing to local networks.


I've got this is my /etc/xen/xend-config.sxp

  (network-script 'network-bridge-wrapper antispoof=yes')


And here is the script:

#  cat network-bridge-wrapper
#!/bin/bash
/etc/xen/scripts/network-bridge "$@" netdev=eth0
/etc/xen/scripts/network-bridge "$@" netdev=eth1



Dom0

Destination  Gateway       Genmask       Flags  MSS Window irtt Iface
192.168.1.0  0.0.0.0       255.255.255.0 U        0 0         0 eth0
192.168.2.0  0.0.0.0       255.255.255.0 U        0 0         0 eth1
192.168.3.0  192.168.2.1   255.255.255.0 UG       0 0         0 eth0
0.0.0.0      192.168.1.254 0.0.0.0       UG       0 0         0 eth1


DomU

Destination  Gateway       Genmask       Flags  MSS Window irtt Iface
192.168.1.0  0.0.0.0       255.255.255.0 U        0 0         0 eth1
192.168.2.0  0.0.0.0       255.255.255.0 U        0 0         0 eth0
192.168.3.0  192.168.2.1   255.255.255.0 UG       0 0         0 eth1
0.0.0.0      192.168.1.254 0.0.0.0       UG       0 0         0 eth0



Dom0

eth0  Link encap:Ethernet  HWaddr 00:11:25:8e:35:5e
      inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
      inet6 addr: fe80::211:25ff:fe8e:355e/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1  Link encap:Ethernet  HWaddr 00:11:25:8e:35:5f
      inet addr:192.168.2.9  Bcast:192.168.2.255  Mask:255.255.255.0
      inet6 addr: fe80::211:25ff:fe8e:355f/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth2  Link encap:Ethernet  HWaddr 00:0e:0c:76:4a:08
      BROADCAST MULTICAST  MTU:1500  Metric:1

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

peth0 Link encap:Ethernet  HWaddr 00:11:25:8e:35:5e
      inet6 addr: fe80::211:25ff:fe8e:355e/64 Scope:Link
      UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

peth1 Link encap:Ethernet  HWaddr 00:11:25:8e:35:5f
      inet6 addr: fe80::211:25ff:fe8e:355f/64 Scope:Link
      UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

vif2.0 Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
       inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
       UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

vif2.1 Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
       inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
       UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1



DomU

eth0  Link encap:Ethernet  HWaddr 00:16:3e:24:79:d6
      inet addr:192.168.1.201  Bcast:192.168.1.255  Mask:255.255.255.0
      inet6 addr: fe80::216:3eff:fe24:79d6/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1  Link encap:Ethernet  HWaddr 00:16:3e:24:79:d7
      inet addr:192.168.2.201  Bcast:192.168.2.255  Mask:255.255.255.0
      inet6 addr: fe80::216:3eff:fe24:79d7/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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


Dom0 & DomU have static IP assignment for each interface.


Both machines (Dom0 and DomU) have an "up" route added for a local network accessible via another local network.



Network extract in DomU cfg file:

vif         = [
                  'mac=00:16:3E:24:79:D6, bridge=eth0',
                  'mac=00:16:3E:24:79:D7, bridge=eth1',
              ]



What am I missing here?



I need DomU to act just like Dom0, that is to be able to route and communicate anywhere.



Thanks.

--
Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


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

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