When a host that uses WoL is attached through an 802.1X port and the host powers off, the 802.1X port becomes unauthorized. T he 802.1X authentication with Wake-on-LAN (WoL) feature solves the problem. I researched the main networking vendors and found that they had solutions. I figured that this couldn't a new problem and that it would be possible to overcome this in the enterprise. Therefore the switch ports becomes blocked in both directions and prevents the WoL magic packet from being delivered - a chicken and egg situation. One of the features of 802.1x is that devices are quarantined when they are turned off. Port-based network access control uses the physical characteristics of a switched LAN infrastructure to authenticate devices that are attached to a LAN port and to prevent access to that port in cases where the authentication process fails. This is the case with WoL and 802.1x authentication.Ĩ02.1x is a standard for port-based network access control that provides authenticated network access to 802.11 wireless networks and wired Ethernet networks. It's either untested or will not work in all scenarios. ![]() I wondered why so I carried out some additional research.Īs with all Microsoft support statements, just because something is not supported doesn't mean that it will not work. One of the things I pointed out was that the feature was not supported using 802.1x authentication. I recently carried out some testing on the new Wake on LAN feature of ConfigMgr 1810 and published the result in this blog post.
0 Comments
Leave a Reply. |