Re: [Xen-users] Bridge networking in Debian

[Jan Hejl <jh@xxxxxxxxxx>]

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@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

Attachment: smime.p7s
Description: Elektronicky podpis S/MIME

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users