This is on an 802.11g (sw00) channel, since there seems to be an issue with DNS on the .11a (sw10) channel. Interestingly enough, when I associate with the .11a guest (sw11) channel, the DNS works. (Go figure; would you like me to file a bug report on that?)
I’ve seen this too. bind9 is supposed to scan the available interfaces every two minutes, and it seems possible to trigger a new scan when a new interface comes up OR have some linux specific monitoring thing (inotify, kernel event?)
Certainly all the wireless interfaces are not active when named starts…
I also note that this report is AFTER we upgraded to bind 9.8.1….
Thank you for the spot! as this disabled dhcp entirely on the main wireless interfaces it was very bad…
Just confirming that rc6 has fixed the issue for me.
Possibly related are the following “bad number” error messages from logread:
Sep 14 08:59:53 Lirpo5 daemon.warn radvd[4403]: resetting ipv6-allrouters membership on sw00
Sep 14 08:59:54 Lirpo5 daemon.notice ntpd[4468]: ntpd 4.2.6p3@1.2290-o Fri Sep 9 22:12:28 UTC 2011 (1)
Sep 14 08:59:54 Lirpo5 daemon.notice ntpd[4469]: proto: precision = 6.288 usec
Sep 14 08:59:54 Lirpo5 daemon.debug ntpd[4469]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Sep 14 08:59:54 Lirpo5 daemon.err ntpd[4469]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
Sep 14 08:59:54 Lirpo5 user.info sysinit: sh: bad number
Sep 14 08:59:54 Lirpo5 user.info sysinit: sh: bad number
Sep 14 08:59:54 Lirpo5 user.info sysinit: sh: bad number
Sep 14 08:59:54 Lirpo5 user.info sysinit: sh: bad number
Sep 14 08:59:54 Lirpo5 user.info sysinit: setting up led WAN LED (green)
Sep 14 08:59:54 Lirpo5 kern.debug kernel: ar71xx-wdt: enabling watchdog timer
Sep 14 08:59:54 Lirpo5 user.info sysinit: Polipo is starting…