similar to: insight on additional adapter

Hi all, I have Xen 3.2 newly installed on Lenny with network bridging configured. When I built my first VM, I found it couldn''t connect to the Internet. This turned out to be because my dom0''s iptables was configured to DROP all packets on the FORWARD chain (when I removed that, it started working). The "Xen Networking" page on the wiki describes this exact situation

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

Hi, in the official XenNetworking ( http://wiki.xensource.com/xenwiki/XenNetworking ) i didn''t find reported how the NAT configuration works with xen. Does anybody know how the vifX.Y (10.X.X.128), gateway of any domU ethX (10.X.X.1) talk with the real ethX of the dom0? Thanks Enrico _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

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 all, I''m using Red Hat Enterprise Linux 5 (with RH Virtualization) and a Dell Poweredge 2950 with 10 NICs. My virtual operating systems are all RHEL4, and I''ve installed 4 instances. I''m trying to set up the virtual operating systems so that the physical NICs are allocated to certain operating systems. Using the following tutorial:

So Working on CEntOS 5 I am trying to sett up Xen with 2 bridges, one that connects dom0 and most of the domU to the physical card and the out to the network. Got that figured out no problem, now i want to have a second bridge that runs a local network for all the doms that doesn''t connect to the network. With code I have found used in multiple places I can easily get 2 bridges, and

Hello all, I have a Xen server with 6 network interfaces, I want a bridge on all of them. I use a personal network script like this : #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 "$dir/network-bridge" "$@"

Hi, I have a box with XEN enabled. Specs : Gentoo 10.0 AMD64 XEN 4.0.0 The server is connected on our network through two physicals NIC. Actually, I''m using a VLAN on each NIC and bridge the domU in it. But now I must create an additional domU which should be in an different VLAN. The best solution is to set a trunk on the switch and use 802.1q directly on the dom0. I found this site

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, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1

Hi, In one of our xen server, I am using two bonding. bond0 : Is for trunk, where the vlans are attached , port eth0 & eth1 is attached to bond0 bond1 : eth2 & eth3 are attached to bond1, where physical ip has been set . In the /etc/xen/xend-config.sxp, I am using (network-script *multi-network-bridge*) , the

On 11/01/2017 07:55 AM, Scott Gennari wrote: > /etc/xen/scripts/network-bridge-pcl > > #/bin/sh > > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=1 netdev=eth2 bridge=xen-dmz2 > "$dir/network-bridge" "$@" vifnum=3 netdev=eth0 bridge=xen-dmz1 Do you get any error output when you run: /etc/xen/scripts/network-bridge

Hi, I am facing issues after upgrading one of the server from rhel5.5. (86_64) to latest rhel5.7 (86_64). The server is under trunk configuraion. I have set the network bridge as follows: #!/bin/bash vconfig set_name_type DEV_PLUS_VID_NO_PAD dir=$(dirname " $0" /etc/xen/scripts/network-bridge $@ vifnum=1 bridge=xenbr2 netdev=bond0.10 /etc/xen/scripts/network-bridge $@

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). I run a virtual pfsense firwall in a DomU. I created multiple bridges. The interfaces itself (except eth2 (connected to br_lan)) itself don't have a IP assigned. I use them to connect to other devices. grep my-network /etc/xen/xend-config.sxp (network-script my-network-script) root at

Hi all, Up until now, we''ve been using Xen 3.0 on CentOS 5.x. Under this setup, dom0 was given a virtual ''ethX'' with the original ''ethX'' (now ''pethX'') IP address. Under this older config, neither ''pethX'' or ''xenbrX'' had an IP address. The logic was to keep traffic from the domU''s, through

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). This appeared in the messages when i started and stopped a DomU: root at dom0:~# cat messages Aug 31 22:04:52 dom0 kernel: [ 775.569937] device vif6.0 entered promiscuous mode Aug 31 22:04:52 dom0 kernel: [ 775.575993] br_lan: port 2(vif6.0) entering forwarding state Aug 31 22:04:52 dom0 kernel: [

Hello, I was following the steps on creating a new bridge and attaching a physical nic to it. ******Steps mentioned in http://wiki.xensource.com/xenwiki/XenNetworking#head-d5446face7e308f577e5aee1c72cf9d156903722 ***************** if you want to use multiple bridges, you must create them yourself, either manually, or via your own startup script, or via a custom script to replace network-bridge.

I have a strange problem with VLANs with Xen 3.0.4. I signalled it on Xen-users list, but found no definitive solution to it. I configure VLANs so that they are available in dom0; domUs don''t know that they use VLANs. I use a stock "network-bridge" comming from Xen for setting up networking: #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge"

Hi all. What is the canonical way of getting xen to fully work with 802.1q (vlans) ? After (re)searching i found many ways but so far none is working. platform is gentoo (x86/32) and netwerk card a tg3. xen is v3. my config is as follows ... eth0 is simply up (with no ip) and i created several eth0.x interfaces corresponding to several vlans. eth0.10 is de ''default'' vlan

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