similar to: Dom0 cannot see network when bridge is enabled

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

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, 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, i have problems with the network between pv-domains and the real network. I done an upgrade with apt-get in debian an now i have xen4.1 with kernel 3.2.9 first i must chance the vif-bridge script from http://nopaste.php-q.net/194087 to http://nopaste.php-q.net/194084 now i have a connection from pv to dom0 and the windows hvm, but no connection between physical network an the pv

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker

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

(If this is a double post, I apologize, my email client crashed when I first sent it) I need some help to configure a secure network on my Xen server. I have been looking online and it seems a I need a routed network. But I am having a terrible time implementing it. My setup: Xen 3.4.2 CentOS 5.5 Dom0 1 NIC (eth0) All guests will be HVM What I want to do is something similar to a firewall

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, I''ve bit the bullet and gone with Xen, but I get some odd networking. Basically, this was the original idea. eth0 external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get

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

Hi, I have a Centos5 machine running xen 3.0.3-41 with two NICs each on its own subnet: 192.168.1.x and 192.168.0.x. All DomUs can talk to each other OK through two xen bridges. There are 3 DomUs: Dom0, Dom1 and Dom2 The scenario: I''m trying to capture packets on Dom2 on 192.168.0.x from external devices that are sending SIP stuff to Dom1, but fail to capture any packets. I

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

CentOS 5 updated, Xen host. The portmap on this machine is somehow "stuck" and I can't figure out why. I enabled it to be able to mount a remote nfs share. The first hurdle was that "portmap" didn't appear in the chkconfig list, it was installed with the initial packages but not added to chkconfig. Took me a while to figure this out. Adding and starting it up is no

Hi, I ''ve got a CentOS 5.2 server running xen 3.0 with 2 DomUs also running CentOS 5.2. All my boxes are up-to date. I''m experiencing trouble with networking. Dom0 can reach the outside world when no DomU are started. It can also reach the outside world when only one DomU is running. The troubles begin when I start the second DomU. At first, this new DomU, called DomU2,

Hi all, I have used tinc to get a vpn up and running I am almost there but have some problems at the end. My config: Building A Network 10.0.0.0 netmask 255.255.255.0 gateway 10.0.0.30 tap0 device on gateway machine 10.0.0.31 Building B Network 10.2.0.0 netmask 255.255.255.0 gateway 10.2.0.154 tap0 device on gateway machine 10.2.0.155 from network A I can ping 10.2.0.154 but not the other

Hi folks, I''ve been trying to work out this situation for a few days now without much success and dug all over the archives for similar issues, none of which seem to relate exactly. I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell server. It works fantastic with all the default configurations with one strange flaw - as soon as the /etc/xen/scripts/network-bridge

Not normally a question for this group, but you guys are very bridge/router/firewall savvy, so I thought I''d toss it here. I have a bridge. On one side of the bridge is that fancy thing called the Internet. On the other side is my LAN. The bridge is the obvious demarcation line and a good place to put a firewall. Now, I have all my iptables stuff planned out, EXCEPT for nat. The

Thanks a lot for your hints Pasi. Due to your suggestion I open a new thread here. I have tested with model=e1000 (HVMs). As HVM configs are identical (not iso images and LVM volumes) I guess it is a xen 4.1.2* issue .. or just involved domU OS-kernels (however as it is HVM it should not play any role) Tested and correctly working OSes (getting an IP address and pinging of

Here are some notes I have about Linux bridging. I''ll try to separate what I know I know from what I think I know. Let''s say I want to bridge eth0, eth1, and eth2 together, all with an IP Address of, say, 1.2.3.2. This is how to do it: echo "Setting up br0 to bridge eth0 with eth1 and eth2" /usr/sbin/brctl addbr br0 /usr/sbin/brctl addif br0 eth0

Hi, I'm trying to configure nwfilter for KVM, but so far I haven't managed to figure out a working configuration. Network setup: The dom0 (Debian 7.1, kernel 3.2.46-1, libvirt 0.9.12) is connected via eth0, part of the external subnet 192.168.17.0/24, and has an additional subnet 192.168.128.160/28 routed to its main address 192.168.17.125. The host's subnet is configured as bridge