Excuse me for the delay- I haven't been checking my email regularly over the
holiday.
I can tell you that I resolved my issues by disabling the automatic creation
of a bridge at boot. As I said in my first report, even when I disable
bridge creation at boot, then restart /etc/init.d/networking with the
original config in place, it still hangs. However, when I execute all the
necessary commands manually all works properly. This behavior is best
explained by an error in my configuration, only it worked perfectly before
upgrading to Gutsy and even once upgraded, by booting the former kernel.
For the time being I've written a simple script that I run manually after
reboots to create and configure the bridge.
I realize I'm not familiar with the the Ubuntu approach to multiple kernel
versions. Which modules versions are loaded along with a specific kernel
version? For example, when I was booting the previous kernel, was it also
loading a previous version of madwifi also left over from Fesity? Might
therefore the error live in the madwidi package? I was born a Gentoo boy
where we just compiled kernels with the proper drivers built right in and
avoided this fancy-dancy module business as much as possible (my /boot
directory used to fit on a 32MB partition with 6 different kernels, now it's
62MB with just the one kernel).
I would love to test Hardy Heron, only given the woes I experienced
upgrading to Gutsy (network bridging wasn't my only headache) I have to wait
until I have more time to devote to work out any kinks.
For the time being, considering network bridging works when established by
hand or script, I suspect the "bug" was due to an idiosyncrasy in my config
and not a serious error in the kernel or driver images. Still, I wonder why
it worked under Feisty and not Gutsy. For good measure, here's the guilty
/etc/network/interfaces (mostly derived from the madwifi documentation):
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
auto ath0
iface ath0 inet manual
#first get rid of madwifi's initial wireless virtual interface
#and rebuild it in Master mode
pre-up wlanconfig ath0 destroy
pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
post-down wlanconfig ath0 destroy
wireless-mode master
wireless-channel 4
wireless-essid bearNet
auto br0
iface br0 inet static
address 192.168.1.127
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.
bridge_ports eth0 ath0
-Ian
On Dec 28, 2007 12:46 AM, Leann Ogasawara <[EMAIL PROTECTED]> wrote:
> Hardy Heron Alpha2 was recently released. It contains an updated
> version of the kernel. You can download and try the new Hardy Heron
> Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ .
> You should be able to then test the new kernel via the LiveCD. If you
> can, please verify if this bug still exists or not and report back your
> results. General information regarding the release can also be found
> here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!
>
> --
> kernel hangs when initializing network bridge
> https://bugs.launchpad.net/bugs/150839
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
kernel hangs when initializing network bridge
https://bugs.launchpad.net/bugs/150839
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
