Tuesday
Hi there,
i have a problem, which i hoped, was already solved. I read the corresponding article and did all which there wass recommended, but without success.
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000082951
That's why i post here.
We have several new universal switches (5420M; OS 31.3.1.3) to which our client computers (windows 11) are connected. We use a central management software to manage the clients. The server software tries to wakeup the clients to install patches, software and ... Therefore the software sends WoL magic packets to the clients, which then starts the windows OS. This worked fine for years until we configured 802.1x netlogin on the summit switches, better the ports of it.
Now the clients won't start, because the switching engine does not forward the magic WoL packet to the clients until they are authenticated..
I created a vlan named WoL-clients with dummy ip of the client vlan, created a policy as described and then bound the policy to that vlan
configure vlan <source-vlan> udp-profile <name>
After that i tried to wakeup a client with no success. So now i have 2 questions:
a) which ip address would have been the correct one?
b)
Thanks in advance for your help. Any hints why that didn't work are highly appreciated?
Best wishes, fritte
10 hours ago
Hi Fritte,
I _think_ the answers to your questions are as follows, although it's been a while since I've work with WoL and policy:
1) A placeholder VLAN needs to be created and assigned to all ports that may need to receive WoL packets.
2) The IP of the placeholder VLAN doesn't matter, I think the IP is only needed for the UDP profile to work.
3) The UDP profile should be assign to the VLAN where WoL packets come into the switch, not the placeholder VLAN
4) However, the UDP profile should use the action 'vlan <placeholderVLAN>' which effectively states 'flood the traffic that has been matched by the profile (WoL Packets) into the placeholder VLAN'
Hope that helps!