similar to: routing and virtual machines: how to access dmz if bridged to two networks

As I received no response on the general CentOS list, I'll repost it here as the question is about Xen virtual machine routing. This is my network setup: http://pastebin.com/kyWpTQYU Lets assume my dom0's eth2 public ip is 1.2.3.33 and my dmz network 11.22.33.96/255.255.255.224 . I have created NAT from my LAN with iptables. You can see my /etc/sysconfig/iptables here:

Hello, I''m new to Xen (and this mailing-list) and facing some problems with the network. I''m stuck and don''t know how to continue. And Google isn''t very helpful either... My setup: - Ubuntu 7.10 for dom0 and Debian 4.0 for all domU - 4 physical NIC (DHCP from my ISP, internal LAN, DMZ & WLAN) - 1 Dom as firewall/router - 1 domU with internal services

Hello folks, I have this really strange routing problem that no amount of googling and experimenting has been able to solve. Then again, I''m new to Xen and "advanced" networking, so I could be missing something very basic. Summary: an unprivileged domU with PCI frontend for a NIC is used as a router; icmp gets routed, but tcp/ip only partially. I''m using a

Hello folks, I have a really strange routing problem that no amount of googling and experimenting has been able to solve. Then again, I''m new to Xen and "advanced" networking, so I could be missing something very basic. Summary: an unprivileged domU with PCI frontend for a NIC is used as a router; icmp gets routed, but tcp/ip only partially. I''m using a xen-unstable

I want to add the following route command route add -net 192.168.2.0/27 gw 192.168.2.3 via the normal network setup. The result should be the following routing table (the first line): 192.168.2.0/27 via 192.168.2.3 dev xenbr1 scope link 192.168.2.0/27 dev eth2 proto kernel scope link src 192.168.2.4 192.168.2.0/27 dev xenbr1 proto kernel scope link src 192.168.2.3 192.168.1.0/24 dev xenbr0

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

Hello Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

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

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

Hi, until now, i have been using Xen 3.0.2. Now i upgraded to Xen 3.0.4. Can anybody confirm, that the ordner in the config files for the network interfaces has not changed? My config file used to read: vif = [ ''bridge=xenbr0'', ''bridge=xenbr1'' ] So inside the DomU, eth0 was attached to xenbr0 on the host and eth1 was attached to xenbr1. Now i upgraded to

When I add all interfaces, the internet does not work.... eth0 = interneteth1 = lan ------------------auto eth0 iface eth0 inet static address 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255 auto eth1 iface eth1 inet static address 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.254 auto xenbr0 iface xenbr0 inet static

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 all, I would like to use two network interfaces. It is working but I notice that both bridges hace the same id. #brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif10.0 xenbr1

Hey Tom, This is my T-1 slash 27 network btw. How does this look??? for---- net eth0 66.224.62.120 ----dmz eth1 66.224.62.120 This box is for practice Dmz we talked about. with the pratice Dmz server''s Ip 66.224.62.121 routing and interface''s below [root@66-224-62-120 root]# ifconfig eth0 Link encap:Ethernet HWaddr

I am writing this email in the hopes of getting some advice from Xen users. My main concern is performance and stability. Before I get any further, let me explain the environment: 1. I am using redhat enterprise linux 5 with the xen kernel (2.6.18-8.1.1.el5xen). This is on a Sun X4200 with two dual core AMD processors, 16Gb of RAM, a Sun StoredgeTek 3320 attached to the X4200,

Hi Folks: I have a strange problem with multiple (2) NICs on a CentOS 5.5 dom0 setup running xen 3.4.3 and have been struggling to fix it for some time. I could not find anything by googling or searching through this list but that is probably because I couldn''t figure out the correct search terms. After I configure my bridges the command "system network restart" fails for eth1

Hi all, The first couple of xen machines we setup used the default xen bridging setup for dom0. I am sure there are many other people out there with this setup. Now that I know a bit more there are probably better ways out there to configure the xen box for firewalling, most notably assigning the red card to a domU and running shorewall in there. But in the meantime I would like to further

I am posting the message below again because it did not go through last night. Help! Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

Hello all, I have been running xen for a while now with two interfaces: dummy0 for host only communication, and eth0 for the outside network. my script looks like this: (/etc/xen/scripts/network-bridge-more) ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0

Hello, Where can I find a link (or docs) to *working* network config for xen 4.1.2? My tests (s. below) were not successful. Thank you in advance for any hints. Regards, Mark # --- root@xen411dom0:~# cat /etc/network/interfaces # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback auto bond0