| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Xen networking on centos
On Mon, 2006-10-02 at 13:41 +0200, Sascha Endlicher wrote:
> Hi,
>
Hi Sascha,
as far as i can see, i'm missing a subnet link between your dom0 and
domU. as there's a public LAN and there's a BackupLan which one is
attached to your xenbridge ? ($ brctl show)
I had some problems using bridgesetup in centos like your setup is
designed as NAT didnt work correctly. I customized the network-bridge
script to add the eth(x) to the bridge, assigned the IP Addresses and
routes to the xenbr(x) device to get it working.
But as mentioned above i'm missing a Subnet link from dom0 to domU in
your setup, something like ifconfig xenbr0 10.0.0.1/24 up and there's
confusing config in your DomU xen Config and your network config in the
DomU.
Kind regards
Michael Lang
>
> hopefully someone can give me some pointers in the right direction:
> I installed Xen 3.0.2-2 on Centos 4.4, downloaded a Fedora Core 5
> image from jailtime.org and I can start the GuestDomain, but I can't
> figure out the networking. I can't ping to or from the GuestOS.
>
>
> From my provider I got two IP ranges with multiple IPs each and I have
> a backup lan in the form of
> Backup Lan IP: 192.168.1.43
> NAS IP: 192.168.1.1
>
>
> My provider gave me the following details:
> Main IP: X.X.X.2
> Public IP Range: X.X.X.14 - 19 (all usable)
> Public IP Range: X.X.X.40 - 27 (all usable)
> Network: X.X.X.0
> Netmask: 255.255.255.0
> Gateway: X.X.X.1
> DNS Resolver: Y.Y.Y.Y
>
>
> My goal is the following setup:
> The GuestOS1 should listen behind 1 or more public IP addresses to
> all services. I plan on installing cpanel on GuestOS1 later on and it
> will have
> more than 1 dedicated IP.
> GuestOS1 should not listen to all IPs though, as I will install a
> GuestOS2 later on. GuestOS2 should also have a few IPs assigned to it.
> The GuestOS* needs to be able to reach the Backup LAN too.
>
>
> In /etc/xen/xend-config.sxp I am using:
> (network-script network-bridge)
> (vif-script vif-bridge)
>
>
> xm list
> Name ID Mem(MiB) VCPUs State Time(s)
> Domain-0 0 2567 4 r----- 223.4
> ns2 16 256 1 -b---- 6.5
>
>
> My ifconfig shows:
> eth0 Link encap:Ethernet HWaddr 00:30:48:55:27:AA
> inet addr:X.X.X.2 Bcast:X.X.X.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:898077 errors:0 dropped:0 overruns:0 frame:0
> TX packets:812176 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:57428320 (54.7 MiB) TX bytes:44416204 (42.3 MiB)
> eth0:1 Link encap:Ethernet HWaddr 00:30:48:55:27:AA
> inet addr:X.X.X.14 Bcast:X.X.X.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
>
> (...) going through the entire IP range (...)
>
>
> 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:454 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:68871 (67.2 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:39 errors:0 dropped:0 overruns:0 frame:0
> TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:6868 (6.7 KiB) TX bytes:6868 (6.7 KiB)
>
>
> vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:7 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:6 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:294 (294.0 b) TX bytes:0 (0.0 b)
>
>
> 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:48175 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2465524 (2.3 MiB) TX bytes:468 (468.0 b)
>
>
>
>
> From what I gather from this, peth is missing.
> My /etx/xen/ns2 looks like this:
>
>
> name = "ns2"
> kernel = "/boot/vmlinuz-2.6.16-xen"
> ramdisk = "/boot/initrd-xen-3.0.2-2.img"
> memory = 256
> root = "/dev/sda1 ro"
> disk = ['file:/usr/local/src/os/fedora.fc5.img,sda1,w',
> 'file:/usr/local/src/os/fedora.swap,sda2,w']
> extra = "3"
> vif=[ 'ip=10.0.0.2' ]
> ip="10.0.0.2"
> dhcp="off"
> netmask="255.255.0.0"
> gateway="10.0.0.254"
> hostname = "ns2"
>
>
> In my guestos my ifconfig shows:
> eth0 Link encap:Ethernet HWaddr 00:16:3E:73:1F:85
> inet addr:X.X.X.14 Bcast:X.X.X.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:294 (294.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:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:288 (288.0 b) TX bytes:288 (288.0 b)
> The config file in /etc/sysconfig/network-scripts/ifcfg-eth0 on the
> guestos:
> TYPE=Ethernet
> DEVICE=eth0
> #BOOTPROTO=dhcp
> BOOTPROTO=none
> ONBOOT=yes
> IPADDR="X.X.X.14"
> NETMASK=255.255.255.0
>
>
>
>
> Can anyone point this confused n00b into the right direction? :)
> --
> Sascha Endlicher
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
--
Michael Lang <michi+xen@xxxxxxxxxxxxxxxxxxxx>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home