Thanks Mike and Thomas for clarifying the issue. The reason I picked Critical was because of it's "description"...
The part that applied to me was "makes unrelated software on the system (or the whole system) break" when i loose network connectivity, to me, that is broken. In my case, the severity comes from a business standpoint. I manage the servers and someone else manages the network. In this case, they WILL NOT(Refuse) change the local network subnet just because of programming errors that will/should be fixed in the future. The reason why I didn't go upstream (besides not knowing where to go) was that In another installation of XCP from xensource works fine with my non /24 subnets. Only on Debian do I see this. So now I feel like this won't be addressed.. I'm sure I am not the only one with this problem. I also don't understand what you mean by : >This doesn't match *at all* your bug report. >> And I get network access this way. >> The problem is that my network isn't configured like this and I don't want >> to change it just to accomodate this setup. >> >> I also tried with other subnetmasks such as /25 /26 /27 ... and none of them >> worked except for /24. >> >> Any help is appreciated! I gave the problem and then the "solution" of what worked.. how does that not match? Perhaps I need to be educated on the "debian way" of bug reporting.. I am all ears.. Marc
