Technical Configuration Guide for Wake on LAN with Ethernet Edge Switched
10
November_2010
avaya.com
4. Wake on LAN: 802.1x Authentication
Wake on LAN and 802.1x authentication are mutually compatible only if the sleeping workstation is able
to receive the magic packet. When an Ethernet switch port is configured with 802.1x enabled, traffic to
and from the PC is dropped until the PC is authenticated. This could be a problem for WoL, as the magic
packet would normally be dropped by the Ethernet switch before it ever reached the intended PC.
The Ethernet Switch 470, Ethernet Switch 425, and Ethernet Routing Switch 5500 series have a feature
(traffic-control) that allows traffic from the network to the workstation even when the authentication
process is not yet done.
From the CLI
(config-if)#eapol traffic-control [port <portlist>] [in] [in-out]
port
Specifies the port or list of ports to configure for EAPOL
in
Incoming traffic is blocked on EAP authentication failure
in-out Incoming and outgoing traffic blocked on EAP authentication failure
In this context, incoming traffic refers to the traffic coming from the PC into the Ethernet switch port. In
order for the WOL magic packet to be passed to the PC while the port has 802.1x enabled, the switch
port must be configured as follows:
(config-if)#eapol traffic-control 2/20 in
From Java Device Manager (JDM):
