On 18/03/13 07:02, Thomas Goirand wrote:
On 03/07/2013 04:23 AM, Daniel Pocock wrote:
Package: release.debian.org
Severity: normal
The current README.Debian is quite old
It gives some advice that will lead to people having a broken system
(e.g. no networking). It describes a procedure for configuring
networking that is completely opposite to what has been described more
recently on the upstream mailing list
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337
I'm happy to overhaul this document and submit a debdiff for the release
team to review - please confirm if this work should go ahead. No other
files in the package will be changed.
Hi Daniel and the release team,
First, thanks Daniel, for taking care of this. I do appreciate such
contributions.
I agree the README is not perfect, though I don't agree it is such a
disaster. The network configuration which I described in it does work,
contrary to what Daniel says. Others also reported using this howto
successfully. What's annoying though, is that to do it, you have to
reboot under a broken networking setup for a while, to be able to do
such a configuration, which is very annoying if you don't have a KVM
over IP in your server.
I have applied all of your git patches. Thanks for them. However, I
cannot apply the part that changes paragraph 4.2, as it did work for me,
and that I would not recommend removing all trace of the network
interface (you would loose network if you reboot without XCP).
The email on the list says that you must do exactly what I described,
empty the /etc/network/interfaces file
This works for me - I have done multiple reboots to test
I also tried re-running the pif-reconfigure-ip a couple of times with
the empty interfaces file, it definitely expects to work that way.
It may be that it works differently for Linux bridge users, I use the
Open vSwitch bridge.
If I do not follow those exact steps, then the dom0 IP networking works,
but XCP fails to add any domU to the xenbr0 bridge and they have to be
bridged using manual brctl commands.
I by the way believe that your paragraph IMPORTANT BUG is important to
add. Mike told me Citrix guys would come back to me with a fix for
#695221 (though it's been weeks I didn't hear about him yet).
Cheers,
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
