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

Re: [Xen-users] Problems with network setup

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Problems with network setup
From: Sebastian Pölsterl <marduk@xxxxxxxxx>
Date: Fri, 6 Jan 2006 18:54:04 +0100 (CET)
Delivery-date: Fri, 06 Jan 2006 17:59:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <80229.1201.217.187.97.220.1136294148.squirrel@xxxxxxxxxxxxxxxxxxxxxxx >
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>
References: <80229.1201.217.187.97.220.1136294148.squirrel@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.5
> Hi!
>
> I'm running Debian sarge as dom0 and IPCop as domU. In my case IPCop
> should handle all the internet/firewall stuff and dom0 should provide a
> print and file server for the local network. dom0 should have the IP
> 192.168.1.1 and domU 192.168.1.2.
>
> But I have problems getting the hole network stuff running. The machine
> has two NICs, one for PPPoE and one for LAN.
> Unfortunatly, the thing isn't working at all. I can't reach either dom0 or
> domU from a client in the network.
> Though, I searched the archive and found out that it has something to do
> with bridging and routing, I have no clue how to do that.
>
Finally, I got it working.
Here are my final config files:

### /etc/network/interfaces ###
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
        up ifconfig eth0 0.0.0.0 promisc up

auto eth1
iface eth1 inet manual
        up ifconfig eth0 0.0.0.0 promisc up

auto br-lan0
iface br-lan0 inet manual
        address 192.168.1.1
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.2
        dns-nameservers 192.168.1.2
        bridge_ports eth0
        bridge_hello 1
        bridge_fd 1
        up ifconfig br-lan0 192.168.1.1 broadcast 192.168.1.255 netmask
255.255.255.0 up
        up route add default gw 192.168.1.2
### END ###

### /etc/xen/ipcop ###
kernel="/boot/vmlinuz-2.4.30-ipcop"
memory=32
name="ipcop"
disk=['file:/mnt/vserver/images/ipcop.img,sda1,w',
'file:/mnt/vserver/images/ipcoplog.img,sda2,w']
nics=1
dhcp="off"
ip="192.168.1.2"
netmask="255.255.255.0"
vif=['mac=aa:00:00:00:00:11, bridge=br-lan0']
root="/dev/sda1 ro"
extra="3"
pci=["00,0a,0"]
### END ###

### /boot/grub/menu.lst ###
title           Xen 2.0.7/Linux, kernel 2.6-xen0
root            (hd0,0)
kernel          /boot/xen.gz dom0_mem=131072 physdev_dom0_hide=(00:0a.0)
module          /boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0 
max_loop=16
savedefault
boot
### END ###

The NIC that's responsible for the internet connection is eth1 with PCI id
00:0a.0

-- 
Gruß,
Sebastian Pölsterl

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

<Prev in Thread] Current Thread [Next in Thread>