Hello Michael,
good to know that it works.
Le 20-07-08 à 15 h 54, Michael Brown a écrit :
Hi Fabrice,
You were right. As soon as I changed the Auth Source for Domain
Computers to MemberOf is CN=Domain Computers,OU=Domain
Groups,DC=eatontown,DC=local it worked the only caveat being that on
from Gui:
Configuration / Network Configuration/interface
in my case ..ETH0 is "external" and ETH1 is Inline (internal with dhcp
server)
in Eth0 i have Type (Management)
and "Additional listening daemon" and can choice : Dhcp, dns, portal,
radius etc ect..select Portal
Il 13/07/2020
One solution is: create a connection profile built for 802.1x and in its
options enable the pre-registration portal
if you are still in the planning stage and want a comparison you can call me
(mobile). My numbers are signed
bye
Giacinto Caretto
ENEA - italy
You must enable the sponsor daemon on the interface where come from the
sponsor.
Check with netstat if in the interface is listen the port 443 probabily not.
After u enable the sponsor must restart haproxy portal iotable and mybe other
service..or reboot the pf
Bye bye
--
GC Net domenica,
I don't see the sponsor daemon as an option under interfaces?
On Monday, July 13, 2020, 03:06:20 AM EDT, i...@gcnet.it
wrote:
You must enable the sponsor daemon on the interface where come from the
sponsor.
Check with netstat if in the interface is listen the port 443 probabily
