WiFi comes up and clients are being associated, but they cannot get an IP address because dnsmasq is not running.Now dnsmasq cannot start because /tmp/adb_list.overall does not exist yet.Once everything is setup, the router is rebooted.Upon the first activation, adblock adds an entry to /etc/config/dhcp: option serversfile '/tmp/adb_list.overall'.WiFi clients start getting associated between steps 2 and 3 above and a second or two after step 3 they start getting IP addresses.It looks like after the network interfaces are up, dnsmasq is restarted via SIGTERM.wifi is started a bit later by S20network.dnsmasq is started by S19dnsmasq and the expectation is that it comes up very quickly.There are actually two issues helping each other make things worse. If ping -qc $NUMP $TARGET >/dev/null thenĮcho "wol.sh: $TARGET is alive" | $LOGGERĮcho "wol.sh: $TARGET not responding to pings" | $LOGGERĮcho "wol.sh: $WOL -b -i $WOLIF $MAC" `$WOL -b -i $WOLIF $MAC` | $LOGGER I did something similar in the WOL script below (now modified but you'll get the idea) VERSION=0.2Įcho "wol.sh: version $VERSION started" | $LOGGER Or writing a watch script to grep for " 'pppoe-wan' link is up" in the logs. Slowing down your whole wifi net seems silly to fix google &/or apple's issues Then manual bring wifi back up and see what happens with your clientsįiguring out how to slow wifi down could be as simple as a sleep command to an init scriptĮDIT: if you do this, perhaps slow down the wifi connection of specific clients by their MAC address. Sat Nov 9 12:50:40.796 en0: Terminating supplicant. Sat Nov 9 12:50:40.776 Unexpected payload found for message 9, dataLen 0 Sat Nov 9 12:50:37.238 initWithInterfaceAndIE: _myMacAddress XX:XX:XX:XX:XX:XX Sat Nov 9 12:50:37.238 parseRSNIE: groupCipherType = 5 pairwiseCipherType = 5 authSel = 6 Sat Nov 9 12:50:35.856 en0: Terminating supplicant. Sat Nov 9 12:50:35.836 Unexpected payload found for message 9, dataLen 0 Sat Nov 9 12:50:32.291 initWithInterfaceAndIE: _myMacAddress XX:XX:XX:XX:XX:XX # The following six lines are missing on MacBook when wireless is restarted on the router with **wifi** command. Sat Nov 9 12:50:32.291 parseRSNIE: groupCipherType = 5 pairwiseCipherType = 5 authSel = 6 Sat Nov 9 12:50:31.987 en0: Terminating supplicant. Sat Nov 9 12:50:31.968 Unexpected payload found for message 9, dataLen 0 Sat Nov 9 12:50:28.438 initWithInterfaceAndIE: _myMacAddress XX:XX:XX:XX:XX:XX Sat Nov 9 12:50:28.438 parseRSNIE: groupCipherType = 5 pairwiseCipherType = 5 authSel = 6 Sat Nov 9 12:50:28.314 _processIPv4Changes: ARP/NDP offloads disabled, not programming the offload Sat Nov 9 12:50:28.298 _processIPv4Changes: ARP/NDP offloads disabled, not programming the offload Sat Nov 9 12:50:28.254 RSNSupplicant: Releasing authenticator for YY:YY:YY:YY:YY:YY Sat Nov 9 12:50:28.254 en0: Terminating supplicant. Sat Nov 9 12:50:28.163 en0: link down event, informing supplicant. Sat Nov 9 12:50:28.156 IO80211AssociationJoinSnapshot::captureRequestCallback Problem reported from corecapture I also tried restarting the wireless and noticed the difference: the middle portion of the log is missing during a wifi restart, but is present during a router reboot. When the router is up and I see the AP, the MacBook is not even trying to connect: no activity in any logs until I manually connect it to the AP. When the router is coming down I see these messages below in wifi.log. I am experiencing the same issue with a MacBook (it can never reconnect after a router reboot while Chromecast sometimes does) and I can provide logs for it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |