Hi Enrico, I also got hit by but 329419, and it bothered me for, dunno, a year by now? Today, I got around to track it down. I started by reading through the ifupdown code, then had a look at the ifplugd code, could track the problem down to guessnet, rebuild guessnet not do link detection, which did not help, when I finally, with help from this bug report, I found the culprit.
Do you really thing it is necessary to ifconfig up the interface before and ifconfig down after checking the essid? At least with my driver (madwifi), this will clear any AP information anyways... At least, please change it to "if the interface is up, that's fine and leave it, if not, I bring it up before and down after, just as now". A simple if /sbin/ifconfig $IFACE|grep -q UP then bringitdown=yes ifconfig $IFACE up fi .. if [ "$bringitdown" = "yes" ] then ifconfig $IFACE down fi should do it. Thanks, and greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
