Simon Kelley <si...@thekelleys.org.uk> writes: > Thanks. Of my two options above, this is clearly 2), since you're not > using /etc/resolv.conf:
> Dec 23 08:51:05 belmer dnsmasq[2516]: warning: ignoring resolv-file flag > because no-resolv is set > There follows lots of logged queries which don't get forwarded anywhere, > as there's no route to the upstream nameservers. These will have > received answers with RCODE set to REFUSED. > Then NetworkManager does stuff, and as soon as it gets to > Dec 23 08:51:36 belmer NetworkManager[2099]: <info> Activation (wlan0) > Stage 2 of 5 (Device Configure) complete. > dnsmasq stops getting errors when it sends UDP packets and starts > forwarding queries. There are no replies from upstream at this point, > which is no great surprise as wlan0 doesn't have an IP address. The > REFUSED answers will have stopped at this point, instead there will be > no answer. Aha! I was working under the incorrect assumption that dnsmasq was all that was needed after boot to enable networking, but actually NetworkManager is involved in getting basic connectivity. Yes, I don't think there's anything that dnsmasq can do, nor do I think there's anything that OpenAFS can do in this case. If one is using NetworkManager, network services just won't be available at boot, and nothing one can put into the init script will help. They won't be available until after NetworkManager runs and authenticates, which often has to wait until the user logs in so that NetworkManager has access to wireless authentication credentials. > Could AFS be fixed to retry DNS queries after a longish timeout either > when there's no reply or when a REFUSED rcode is received? The behaviour > of ntpd in the log above shows fairly well how to get it right. Starting AFS when there's no network available should generally work when using dynroot provided that one doesn't attempt to access any files in AFS until the network is available, but one will get timeouts if one tries to access AFS before the network is present. > It's not clear to me that there exists any sane change in the behaviour > of dnsmasq that would help things. Agreed. I think the bug against dnsmasq can be closed. Brent, I'm confused by the bug history here: what happens when AFS doesn't start? Your log messages in the original bug report only show a log message that isn't printed, so far as I know, by the init script that comes with the openafs-client package. What sort of behavior do you see when AFS is started prior to the network being available? -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
