Hello,
I am trying to get MAC auth working on packetfence-8.3.0-1.el7.noarch to
replicate a legacy system we currently have going. (We may use more
advanced features later.)
I have exported some systems from the old system via MySQL CSV and
imported them into PF; they show up as registered in the
On Tue, May 7, 2019 08:03, Ludovic Zammit via PacketFence-users wrote:
> Hello,
>
> What’s the switch type that you used for 10.0.0.22? Is it in production
> mode? It says that it failed authentication in Mac authentication. Check
> in the Packetfence.log the answer must be there. Your MAC address
On Tue, May 7, 2019 07:45, Nicolas Quiniou-Briand wrote:
> Hello David,
>
> In order to test MAC Auth, you need to specify additional attributes.
>
> What you can do:
>
> 1. Create a mac-authentication.test file:
> ```
> User-Name = "00:11:22:33:44:55"
> User-Password = "00:11:22:33:44:55"
> NAS-IP
Hello,
Is there support in packetfence-8.3.0-1.el7.noarch to return Egress-VLANID
attributes in RADIUS Access-Accept responses? (In addition to RFC3576/3580
Tunnel-* stuff.)
There seems to be some code in
pf/lib/pf/Switch.pm:enablePortConfigAsTrunk() and
pf/lib/pf/floatingdevice.pm:enablePortConf
On Tue, May 7, 2019 22:29, Durand fabrice via PacketFence-users wrote:
> Hello David,
>
> for that you can use the radius filter to add on the fly the additional
> attribute.
>
> [mac]
> filter = mac
> operator = is
> value = 00:11:22:33:44:55
>
> [1:mac]
> scope = returnRadiusAccessAccept
> merge_
On Wed, May 8, 2019 18:37, Durand fabrice wrote:
> Hello David,
>
> can you try that:
>
> [mymachine1]
> filter = mac
> operator = is
> value = 07:3d:95:14:aa:ee
>
> [mac:mymachine1]
> scope = returnRadiusAccessAccept
> merge_answer = yes
> answer1 = Egress-V
Hello,
This is for packetfence-9.0.1-1.el7.noarch.
We have the following lines in "var/conf/mariadb.conf" (amongst others):
bind-address=192.168.0.37
wsrep_cluster_name=pfcluster
wsrep_cluster_address="gcomm://192.168.0.28,192.168.0.37"
wsrep_node_name=net-pf1
One risk with this is that you do not see security updates from EPEL for
packages already installed.
Another option is to use the “exclude” keyword in the .repo configuration file
to blacklist things:
> [epel]
> name=Extra Packages for Enterprise Linux 7 - $basearch
> metalink=https://mirrors.f
Hello,
Currently the official repos only have binaries for Debian 9 (stretch) which is
getting kind of old (security updates will stop June 2022):
https://www.packetfence.org/doc/PacketFence_Installation_Guide.html#_debian_based_systems
Given that Debian 11 (bullseye) will be released
