similar to: Xen bridge swallowing packets?

Hi, Creating a new domain is a lot easier in opensuse 11. I follow the instruction on the website and build a virtual machine which uses opensuse 11 as well (I installed it from iso image). Everything works fine except the network. I cannot access the Internet from DomU. Here is some information. P.S. the DomU id is 1. "brctl show" in Dom 0: bridge name bridge id STP

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

When starting xend i see the following errors on the console. I''m running CentOS 5 as the operating system with kernel 2.6.32.18 from 4.0.1''s `make prep-kernels` Below is a log, the things i''m concerned with is the XENBUS errors and the deprecated iptables stuff. Any ideas whats going on here? ---------------------------------------------------- Bridge

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

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

I''m using xen-3.0.3-64.el5_2.1 on centos 5.2. When I installed centos 5.2 at first time, I could see shared physical device (xenbr0). but after updating virtualization package by yum, it disappeared... connection.py is patched at centos 5.2 release time. so I can''t find out what''s wrong.... bridge configuration is below and it''s normal state.

Hi * in xend-config.xsp I have: ******************************** (network-script network-route) (vif-bridge xen-br0) (vif-script vif-bridge) ******************************** and in /etc/network/interfaces ********************************* iface eth0 inet static address 0.0.0.0 auto xen-br0 iface xen-br0 inet static pre-up ifconfig eth0 up pre-up brctl addbr xen-br0 pre-up brctl addif

All works fine on my virtual hosts, except the network. The internal interface is created (have an ip address), the external bridge is ok, with the external vif1.0 for the virtual host, but `ping virtual_host_address` dont work. Ok, I try to put on vif1.0 an ip address. When I do an `ifconfig vif1.0 127.1.2.3` the network works fine, `ping virtual_host_address` works and all machines from my

I don''t know if there was a problem in the archive or not, I just wanted to link to this post of mine, but I could not find it in the archive. So here''s a re-post. -------- Original-Nachricht -------- Betreff: [Xen-users] Xen, NIC bonding, ARP problem Datum: Fri, 30 Mar 2007 10:05:45 +0200 Von: Dominik Klein <dk@in-telegence.net> An: xen-users@lists.xensource.com Hi

Hi, I have taken the long and winding road and indeed it lead me to your door. I need your help, please. My Xen includes 2 guests. Xen itself (10.2.0.52) gets free access to the outside world and to its guests. Both guests however (10.2.0.54/10.2.0.55) see each other but stay under house arrest! Not a single ping manages to go past the bridge (xenbr0) and get an answer from the default gateway

Hi list, i''ve been migrating our RAID1 system onto bigger drives. Therefor I''ve setup a new dom0 with a 2.6.32-5-xen-amd64 kernel and Xen in version 4.0, because there was a 2.6.19 kernel and xen 3.0.1 causing problems time by time. My main problem is, that the domU running our intranet services (webserver, mail, databases etc) is not responding or rejecting each attempt to

> Hi. what creates veth0 and vifu.0, when? what''s the > underlying architecture behind them? Just trying to > understand the internals. netback/loopback.c creates them. It''s effectively a point to point link, allowing domain 0 to connect on to the bridge in the same manner that other domains do. (before, packets to domain 0 were short-cutted and came off the

Hello, I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear in domU. I have 3 servers running FC3 and Xen 2 with various domUs since a year. Everything is fine on that front. I took one of the server, upgraded it to FC5 and did the following: - yum install xen kernel-xen0 kernel-xenU - grub.conf contains title Fedora Core (2.6.15-1.2054_FC5xen0 root (hd0,0) kernel

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

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.

> 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

Hi! I''m not new to Xen but I''m new to this list. I''m having a truely bizarre problem with Xen bridged networking at the moment. This is a new install, on RHEL4. The symptom is that any domU set up simply fails to talk to anything else. It''s there, and running, and it has an ethernet device, but there''s never any response. After digging through the

Hey All I''m Using Xen 3.0.3-105 on CentOS 5.5. It Has to Nics: eth0 - Internet eth1 - Internal Lan ( where Dhcp , DNs , Cobbler - Kick Start Server Resides ) I''ve Set xend-config.xsp to create xenbr1 on eth1 and it looks well So Guest May Get Access TO ALl Resources via the Bridge. brctl show bridge name bridge id STP enabled interfaces xenbr1

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'']