Sadly our issue may be even more complicated since we have Extreme Networks 
switches and they don't appear to act the same way as the Ciscos. Since we 
aren't replacing our network switches, it sounds like our only options with the 
Extreme switches is to look into a way to query PacketFence as you mentioned. 
Maybe a Powershell script?

-----Original Message-----
From: Jason Frisvold [[email protected]]
Received: Thursday, 14 Aug 2014, 8:40PM
To: [email protected] 
[[email protected]]
Subject: Re: [PacketFence-users] 802.1x and Wake on LAN with PacketFence

Stormont, Stephen (IMS) wrote:
> It looks like it may only be Cisco switches that support WOL and 802.1x.

We continue to struggle with this.  Yes, Cisco supports WoL with 802.1x.
 And it works, if you can direct the WoL packet to the right place.

In our network, we have a number of different VLANs.  And, each VLAN is
broken into lots of subnets based on switch stacks.  When a system is
turned off, or is machine auth'ed, then it ends up in a holding VLAN
intended to separate the machines away from the production network.
There are a few problems.  First, the default "holding" network that
Cisco uses is VLAN 1.  We don't have that routed, so there's actually no
way to get to it.

You can configure the holding network, though (the switchport access
vlan XXXX command) and then you have a definitive place to send the
packet.  And then we come to our next problem.  We're using Landesk,
which is apparently a braindead solution.  If the machine isn't in the
same place it was a moment ago, Landesk apparently has no way of
discovering where the machine is now.  Very frustrating.

If you're using a management solution that can be programmed, however,
this is a really easy task.  Just ask packetfence where the machine is.
 For our network, I can tell you where a machine is via a direct answer
from packetfence, or by using the switch/port information that
packetfence has to determine what the "resting" VLAN would be.

This should all work with MAB as well.  In fact, it's easier since the
VLAN shouldn't change when you turn off the machine.  Well, unless you
configure things a bit differently, that is.

--
---------------------------
Jason 'XenoPhage' Frisvold
[email protected]
---------------------------

"Any sufficiently advanced magic is indistinguishable from technology.\"
- Niven's Inverse of Clarke's Third Law

------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

________________________________

Information in this e-mail may be confidential. It is intended only for the 
addressee(s) identified above. If you are not the addressee(s), or an employee 
or agent of the addressee(s), please note that any dissemination, distribution, 
or copying of this communication is strictly prohibited. If you have received 
this e-mail in error, please notify the sender of the error.

------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to