We testing with the device in a “registered” state and it allowed access! It
appears to be working as expected. Thank you so much. We were close but had
been trying a different approach with “node role=known_device” under the
connection profile as a filter rather than using the registered vs
Sorry for my ignorance, where is the VLAN filter created?
Louis Scaringella
Security Systems Engineer
Yellow Dog Networks, Inc
785-342-7903
> On Jun 4, 2020, at 9:56 PM, Durand fabrice via PacketFence-users
> wrote:
>
> Hello Louis,
>
> my answer bellow.
>
> Le 20-06-04 à 21 h 53, Louis
Ok, thank you. I think I have it setup and will test as soon as I can.
I think most of the filter you mentioned is self-explanatory, but wanted to
clarify on the “scope”. Is the scope just the area of PacketFence where this
determination is being made, in my case it would be the registration
Initial testing shows this working with an “unregistered” device and this is
what shows in the Radius audit logs.
Reply-Message = "This node is not allowed to use this service”
Louis Scaringella
Security Systems Engineer
Yellow Dog Networks, Inc
785-342-7903
> On Jun 4, 2020, at 10:40 PM,
https://mgmt_ip:1443/admin/alt#/configuration/filter_engines
Le 20-06-04 à 23 h 28, Louis Scaringella a écrit :
Sorry for my ignorance, where is the VLAN filter created?
Louis Scaringella
Security Systems Engineer
Yellow Dog Networks, Inc
785-342-7903
On Jun 4, 2020, at 9:56 PM, Durand
Hello Louis,
my answer bellow.
Le 20-06-04 à 21 h 53, Louis Scaringella via PacketFence-users a écrit :
Hello,
Thank you for your time in helping.
I am working with a client and the goal is to build upon the current 802.1X
PEAP environment they have with Windows NPS and expand this to use
Hello,
Thank you for your time in helping.
I am working with a client and the goal is to build upon the current 802.1X
PEAP environment they have with Windows NPS and expand this to use PacketFence
and to limit BYOD by using MAC address authentication in conjunction with
802.1X PEAP.
