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] Network setup on Redhat based systems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Network setup on Redhat based systems
From: Sascha Endlicher <me@xxxxxxxxx>
Date: Fri, 13 Oct 2006 00:37:33 +0200
Delivery-date: Thu, 12 Oct 2006 15:37:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I have the following Xen 3.0.2-2 related problem:
A host system with Centos 4.4 in the dom0, guest systems are Fedora Core 5 (images from jailtime.org) mounted on LVM.

Networking on the domUs is not working, Iptables in the guests are not working either.

Each Guest system should have at least 1 dedicated public IP assigned to it, but should have the capability to have more than 1 IP address assigned to it.

There are a lot of examples for Debian in the list archives, but I can't find any resources for public IP setups for Redhat based systems.

I was given the following details by the provider:
Main IP: XX.YY.33.64
Range: XX.YY.33.64 - 79 (all usable)
Range: XX.YY.33.100 - 115 (all usable)
Network: XX.YY.33.0
Netmask: 255.255.255.0
Gateway: XX.YY.33.1
DNS Resolver: 65.74.153.77

Unfortunately, I seem to be missing some of the basics and have a few questions:
a) Do all the public IP addressed need to be set to listen in dom0 and domU or in one of them only?
I.e. if I want XX.YY.33.100 to bind to 1 domU, would I still need to listen to this IP in dom0?
Would this be sufficient to bring it up?
ip addr add XX.YY.33.100 dev eth0
Or would I need to add it to another interface?

b) What would be the typical broadcast address for eth0? The network address or the gateway address from the example above? My ifconfig shows Bcast:XX.YY.33.255 , but that's neither one of them. Does it matter in this case?

My current configuration:
# ifconfig in dom0:

eth0      Link encap:Ethernet  HWaddr 00:30:48:55:27:AA 
          inet addr:XX.YY.33.64  Bcast:XX.YY.33.255  Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fe55:27aa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1225895 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4864 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:77888321 (74.2 MiB)  TX bytes:630273 (615.5 KiB)

eth1      Link encap:Ethernet  HWaddr 00:30:48:55:27:AB 
          inet addr:192.168.1.43  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fe55:27ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:569 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:65225 (63.6 KiB)  TX bytes:620 (620.0 b)
          Interrupt:18

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:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1804 (1.7 KiB)  TX bytes:1804 (1.7 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:1231013 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4906 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:83198745 (79.3 MiB)  TX bytes:654971 (639.6 KiB)
          Interrupt:17

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4866 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1225901 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:630613 (615.8 KiB)  TX bytes:77888797 (74.2 MiB)

vif9.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:895241 errors:0 dropped:112 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:496 (496.0 b)  TX bytes:56757350 (54.1 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29921 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1574921 (1.5 MiB)  TX bytes:510 (510.0 b)

My domU configuration in dom0 /etc/xen/fc5.conf:
kernel = "/boot/vmlinuz-2.6-xen"
memory = 128
name = "fc5"
dhcp = "static"
vif = [ 'mac=aa:00:00:00:00:11, bridge=xenbr0, ip=XX.YY.33.100' ]
ip= "XX.YY.33.100"
disk = ['phy:vg/ns2g,sda1,w', 'file:/usr/local/src/os/fedora.swap,sda2,w']
root = "/dev/sda1 ro"
netmask = "255.255.255.0"
gateway = "XX.YY.33.1"

The brctl output:
brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0
                                                        vif9.0


My configuration in 1 domU with FC5:
My ifconfig:
[root@fc5_pristine ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:00:00:11 
          inet addr:XX.YY.33.100  Bcast:XX.YY.33.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:906298 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:57458107 (54.7 MiB)  TX bytes:606 (606.0 b)

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:0 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:0 (0.0 b)  TX bytes:0 (0.0 b)

/etc/resolv.conf:
nameserver 65.74.153.77

/etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=fc5_pristine
GATEWAY=XX.YY.33.1

/etc/sysconfig/networking/devices/ifcfg-eth0:
TYPE=Ethernet
DEVICE=eth0
BOOTPROTO=dhcp
>
IPADDR='XX.YY.33.100'
NETMASK='255.255.255.0'

Beeing the n00b I am, I can't figure out what's wrong and I would appreciate any pointers, of course.

Sincerely
Sascha Endlicher
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>