[Bug 144711] Re: network-bridge script get wrong vifnum

2007-10-08 Thread Chuck Short
xen-3.1 (3.1.0-0ubuntu17) gutsy; urgency=low * Fix network bridge due to ifplugd changes (LP: #144711) * Fix HVM so that mouse doesnt get stuck on the left side of the screen. (LP: #140963) -- Chuck Short [EMAIL PROTECTED] Sat, 06 Oct 2007 13:18:06 -0400 ** Changed in: xen-3.1

[Bug 144711] Re: network-bridge script get wrong vifnum

2007-10-07 Thread Chuck Short
Will be uploaded soon. ** Changed in: xen-3.1 (Ubuntu) Status: New = Fix Committed -- network-bridge script get wrong vifnum https://bugs.launchpad.net/bugs/144711 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 144711] Re: network-bridge script get wrong vifnum

2007-09-28 Thread Nicklas Svanteson
I can confirm this bug. The line provided by Dyno: vifnum=${vifnum:-$(ip route list | sed -n -r -e s/^default.+dev[^0-9]+([0-9]+).*$/\1/p)} solved the problem for me. Thanks -- network-bridge script get wrong vifnum https://bugs.launchpad.net/bugs/144711 You received this bug notification

[Bug 144711] Re: network-bridge script get wrong vifnum

2007-09-27 Thread Henrik Riomar
This is due to a change in ifupdown ifupdown (0.6.8ubuntu8) gutsy; urgency=low * ifupdown.nw: use 100 as default route metric unless an explicit metric parameter is set in /etc/network/interface; this applies for static and dhcp interfaces and passes the -e IF_METRIC=%metric% option to

[Bug 144711] Re: network-bridge script get wrong vifnum

2007-09-26 Thread Fastguy
I confirm. I was playing with interfaces, unplugged an external USB interface, plugged the cable to another interface etc, then while checking my ifconfig output, here's what I've found: xenbr100 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64