You are correct that by default the Xen package(s) will not seutp
 the bridge.

  Your solution of adding the bridge manually will work, but it
 isn't the preferred solution.

  Instead you should edit the file /etc/xen/xend-config.sxp

  Comment out:

    (network-script network-dummy)

  Uncomment the line:

    (network-script network-bridge)

  This will cause the Xen to create the bridge for you automagically.
 The bonus of this approach is that it will allow your system to be
 unchanged, and will allow your Xen host to have a bridge setup even
 when using a DHCP address.

  This is covered in the manual I believe, if not I've certainly
 documented it in the past:

    http://www.debian-administration.org/tag/xen

  Anyway.  I think that forcing this issue is wrong:

    a)  The user might get broken networking if I tried to enable it.

    b)  It makes unexpected changes to the host.

    c)  The host might be using a different network setup, such as
       network-dummy, or network-nat.

  If you have no objection I'm going to close this bug report.  If
 you do I will tag it 'wontfix' unless you can offer a convincing
 argument that all users of Xen will want to use a bridge ...

Steve
-- 
# The Debian Security Audit Project.
http://www.debian.org/security/audit

Attachment: signature.asc
Description: Digital signature

Reply via email to