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

[Xen-users] domU to domU bridge - vif being created in dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ben Holt" <beanjammin@xxxxxxxxx>
  • Date: Sat, 29 Sep 2007 16:32:49 -0700
  • Delivery-date: Sat, 29 Sep 2007 16:33:41 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TyD1uKQOj+Fp8k1Xix9gsYWLs6PrEIdQaP/paDqqpcfHFdmbAdFdZFsC94HMC0pHizSo3cRn4oZwzqaQbKI2nlH3FIR4WzbnnfyA4uYx4EISUWO6DzNuLxREIzWSLcsYAdf40+2m4+fQhWTzcDIQAhARL8bYNRMp1FuDid/xqrI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

I am attempting to create a virtual network using a bridge from one
domU (firewall) to another (inetserver), however when inetserver is
started the corresponding vif is created in dom0 and not the firewall
domU.

I have been following the example given here:
http://lists.xensource.com/archives/html/xen-users/2005-07/msg00558.html.

My understanding was that by configuring the firewall domU with
netif=1 and the inetserver domU with vif = [ 'mac=aa:00:02:08:01:12',
'backend=firewall' ] the vif created when inetserver is started would
appear on firewall and could be bound to its dmz bridge, however it is
appearing on dom0 instead.  Any pointers on where I have gone wrong
would be greatly appreciated.

Many thanks,

- Ben


My specifics:

dom0 - debian etch, xen 3.0.3-1

domU (firewall)
- debian etch
- same kernel as dom0
- NICs (2) hidden from dom0
- bridge named dmz created on boot with 10.8.103.254 as ip
- uses the following config:

#
# Configuration file for the Xen instance fileserver, created on
# 20 September, 2007.
#


#
#  Kernel + memory size
#
kernel  = '/boot/vmlinuz-2.6.18-5-xen-686'
ramdisk = '/boot/initrd.img-2.6.18-5-xen-686'

memory  = '128'


#
#  Disk device(s).
#
root    = '/dev/sda4 ro'

disk    = [ 'phy:VM/firewall_asterisk-swap,sda1,w',
'phy:VM/firewall_asterisk-tmp,sda2,w',
'phy:VM/firewall_asterisk-var,sda3,w',
'phy:VM/firewall_asterisk-root,sda4,w' ]

#
#  Hostname
#
name    = 'firewall'


#
#  Networking
#
netif   = 1

#
# PCI device passthrough
#
pci    = [ '01,06,0', '01,04,0' ]

#
#  Behaviour
#
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'
restart     = 'onreboot'



/sbin/ifconfig on firewall is:
dmz       Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:10.8.103.254  Bcast:10.8.103.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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:846 (846.0 b)

eth0      Link encap:Ethernet  HWaddr 00:80:C6:F7:38:A3
          inet addr:192.168.3.12  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::280:c6ff:fef7:38a3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:109 errors:0 dropped:0 overruns:0 frame:0
          TX packets:161 errors:0 dropped:0 overruns:0 carrier:0
          collisions:20 txqueuelen:1000
          RX bytes:13288 (12.9 KiB)  TX bytes:40262 (39.3 KiB)
          Interrupt:16 Base address:0x9400

eth1      Link encap:Ethernet  HWaddr 00:11:2F:75:07:67
          inet addr:10.8.101.254  Bcast:10.8.101.255  Mask:255.255.255.0
          inet6 addr: fe80::211:2fff:fe75:767/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:346 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:36277 (35.4 KiB)  TX bytes:812 (812.0 b)
          Interrupt:17

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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:896 (896.0 b)  TX bytes:896 (896.0 b)




domU (inetserver)
- debian etch
- same kernel as dom0
- eth0 started on boot with ip 10.8.103.1 with 10.8.103.254 as gateway
- uses the following config:

#
# Configuration file for the Xen instance inetserver, created on
# 29 September, 2007.
#

import time
time.sleep(3)


#
#  Kernel + memory size
#
kernel  = '/boot/vmlinuz-2.6.18-5-xen-686'
ramdisk = '/boot/initrd.img-2.6.18-5-xen-686'

memory  = '128'


#
#  Disk device(s).
#
root    = '/dev/sda4 ro'

disk    = [ 'phy:VM/inetserver-swap,sda1,w',
'phy:VM/inetserver-tmp,sda2,w', 'phy:VM/inetserver-var,sda3,w',
'phy:VM/inetserver-root,sda4,w' ]

#
#  Hostname
#
name    = 'inetserver'


#
#  Networking
#
vif = [ 'mac=aa:00:02:08:01:12', 'backend=firewall' ]

#
#  Behaviour
#
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

_______________________________________________
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®.