Hello Eugene,
the probable issue is because the switch is not defined on the
packetfence side. (18:e8:29:93:52:a8)
But you can add a switch range on pf (like 192.168.0.0/24 as switch id,
set the controller ip and set the http credential to connect to the api)
and there is pfcron task who will try to find all the bssid of all the
AP and will do a map between the mac and the ip of the AP.
First use the latest version + the maintenance patch (pf-maint.pl) and
to force the task do:
./sbin/pfcron ubiquiti_ap_mac_to_ip
to see what you have in the cache:
./bin/pfcmd cache switch_distributed list
You should be able to see Ubiquiti-18:e8:29:93:52:a8 in the cache.
Then retry to hit the portal
Regards
Fabrice
Le 20-12-08 à 23 h 23, ypefti--- via PacketFence-users a écrit :
Guys,
I’m resurrecting the old topic that I’ve never brought to a conclusion
and implementation.
Asking for a second opinion of those who could do it and for Fabrice
and Ludovic expertise.
Please help me! I do believe Inverse team tested their product with
Unifi WiFi.
I redirect a guest portal from Unifi to PF by using their option
called “use external portal server”
The endpoint normally associates to a guest SSID and web page comes up
showing this error.
pf.options.bc.ca resolves normally to the IP address of PF that has
captive portal listens on that IP address.
What drives me mad and is unknown to me is how this URL is formed and
why this URL contains the directory of Unifi controller, i.e. q4b0wgkk.
Of course it doesn’t exist on PF and to me it is a reason I see “Not
implemented”.
What am I missing ? I can also attach captures done during this
connection attempt.
Eugene
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
