2010/12/21 David Woodhouse <dwmw2@xxxxxxxxxxxxx>: > On Fri, 2010-12-10 at 20:08 +0100, Johannes Berg wrote: >> On Fri, 2010-12-10 at 20:04 +0100, GÃbor Stefanik wrote: >> > On Fri, Dec 10, 2010 at 8:02 PM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote: >> > > On 12/10/2010 12:47 PM, Johannes Berg wrote: >> > >> On Fri, 2010-12-10 at 19:30 +0100, Francesco Gringoli wrote: >> > >> >> > >>> [ 1117.516031] unregister_netdevice: waiting for wlan1 to become free. Usage count = 1 >> > >>> >> > >>> and the device is never release (by who?). I have to reboot. >> > >> >> > >> That's a bug in the ipv6 code, upgrade your kernel :-) >> > > >> > > I would not have seen that as IPv6 is disabled in my kernels. >> > >> > Are you serious? Disabling ipv6 with ipv4 exhaustion expected in January? >> >> Can we stop this thread right here and go on-topic again please? > > On-topic: > > Anyone working on or testing network device drivers should be using > IPv6. IPv6 will exercise code paths and network behaviour that Legacy IP > rarely does, in particular using multicast to do neighbour discovery. > And on wireless networks when multicast will be handled differently by > the AP, that makes more difference than on wired where it's mostly the > MAC filters that get neglected. > > I've seen a number of broken drivers because their authors were only > testing with Legacy IP and not IPv6. > > It's not hard to set up IPv6. Larry, if you need any pointers I'd be > more than happy to help. I've router with OpenWRT, so that probably should be possible for me to setup IPv6. However first I want to have working basic PHY and radio configuration. -- RafaÅ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
