similar to: Network issue with vif-route method

Today I found I can not ping some of my domU''s. I logged in to dom0, did a "xm list", all domU are there. Then I did a "ifconfig" and surprised to find some of vif''s disappeared! Like for example. "xm list" show dom13 is alive, but "brctl show" shows no vif13.0. If I "xm console 13", there''s some message: WARNING:

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

I''m running Xen and created a virtual os called Domain-1. So now I have two systems, Domain-0(dom0) and Domain-1(dom1), both running fedora 8. I only have 1 ethernet device eth0. However, for some reason, my internet doesn''t work in Domain-1. My output for route -n on Domain-0 is: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref

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

Hey, I''m having a bit of difficulty sshing from Dom0 to DomU and vice versa, my setup is as follows; Xen-3.0-unstable, XenLinux kernel 2.6.12 Dom0 on Redhat EL 4 Dom1 on SuSE linux 9.1 (with the standard xenU kernel included with xen-unstable) The server it runs on doesnt have a nic installed (well it does, just without drivers) the suse config file sets the eth0 interface up as

Hi, all I trying setting domain samba with bind9-DLZ. I followed the tutorial https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, but not work. see the tests bellow ricardobarbosa at isadora:~$ bash tools/testSambaRecords.sh Host _ldap._tcp.freewaynet.corp not found: 3(NXDOMAIN) Host _kerberos._udp.freewaynet.corp not found: 3(NXDOMAIN) Host

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

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

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the

Hello, Fast question: from DomU I cannot ping Dom0, I only get 19:17:33.573370 arp who-has 192.168.10.1 tell 192.168.10.150 19:17:34.573421 arp who-has 192.168.10.1 tell 192.168.10.150 using tcpdump in Dom0. Why? --------------- Detailed question: I''m setting up a Xen virtual server. The environment is: -HVM -AMD64 -Debian Etch and using Xen from Debian repository (so Xen 3.0.3,

I get the error while starting hvm doms. Any workarounds... suggestions.. Thanks /Jd Some thiings that might be useful are cut-pasted below. ifconfig -a udevmonitor output (as suggested in prev posts) qemu-dm log xend.log xend-debug does not seem to have anything interesting. ifconfig -a =========== eth0 Link encap:Ethernet HWaddr 00:0F:EA:53:5C:79 inet addr:192.168.12.103

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

Hi, I''ve a working xen 3.0.2 booting a gentoo linux on Dom0. I have setup a Windows XP in a DomU OK with no problems except the network!! My problem is that I wanted to give a working network interface on the DomU and the best I could. making the windows detect an network adapter, was putting: vif = [''type=ioemu''] I also tryied: vif = [''type=ioemu,

Em 10-09-2018 10:43, Rowland Penny via samba escreveu: > On Mon, 10 Sep 2018 09:56:46 -0400 > spiderslack via samba <samba at lists.samba.org> wrote: > >> Hi, all >> >> >> I trying setting domain samba with bind9-DLZ. I followed the tutorial >> https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, >> but not

My domains dont see any traffic until you try to connect out from within the domain. Tried this several times and it was consistent. I have no firewall either. running each domain on different cpu probably doesn''t help, although Im no network expert. Here is some info. ================ [root@a root]# xm info system : Linux host : a.b.com release

Hello All, I am trying to implement OpenVPN on Fedora core Linux 3 with the latest pathces installed. This server is used only as firewall/internet gateway/proxy/VPN server, with kernel 2.6.1-1.27.FC3 and kernel 2.6.1-1.27.FC3 SMP It has two NIC''s eth0 (10.0.0.150) connected to ADSL, eth1 (192.168.3.12) connected to the local network. I use shorewall 2.4 on this machine. I like to test

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

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, When using xen without a bridge but NAT or routing, HVM domains can''t boot, and qemu-dm-n.log contains: config qemu network with xen bridge for tap0 xenbr0 bridge xenbr0 does not exist! That''s because the qemu-ifup script always tries to add the vif to a default-named xenbr0 bridge. On the contrary, PV domains just work fine with the same configuration file except HVM