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] networking confusion

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] networking confusion
From: <JDuncan@xxxxxxxxxxxxxxxx>
Date: Tue, 14 Jul 2009 16:17:39 -0400
Delivery-date: Tue, 14 Jul 2009 13:18:38 -0700
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoEwCJj5m5Z5QFsQV+CEoVuqzsH7w==
Thread-topic: networking confusion

I know it’s hard to believe, with all of the amazingly contradictory information out on the internet, but after 2 days of reading and testing I’m still not 100% with getting my Xen environment networked properly.

 

I have my dom0 setup and it’s ALMOST happy.  It can speak on the 2 needed networks. 

 

10.175.8.0/21 is an internal network

10.150.8.0/24 is a natted network to the outside

 

eth0      Link encap:Ethernet  HWaddr 00:19:B9:F2:1B:C3

          inet addr:10.175.8.158  Bcast:10.175.15.255  Mask:255.255.248.0

          inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:591562 errors:0 dropped:0 overruns:0 frame:0

          TX packets:210322 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:855948093 (816.2 MiB)  TX bytes:17183183 (16.3 MiB)

          Interrupt:16 Memory:f8000000-f8012100

 

eth1      Link encap:Ethernet  HWaddr 00:19:B9:F2:1B:C5

          inet addr:10.150.8.158  Bcast:10.150.8.255  Mask:255.255.255.0

          inet6 addr: fe80::219:b9ff:fef2:1bc5/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:5327 errors:0 dropped:0 overruns:0 frame:0

          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:367839 (359.2 KiB)  TX bytes:21044 (20.5 KiB)

 

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:21 errors:0 dropped:0 overruns:0 frame:0

          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:2000 (1.9 KiB)  TX bytes:2000 (1.9 KiB)

 

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:12707 errors:0 dropped:0 overruns:0 frame:0

          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:861593 (841.3 KiB)  TX bytes:23350 (22.8 KiB)

          Interrupt:16 Memory:f4000000-f4012100

 

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:200 errors:0 dropped:0 overruns:0 frame:0

          TX packets:5327 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:21044 (20.5 KiB)  TX bytes:367839 (359.2 KiB)

 

vif7.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:370 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1860 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:32

          RX bytes:17297 (16.8 KiB)  TX bytes:120860 (118.0 KiB)

 

virbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0

          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:189755 errors:0 dropped:0 overruns:0 frame:0

          TX packets:555037 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:10965164 (10.4 MiB)  TX bytes:824668323 (786.4 MiB)

 

xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:5069 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:287789 (281.0 KiB)  TX bytes:0 (0.0 b)

 

I currently have one test Guest dom set up, mgixentest.  It’s config file looks as follows:

 

# cat /etc/xen/mgixentest

name = "mgixentest"

uuid = "8eb40858-96b7-baad-1390-d44c01342e43"

maxmem = 512

memory = 512

vcpus = 1

bootloader = "/usr/bin/pygrub"

>

>

>

vfb = [  ]

disk = [ "file:/var/lib/xen/images/mgixentest-disk0,xvda,w" ]

vif = [ "mac=00:16:3e:7f:1e:33,bridge=virbr0" ]

 

My goal:

 

1.       Each guest domN will be assigned an IP on either 1 or both of the above networks (10.175.x.x or 10.150.x.x).

2.       Each guest will be reaching from within the 10.175.8.0/21 network to and from other machines.

3.       Each guest (if so supplied) will have external access to the internet via the 10.150.8.0/24 network

Can someone please get me going down the correct path?

Thanks for any insight.

 

Jamie Duncan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] networking confusion, JDuncan <=