- Mar 7, 2006
- 1,006
- 0
- 76
I'm fliddling around with WoWLAN for a desktop that is not connected to the rest of my home Ethernet network.
Background: In my current setup, the desktop is connected by Ethernet to an old router that I've set up as a wireless client bridge, and I'm using traditional WoL to wake it up (but still using the desktop's internal WiFi--an Intel 6xxx card--for actual connectivity since that performs much better than this old single-band router). Since the wireless bridge is being used for WoL and nothing else and since the Intel 6xxx series support WoWLAN, I'm trying to switch over to using WoWLAN so that I can get rid of this otherwise useless wireless bridge.
The parts that work: Almost everything, actually. It works beautifully and reliably when waking from both sleep and hibernate.
The one part that doesn't work: The computer wakes up periodically to rekey.
The "Advanced" tab of the device driver configuration has the following option: "GTK rekeying for WoWLAN", which defaults to Enabled. Examining the INF file, this option corresponds to the PMWiFiRekeyOffload parameter, which according to Microsoft's documentation, means that GTK rekeys can be offloaded to the wireless card when the computer sleeps.
So the GTK offload is enabled (as it is by default), and I've also set the EnableWoWLAN registry value to enable GTK handling.
Yet, like clockwork, this Intel WLAN card wakes up the desktop (as in, the entire system wakes up) every hour at the exact same time, presumably to rekey (the rekey interval on my wireless router is set to one hour). I thought the whole point of the GTK offload was so that these periodic rekeys can be handled by the NIC without waking up the entire system?? (Yes, I could jack up the rekey interval so it wakes up less frequently than once-per-hour, but I'd much rather prefer that it not wake up at all for rekeying.)
So my question is, has anyone managed to get WoWLAN working without the whole system waking up to rekey? If so, what am I doing wrong? Is this a client-side problem, or is there a problem with my wireless router?
Or is WoWLAN just some half-baked thing that I should avoid?
Background: In my current setup, the desktop is connected by Ethernet to an old router that I've set up as a wireless client bridge, and I'm using traditional WoL to wake it up (but still using the desktop's internal WiFi--an Intel 6xxx card--for actual connectivity since that performs much better than this old single-band router). Since the wireless bridge is being used for WoL and nothing else and since the Intel 6xxx series support WoWLAN, I'm trying to switch over to using WoWLAN so that I can get rid of this otherwise useless wireless bridge.
The parts that work: Almost everything, actually. It works beautifully and reliably when waking from both sleep and hibernate.
The one part that doesn't work: The computer wakes up periodically to rekey.
The "Advanced" tab of the device driver configuration has the following option: "GTK rekeying for WoWLAN", which defaults to Enabled. Examining the INF file, this option corresponds to the PMWiFiRekeyOffload parameter, which according to Microsoft's documentation, means that GTK rekeys can be offloaded to the wireless card when the computer sleeps.
So the GTK offload is enabled (as it is by default), and I've also set the EnableWoWLAN registry value to enable GTK handling.
Yet, like clockwork, this Intel WLAN card wakes up the desktop (as in, the entire system wakes up) every hour at the exact same time, presumably to rekey (the rekey interval on my wireless router is set to one hour). I thought the whole point of the GTK offload was so that these periodic rekeys can be handled by the NIC without waking up the entire system?? (Yes, I could jack up the rekey interval so it wakes up less frequently than once-per-hour, but I'd much rather prefer that it not wake up at all for rekeying.)
So my question is, has anyone managed to get WoWLAN working without the whole system waking up to rekey? If so, what am I doing wrong? Is this a client-side problem, or is there a problem with my wireless router?
Or is WoWLAN just some half-baked thing that I should avoid?
Last edited:
Facebook
Twitter