Starting a new Xen setup, with off-the-shelf Wheezy, and the standard Xen
packages,
which turn out to be Xen 4.1
I used to just put a (network-script network-bridge) in the Xen setup, but I
guess
you can''t do that anymore...
There are a variety of recipes to setup the network and bridging, since
apparently
the Xen setup doesn''t does this for you anymore. I''ve gone
through a couple
tries, with no success so far.
Following instructions in /usr/share/doc/xen-utils-common/README.debian,
I created a /etc/network/interfaces file like this:
auto br0
iface br0 inet static
address 192.168.0.26
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
bridge_ports all
When the machine reboots, I see:
br0 Link encap:Ethernet HWaddr 00:1e:4f:11:51:5f
inet addr:192.168.0.26 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2174 errors:0 dropped:0 overruns:0 frame:0
TX packets:531 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:316591 (309.1 KiB) TX bytes:67600 (66.0 KiB)
eth0 Link encap:Ethernet HWaddr 00:1e:4f:11:51:5f
inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2601 errors:0 dropped:0 overruns:0 frame:0
TX packets:648 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:508220 (496.3 KiB) TX bytes:84048 (82.0 KiB)
Interrupt:16 Memory:f8000000-f8012800
So, the eth0 physical interface somehow picked up .104, likely from DHCP-
but I don''t know why.
And I get wierd ping responses. A ping on the local network works fine, but try
to move out to the next network yields:
james@puerto:/usr/share/doc/xen-utils-common$ ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
From 192.168.0.104 icmp_seq=1 Destination Host Unreachable
From 192.168.0.104 icmp_seq=2 Destination Host Unreachable
The ICMP reply comes from the .104 address? ???
Does anyone know the correct configuration in /etc/network/interfaces for
a dead-simple bridge to support Xen domU''s?
thanks!
James
James Triplett <jm-xenusers@vj8.net> schrieb:> >Starting a new Xen setup, with off-the-shelf Wheezy, and the standard >Xen packages, >which turn out to be Xen 4.1 > >I used to just put a (network-script network-bridge) in the Xen setup, >but I guess >you can''t do that anymore...>Does anyone know the correct configuration in /etc/network/interfaces >for >a dead-simple bridge to support Xen domU''s?For first check your bridge setup (which is not xen related - see bridge-utils / linux bridge or better debian bridge networking for any details of you OS, but should be simple): To watch and manipulate bridges you should have brctl ("brctl help" gives you a list of commands/options). See is you bridge is up and all the required intercaces (including the "outer side physical") are in the bridge: brctl show As the first step - make shure that all of your physical interfaces are up but have no IP configurations (this breaks the principle of bridges) - just your bridge has to have a IP if you want networking from your Dom0: ifconfig or ip addr show and route -n If you want to ping to or from outside to/from your Dom0 ("host system") you need an IP and route on/over your bridge interface, but NOT on the real interfaces! As the second step - with the 4.1 xen / DomU config you just enable bridge config (with the name of your bridge) - this enables xen to add/connect each new DomU interface to your bridge automatically. good luck and best regards, Niels. -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi James, add this line to you /etc/network/interfaces: iface eth0 inet manual Jan Dne 20.5.2013 03:19, James Triplett napsal(a):> Starting a new Xen setup, with off-the-shelf Wheezy, and the standard Xen packages, > which turn out to be Xen 4.1 > > I used to just put a (network-script network-bridge) in the Xen setup, but I guess > you can''t do that anymore... > > There are a variety of recipes to setup the network and bridging, since apparently > the Xen setup doesn''t does this for you anymore. I''ve gone through a couple > tries, with no success so far. > > Following instructions in /usr/share/doc/xen-utils-common/README.debian, > I created a /etc/network/interfaces file like this: > > auto br0 > iface br0 inet static > address 192.168.0.26 > network 192.168.0.0 > netmask 255.255.255.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 > bridge_ports all > > When the machine reboots, I see: > br0 Link encap:Ethernet HWaddr 00:1e:4f:11:51:5f > inet addr:192.168.0.26 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2174 errors:0 dropped:0 overruns:0 frame:0 > TX packets:531 errors:0 dropped:0 overruns:0 carrier:0 > RX bytes:316591 (309.1 KiB) TX bytes:67600 (66.0 KiB) > > eth0 Link encap:Ethernet HWaddr 00:1e:4f:11:51:5f > inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2601 errors:0 dropped:0 overruns:0 frame:0 > TX packets:648 errors:0 dropped:0 overruns:0 carrier:0 > RX bytes:508220 (496.3 KiB) TX bytes:84048 (82.0 KiB) > Interrupt:16 Memory:f8000000-f8012800 > > So, the eth0 physical interface somehow picked up .104, likely from DHCP- > but I don''t know why. > > And I get wierd ping responses. A ping on the local network works fine, but try > to move out to the next network yields: > > james@puerto:/usr/share/doc/xen-utils-common$ ping 192.168.1.4 > PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data. > From 192.168.0.104 icmp_seq=1 Destination Host Unreachable > From 192.168.0.104 icmp_seq=2 Destination Host Unreachable > > The ICMP reply comes from the .104 address? ??? > > > Does anyone know the correct configuration in /etc/network/interfaces for > a dead-simple bridge to support Xen domU''s? > > thanks! > > James > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
And change line: bridge_ports all to: bridge_ports eth0 Jan Dne 20.5.2013 03:19, James Triplett napsal(a):> Starting a new Xen setup, with off-the-shelf Wheezy, and the standard Xen packages, > which turn out to be Xen 4.1 > > I used to just put a (network-script network-bridge) in the Xen setup, but I guess > you can''t do that anymore... > > There are a variety of recipes to setup the network and bridging, since apparently > the Xen setup doesn''t does this for you anymore. I''ve gone through a couple > tries, with no success so far. > > Following instructions in /usr/share/doc/xen-utils-common/README.debian, > I created a /etc/network/interfaces file like this: > > auto br0 > iface br0 inet static > address 192.168.0.26 > network 192.168.0.0 > netmask 255.255.255.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 > bridge_ports all > > When the machine reboots, I see: > br0 Link encap:Ethernet HWaddr 00:1e:4f:11:51:5f > inet addr:192.168.0.26 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2174 errors:0 dropped:0 overruns:0 frame:0 > TX packets:531 errors:0 dropped:0 overruns:0 carrier:0 > RX bytes:316591 (309.1 KiB) TX bytes:67600 (66.0 KiB) > > eth0 Link encap:Ethernet HWaddr 00:1e:4f:11:51:5f > inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2601 errors:0 dropped:0 overruns:0 frame:0 > TX packets:648 errors:0 dropped:0 overruns:0 carrier:0 > RX bytes:508220 (496.3 KiB) TX bytes:84048 (82.0 KiB) > Interrupt:16 Memory:f8000000-f8012800 > > So, the eth0 physical interface somehow picked up .104, likely from DHCP- > but I don''t know why. > > And I get wierd ping responses. A ping on the local network works fine, but try > to move out to the next network yields: > > james@puerto:/usr/share/doc/xen-utils-common$ ping 192.168.1.4 > PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data. > From 192.168.0.104 icmp_seq=1 Destination Host Unreachable > From 192.168.0.104 icmp_seq=2 Destination Host Unreachable > > The ICMP reply comes from the .104 address? ??? > > > Does anyone know the correct configuration in /etc/network/interfaces for > a dead-simple bridge to support Xen domU''s? > > thanks! > > James > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, May 20, 2013 18:02, Niels Dettenbach wrote:> > > James Triplett <jm-xenusers@vj8.net> schrieb: > >> >>Starting a new Xen setup, with off-the-shelf Wheezy, and the standard >>Xen packages, >>which turn out to be Xen 4.1 >> >>I used to just put a (network-script network-bridge) in the Xen setup, >>but I guess >>you can''t do that anymore... > >>Does anyone know the correct configuration in /etc/network/interfaces >>for >>a dead-simple bridge to support Xen domU''s?allow-hotplug eth0 auto xenbr0 iface xenbr0 inet static address 10.20.30.34 netmask 255.255.240.0 gateway 10.20.30.254 bridge_maxwait 5 bridge_ports regex eth0 The above is what I use on one of my xen hosts. You would also have the lo sections, but you don''t need anything else referring to eth0 Essentially, the bridge is just like a normal eth0 interface, except you add the extra bridge_ports config line. Hope that helps. Regards, Adam
Hello. El 19/05/13 20:19, James Triplett escribió:> Following instructions in /usr/share/doc/xen-utils-common/README.debian, > I created a /etc/network/interfaces file like this: > > auto br0 > iface br0 inet static > address 192.168.0.26 > network 192.168.0.0 > netmask 255.255.255.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 > bridge_ports allThis looks pretty nice, should work as is, maybe with few corrections: 1. The specification of "network" and "broadcast" may be safely omitted, ifupdown scripts do excellent job deducing this parameters. Omitting them leaves you less room to make a mistake. 2. Consider adding "bridge_stp off" parameter. http://wiki.xen.org/wiki/Xen_Bridge_Loop#Why_STP_is_turned_off.3F 3. Specify "eth0" in bridge_ports, it would make things more explicit. 4. IMPORTANT Make sure eth0 is not configured elsewhere. Comment out any "auto eth0" or "allow-hotplug eth0" (contrary to what Adam Goryachev suggested) in /etc/network/interfaces. Make sure any network automated configuration tool is turned off, such as Debian''s NetworkManager.> Does anyone know the correct configuration in /etc/network/interfaces for > a dead-simple bridge to support Xen domU''s?A simple and clean starting /etc/network/interfaces would look like this: ##allow-hotpug eth0 #iface eth0 inet static # address 192.168.0.26 # netmask 255.255.255.0 # gateway 192.168.0.1 auto br0 iface br0 inet static address 192.168.0.26 netmask 255.255.255.0 gateway 192.168.0.1 bridge_ports eth0 bridge_stp off #<and nothing else> Greetings. -- Alexandre Kouznetsov
On (20/05/13 10:11), Jan Hejl wrote:> Date: Mon, 20 May 2013 10:11:41 +0200 > From: Jan Hejl <jh@excello.cz> > To: xen-users@lists.xen.org > Subject: Re: [Xen-users] Bridge networking in Debian > > Hi James, > > add this line to you /etc/network/interfaces: > > iface eth0 inet manualSuccess! Adding that line got me going again. And due to other''s info I got the rest of it working. Thanks to all who replied. To summarize, for Xen 4.1 on Debian Wheezy 7.0, what worked was: 1. Make the bridge yourself, rather than let xend do it. For Debian, this is in /etc/network/interfaces: iface eth0 inet manual auto br0 iface br0 inet static address 192.168.0.26 network 192.168.0.0 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.1 bridge_ports all 2. Leave xend-config.sxp untouched (all default, no ''network-script''). 3. For the domU, a simple line: vif = [ ''bridge=br0'' ] cheers, James> > Jan > > Dne 20.5.2013 03:19, James Triplett napsal(a): > >Starting a new Xen setup, with off-the-shelf Wheezy, and the standard Xen packages, > >which turn out to be Xen 4.1 > > > >I used to just put a (network-script network-bridge) in the Xen setup, but I guess > >you can''t do that anymore... > > > >There are a variety of recipes to setup the network and bridging, since apparently > >the Xen setup doesn''t does this for you anymore. I''ve gone through a couple > >tries, with no success so far. > > > >Following instructions in /usr/share/doc/xen-utils-common/README.debian, > >I created a /etc/network/interfaces file like this: > > > > auto br0 > > iface br0 inet static > > address 192.168.0.26 > > network 192.168.0.0