similar to: Firewall problem resolved - cannot set up networking in domU

Hello, my current network setup looks like the following: dom2-eth0 (172.30.1.22) netmask /24 | | xen-br1 (no ip) | dom1-eth0 (172.30.1.21) netmask /24 dom1-eth1 (172.30.0.21) netmask /24 | | xen-br10 (172.30.0.1) netmask /24 | dom0 | | xen-br0 (normal IP) | eth0 (same IP as xen-br0) |

Hello, At first i want to thank you for your work on such a wonderful piece of software. If can get my setup running as planned it will help me to use my hardware ressources in a much more efficient way. I''m a xen newbie an trying to setup following environment: xen-2.0.4 compiled from source hardware: 2 PIV 3GHz Processors, 1GB RAM, 2 NICs Dom0: Debian Sarge kernel 2.6.10 on xen-br0

Hi, I am new to xen and needed some help doing a networking setup on xen. I am using a Centos host with the xen modules installed. I have created a dom1 which contains another centos machine. I want the interface eth1 of dom1 to receive all traffic that is seen for eth0 on the physical machine. The interfaces of dom1 are bridged to xenbr0. I have set eth1 to promiscuous mode on dom1. On doing an

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

Hi list, I''m looking for some help in getting my domU network aware. Currently I can run /etc/xen/scripts/network from dom0 to successfully create xen-br0. After I do this, dom0 can still access any network resource that it could before. However, when I start up a domU, it can only ping dom0; it fails to connect to any other ip. I don''t receive any sort of error message,

Greetings, I have a problem that is baffling me. My host machine is an older Dual Xeon machine that does not support HVM - PAE is supported. I have 2008.11 b98 installed as Dom0. I''m trying to install the same as a DomU. In the DomU, I''m starting the ssh service, logging in with X forwarding and starting the gui with: (dom1) jack$ pfexec gui-install The gui displays on my

Hi, Question on setting up networking in xen. I want to do the following on my laptop: dom0 is attached to eth0 and ath0. dom1 is going to by my virtual firewall for all my virtual machines. So I assume 3 interfaces, a bridge to eth0, ath0 and a virtual interface? dom2 and so on will route all their traffic through dom1 (through the virtual interface) I''ve read the documentation a

Moi! I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly. I''m still able to boot dom0 and start domUs but networking doesn''t work anymore. xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is used. Interface appears in domU and all seems to be fine, except no any data doesn''t move in any direction. I can''t even ping

> That''s great, except when you need *two* bridges, for two > independent subnets, and there is no, as far as I can see, peth1. You can have multiple vethX interfaces on recent builds -- see netback/loopback.c. I think the current default is a rather miserly 1 (and should be increased), but can be set on the command line. Ian > Em Wednesday 14 September 2005 16:30, John

When I start xen dom0 I get that same dhcp address for eth0 and for xen-br0, dom0 can talk to the world. If I start each of my 3 domU''s mannually, each guest gets a xen-br0 vif with a dhcp address and all 3 can talk to the outside world and each other (my "flat network"). What I want is a tiered network with the first domU acting as a firewall with 3 nics vif = [

Hello @all, thanks for all the helpfull answers in this mailing list. They helped me compiling a new kernel 2.6.10.11 with Xen 2.0.6 (my first one), setting up a dom0 with RAID, LVM and loop devices for domU, integrating a second network as xen-br1 (I''m calling the /etc/xen/scripts/network script from within /etc/init.d/xend to bring up / down the second bridge.) and bootstrapping

I posted this to the Fedora-test list but I''ll try here. If I need to ditch fedora rpms and move to building directly from src before posting here, please let me know and I''ll do so (apologies in advance if this is the case). I have the following Fedora RPMS installed: kernel-xen0-2.6.10-1.1155_FC4 kernel-xenU-2.6.10-1.1155_FC4 xen-2-20050222 I can

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

I am trying to dedicate a number of PCI ports to DomU and no success! The PCI devices I am trying to dedicate are QLogic 23xx cards! I am using SUSE 10.1 with latest xen-unstable! I have followed all the instructions given in latest xen 3.0 manual. Like building the backend support in Dom0 Building the frontend support in DomU Using the pciback.hide=(xx:xx.x) in Dom0 command

Up to now I''ve been using only one domU and networking has been fine. Now I''m trying to use several domUs simultaneously (up to 14) and having many networking problems. In particular I''d like to fire off commands on all the domUs at the same time (or at least within a couple seconds). Even something as simple as: ssh dom1 hostname & ssh dom2 hostname &

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 Hi, Hvm domU does not starts up afer dom0 reboot. Bridge br0 is set up manually. Dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux DomU: Debian Squeeze 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux config: ===<======== kernel = '/usr/lib/xen-4.1/boot/hvmloader' builder = 'hvm'

Hi all, In June 2007 Jerry Nelson started a thread on this mailing list about a problem he was seeing. The thread was http://syslinux.zytor.com/archives/2007-June/008673.html After several hours of searching through the list, I am still convinced that his problem was never solved and is very valid. I recently moved from the old syslinux config options model (all labels in 1 default config file)

Hello All, I¹ve installed the vanilla shorewall F12, I¹ve got it installed on a couple of other servers with no problems. no matter how I define the zones and interfaces, shorewall logs and allows, rejects or drops only traffic to world. ACCEPT:info net:<myip>/32 $FW icmp Shorewall:world2fw:REJECT:IN=br0 ACCEPT:info world:<myip>/32 $FW icmp

Hello I've got this Mini-PC https://www.zotac.com/product/mini_pcs/zbox-ci323-nano everything is fine -> latest 6.8 kernel works; both Ethernet-Interfaces work and also the WLAN-Interface works; the two Ethernet-Interfaces are eth0 and eth1 the WLAN-Interface is wlan0 eth1 is connected on ISP side eth0 is connected on my LAN side to a switch; and wlan0 shall also be on my LAN side f?r

Hi everyone, I need your help. I would like to create a front-back architecture with Xen. My physical server has only one public Interface. Currently, my DOM0 is using the network-route configuration: *(network-script ''network-route netdev=eth0'') (vif-script vif-route)* My DOM1 is configured with a public IP + proxy_arp with DOM0. DOM1 can connect any address on