Hello David,
a radius request without Calling-Station-Id attribute mean for
packetfence that it's a cli access (ssh on the switch per example), so
the attribute is mandatory.
On the other side you can create a local account nagios with the correct
password and assign it an administration acc
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
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
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 is registered in
Packetfence ? With which role?
Thanks,
> On May 7, 2019,
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-Address = 192.168.0.1
NAS-Port = 0
NAS-Port-Type = Ethernet
Service-Type =
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
