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

[Xen-users] xen and wireless domUs


  • To: "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "john maclean" <jayeola@xxxxxxxxx>
  • Date: Sun, 3 Jun 2007 00:57:31 +0000
  • Delivery-date: Sat, 02 Jun 2007 17:55:59 -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=JUUB3pF8bGB94Ki9j62z93/COkLkFkRjIF6NAHcIm7Ifws/SZ/xVi5SN9oYvNJuzx3/L3rMOUX5GCkJt5wd6cG0NTgGMDxVCh4LsJgmZEEBShz87YqkzqnIvb+xSlB3BT19J9/yPWEnMcsDwMlYVroYl6waTcnp2Ulz5s/bxI68=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi chaps,
host = laptop
dom0 = debian testing
domU = various
problem = providing wireless to my domUs
references = 
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Virtualization-en-US/ch-virt-laptop-configurations.html

That ref has been good so far in that a CentOS instance has got an IP
with dummy0.

host machine:-
cat /etc/issue && cat /etc/network/interfaces
Debian GNU/Linux 4.0 \n \l

# -*- sh -*-
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp
iface eth2 inet dhcp
iface eth3 inet dhcp
iface eth4 inet dhcp

iface dummy0 inet static
address 10.1.1.1
netmask 255.255.255.0
broadcast 10.0.0.255
# arp=yes
# peerdns yes

a CentOS instance
cat /etc/issue && cat /etc/sysconfig/network-scripts/ifcfg-dummy && ifconfig
CentOS release 4.5 (Final)
Kernel \r on an \m

# Thu May 31 18:56:30 BST 2007
# Linux centos4.localdomain 2.6.18-xen #8 Thu May 31 16:52:23 GMT 2007
i686 i686 i386 GNU/Linux
# CentOS release 4.5 (Final)
# Kernel \r on an \m
# added to get this xen instance wireless

DEVICE=dummy0
BOOTPROTO=none
ONBOOT=no
TYPE=Wireless
# NETWORKING=yes
HOSTNAME=centos4.localdomain
GATEWAY=10.1.1.1
IPADDR=10.1.1.10
NETMASK=255.255.255.0

ifconfig
dummy0    Link encap:Ethernet  HWaddr 7E:40:FE:5C:67:F0
         inet addr:10.1.1.10  Bcast:10.1.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:4995 (4.8 KiB)

soooooo close, as at least I have an address ;). Point is that there
is an /etc/rc.foo/bah script in the reference above that's very Redhat
specific. Has any one something similar on a Debian system? I know (or
think) that the next step is to allow the domUs access to the outside
world but I'm not sure how this is done.


--
John Maclean  - 07739 171 531
MSc (DIC)

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