[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Reverting bridge/antispoofing param removal

  • To: Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Nivedita Singhvi <niv@xxxxxxxxxx>
  • Date: Fri, 28 Oct 2005 01:14:18 -0700
  • Delivery-date: Fri, 28 Oct 2005 08:11:36 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

While cleaning up some other stuff in this area, I looked
into a problem Sean Dague ran into - he was specifying br0
as the bridge name in xend-config.spx and it was still using
the original default xenbr0.  When the bridge name is
specified in the network-bridge script, it is created
correctly (ditto anti-spoofing).

A recent patchset:

removed the parameters vif-bridge and anti-spoofing from
the xend/vifctl.py as the script was allowing them
to be configured.

The config file still has the examples, however, which
results in the user setting those parameters in
xend-config.spx futilely.  The actual parameter that is
used is the default (unless overridden in the script).
The intent seems to be to allow the user to configure
it in the script, and avoid the redundancy of overriding
via xend.

Would you rather have a patch that removes the example
from the xend-config.spx script, so as not to confuse the
user (but this would need sanitizing xend to use the right
params) or restore the original piece of code? It latter
worked well before, you could set it in one place and
have it be seen by script and xend.

I had both in test, will send off whichever is
desirable when I get in tmrw..


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.