similar to: http-traffic rejected, domU

This patch adds an ACM hook into the network scripts (/etc/xen/scripts). It adds iptables rules that enforce mandatory access control on network packets exchanged between virtual interfaces. If ACM is active, this patch sets the default FORWARD policy in Dom0 to DROP and adds iptables ACCEPT rules between vifs that belong to domains that are permitted to share (determined by using the

Here is the situation. I have a xen system with 2 drives setup in a RAID1. I pulled one drive and put it into an identical server. Now, when I boot up the new server, peth1 is not created. [root@dom0 ~]# ifconfig | grep Link eth1 Link encap:Ethernet HWaddr 00:14:38:A7:55:C2 inet6 addr: fe80::214:38ff:fea7:55c2/64 Scope:Link lo Link encap:Local Loopback vif1.0 Link

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

Hello, I''ve recently changed my xen network setup and now, almost expectedly, my configuration has broken access to the Domus from the network, and now I need a little help. Previously, I had four interfaces, only one of which was configured to be used by both dom0 and domu. I have since created a bond between eth2 and eth3, expecting that eth0 would be automatically assigned for use

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

hi, after rebooting my host, i can''t have anymore the networking: here''s my output of /etc/init.d/networking restart Reconfiguring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. done. cat

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

Hello, There is a xen setup in which "brctl show" gives the following output. bridge name bridge id STP enabled interfaces eth1 8000.003048c9d4df no peth1 vif1.0 vif2.0

I have a OpenSuse 10.3 with xen 3.1.0 running and it''s been running fine for a few months. This past weekend it suddenly started to act up and after some troubleshooting I can now say that it seems like the guests(domU) loose the outgoing network pipe, from the console I can see that the TX counter is stuck at the same value but it''s no errors. It behaves as if whatever I try to

Hi, we''re running 4 xen servers on our network with multiple network cards. During HighLoad we experince degeneration of inbound network traffic through our loadbalancer. I might found a reason for it, in Dom0 dmesg output looks as follows: [1157421.975910] eth0: received packet with own address as source address [1157421.975957] eth0: received packet with own address as source

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 5:25 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson > (davetho) wrote: > > > >

Hello everybody, I have an odd problem with iptables using a Xen bridge setup. I don''t know if it would be better to post to netfilter Mailing-List. But I hope someone here know how to solve it. If it''s OT here, please let me know. I''ll try to do a little bit ASCII-Graphics to explain the topo better: _________ ________

Hi, we are trying to secure our Xen boxes with IPtables on Dom0 but we always seem to get cut off and can only cure it be rebooting the box. Has anyone got a sucessful config they can share that secures the server with one nic? We are using Xen 3.0.4 thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello, Finally I managed to get a xen 4.0 working on ubuntu 10.04 with pvops kernel and libvirt. However I am having some problems with networking... after initial installation with netinstall image in hvm mode, when I transform the vm in xen pv (via pygrub with the current ubuntu kernel), networking startEd to act weird... Basically I''m not using a network script from xen. I define a

Hello, Finally I managed to get a xen 4.0 working on ubuntu 10.04 with pvops kernel and libvirt. However I am having some problems with networking... after initial installation with netinstall image in hvm mode, when I transform the vm in xen pv (via pygrub with the current ubuntu kernel), networking startEd to act weird... Basically I''m not using a network script from xen. I define a

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

xm list reveals the following information... Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 315 0 r---- 2058.1 Domain-1 11 342 0 -b--- 5.2 9611 Domain-2 12 342 0 -b--- 3.9 9612 Xen seems to be working beautifully but I have not yet figured out how to get Domain-0 to ping both Domain-1 and Domain-2,

In my project, I tried to use iptables, instead of bridge, to direct networking traffics from one VM to another in one host. What I am doing is I delete xen-br0, and I have two VMs that have IP addresses of 10.8.0.51 and 10.8.0.52. I use iptables -t mangle -A FORWARD -d 10.8.0.51 -j ROUTE --oif vif1.0 iptables -t mangle -A FORWARD -d 10.8.0.52 -j ROUTE --oif vif2.0 vif1.0 and vif2.0 are the