Re: [Xen-users] how do i setup (simple) networking for dom0 <--> domU ?

[Sadique <sadique@xxxxxxxxxxxxxxxxxxx>]

All that you need to do is configure your default gateway to forward
packets to the internet and dom-u's would act normally as physical
servers forwarding packets to internet. I am using ethernet bridging and
I am able to ping to internet from my dom-u.

Thanks
Sadique

Dave Fear wrote:

>Hi folks
>
>I am trying to setup networking for domU's (just the 1 at the moment)
>and i am highly confused?
>
>My network setup is as follows: 
>
>fw (& gw / connection to internet)
>network addr:  192.168.12.0
>netmask        255.255.255.0
>gw ip addr:    192.168.12.1
>
>dom0 address:  192.168.12.10
>domU address:  192.168.12.100
>
>Running Xen 3.0/unstable -- using xen-unstable-install-x86_32.tgz ---
>download on 11/09/05
>
>I want to setup networking so that:
>1) dom0 (and clients on net 192.168.12.0) can ping domU
>2) domU can ping dom0 (and clients on net 192.168.12.0)
>3) domU can ping internet
>
>I don't no whether to use routed, bridged or proxy-arp networking and if
>iptables or ebtables is required.
>
>
>-----------------------
>listing of conf files:
>-----------------------
>
>xend-config.sxp (relevent extract listed)
>------------------------------------------
>
>---- snip -----
>## Use the following if VIF traffic is routed.
># The script used to start/stop networking for xend.
>#(network-script     network-route)
># The default script used to control virtual interfaces.
>#(vif-script         vif-route)
>
>## Use the following if VIF traffic is bridged.
># The script used to start/stop networking for xend.
>(network-script    network-bridge)
># The default bridge that virtual interfaces should be connected to.
>(vif-bridge        xen-br0)
># The default script used to control virtual interfaces.
>(vif-script        vif-bridge)
>
># Whether iptables should be set up to prevent IP spoofing for
># virtual interfaces. Specify 'yes' or 'no'.
>(vif-antispoof     no)
>---- snip -----
>
>
>vm03.cfg (config file for 1st domU)
>-----------------------------------
>
>kernel="/boot/vmlinuz-2.6.12-xenU"
>memory=96
>name="AsteriskAThome"
>
>nics=1
># Set if you want dhcp to allocate the IP address.
>#dhcp="dhcp"
># Set netmask.
>#netmask="255.255.255.0"
># Set default gateway.
>#gateway="192.168.12.1"
># Set the hostname.
>#hostname="pbx.home.dfear.net"
>#ip="192.168.12.100"
>#vif = [ 'bridge=xen-br0' ]
>#vif=[ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ]
>vif=[ 'mac=00:60:00:00:00:01' ]
>
>disk=['file:/xen/domains/vm03/CentOS4.img,sda1,w','file:/xen/domains/vm03/swapimage,sda2,w']
>root="/dev/sda1 rw"
>ramdisk="/boot/initrd-2.6.11.12-xenU.img"
>
>restart="onreboot"
>
>
>----------------------
>output of various cmds:
>-----------------------
>
>uname -r
>--------
>
>2.6.12-xen0
>
>
>route - n (on dom0)
>-------------------
>
>Kernel IP routing table
>Destination     Gateway         Genmask         Flags Metric Ref    Use
>Iface
>192.168.12.0    0.0.0.0         255.255.255.0   U     0      0        0
>eth0
>169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
>eth0
>0.0.0.0         192.168.12.1    0.0.0.0         UG    0      0        0
>eth0
>
>
>ifconfig
>--------
>
>eth0      Link encap:Ethernet  HWaddr 00:A0:C9:A5:A2:DD
>          inet addr:192.168.12.10  Bcast:192.168.12.255
>Mask:255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:2392 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:1982 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:238565 (232.9 KiB)  TX bytes:337763 (329.8 KiB)
>
>lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:212 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:212 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:24681 (24.1 KiB)  TX bytes:24681 (24.1 KiB)
>
>vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:8 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:336 (336.0 b)  TX bytes:0 (0.0 b)
>
>xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:13 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:364 (364.0 b)  TX bytes:0 (0.0 b)
>
>
>iptables -v -L (on dom0)
>-------------------------
>
>Chain INPUT (policy ACCEPT 1107 packets, 85910 bytes)
> pkts bytes target     prot opt in     out     source
>destination
>
>Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target     prot opt in     out     source
>destination
>
>Chain OUTPUT (policy ACCEPT 928 packets, 194K bytes)
> pkts bytes target     prot opt in     out     source
>destination
>
>
>iptables -v -L -t nat (on dom0)
>-------------------------------
>
>Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target     prot opt in     out     source
>destination
>
>Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target     prot opt in     out     source
>destination
>
>Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target     prot opt in     out     source
>destination
>
>
>
>===========================================================
>
>I hope someone on the list can sort this mess out for me (and many
>others on the list it seems).
>
>I and many others would be very very greatfull for a solution.
>
>
>  
>


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