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 the bridge and out ''pethX'' without dom0 seeing anything. This is particularly useful in our environment (2-node cluster using DRBD to allow hot-migration and disaster recovery between nodes). Here is what I am talking about, in graph form: http://wiki.alteeve.com/index.php/Networking_in_Xen#Real_World_Example I''d like to keep this setup, but it seems under Xen 3.4 this is no longer the default configuration. I created a simple ''network-script'' with: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 ... "$dir/network-bridge" "$@" vifnum=N netdev=ethN bridge=xenbrN What else do I need to do to get the virtual copies of ''ethX'' back on my dom0? Thanks! -- Digimer E-Mail: linux@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Sep-13 09:00 UTC
Re: [Xen-users] Setting up virtual ''ethX'' devices in Xen 3.4
On Sat, Sep 11, 2010 at 1:20 AM, Digimer <linux@alteeve.com> wrote:> The logic was to keep traffic from the > domU''s, through the bridge and out ''pethX'' without dom0 seeing anything.That''s not entirely true. dom0 still see all the traffic, and (on default Centos setup) applies iptables rules to them.> I''d like to keep this setup, but it seems under Xen 3.4 this is no > longer the default configuration. I created a simple ''network-script'' with: > > #!/bin/sh > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 > ... > "$dir/network-bridge" "$@" vifnum=N netdev=ethN bridge=xenbrN > > What else do I need to do to get the virtual copies of ''ethX'' back on > my dom0?It should not really matter. The default setup now uses eth0 as the name of the bridge (instead of xenbr0). Dom0 still see all domU traffic, so function-wise nothing changed much. If you still want old-style bridge setup anyway, you might be able to copy /etc/xen/scripts/network-brige (and possibly some other files it depends on) from the default Centos installation. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users