Good Morning Fabrice.
We did the changes and the .in was sent and the ACL was applied. This was
strange because in the ACL name box we change at one point the ACL to be ACL.in
and that did not work (Maybe we had another misconfiguration at that time). We
will revert the code change and test
Sorry Fabrice,
Right now cooking home made fish cakes for the family.
Will try over the weekend and report back of course ;-)
Thanks for your support
Simon
Sent from my Galaxy
Original message
From: Fabrice Durand
Date: 21/01/2022 18:05 (GMT+00:00)
To: Simon Sutcliffe
Hi Fabrice,
We have been using the default cisco switch template as non of our production
switches have templates.
We have 3650 and 2960 in the lab.
Kind Regards
Simon
Sent from my Galaxy
Original message
From: Fabrice Durand
Date: 21/01/2022 16:54 (GMT+00:00)
To: Simon
Hello Simon,
if you change this line
https://github.com/inverse-inc/packetfence/blob/devel/conf/template_switches.conf.defaults#L94
from
acceptRole=Filter-Id = $role
to
acceptRole=Filter-Id = ${role}.in
and do a /usr/local/pf/bin/pfcmd configreload hard
does it work ?
Regards
Fabrice
Le
Hello Simon,
what switch module are you using in PacketFence ?
It´s implemented here:
https://github.com/inverse-inc/packetfence/blob/devel/lib/pf/Switch/Cisco/Catalyst_2960.pm#L580
Regards
Fabrice
Le ven. 21 janv. 2022 à 02:43, Simon Sutcliffe
a écrit :
> Dear Team
>
>
>
> Over the last
Dear Team
Over the last few weeks we have been engaged with trying to understand a
problem we were facing. The problem was with sending a Filter-ID
[Graphical user interface, text, application, chat or text message Description
automatically generated]
On the switch we had created a
