@danicavini
Thanks, i will try it !

@undrblack

Without knowing the details :
When you remove the 'virtual' part, that is : running pfSense with 3 real networking interfaces, bare bone, your issue will be gone. I can imagine the vitual interfaces / switch can be set up many ways, some of them could be wrong ?
See also Virtualization ! if you have a Windows 10 (Pro) orMS SErver : use the build in Hyper-V : I've one running iwth Hyper-V, and it works fine. There is a detailed step by step setup guide in the doc.
When a client connects to the Wifi, can you see the DHCP server log 'lease' attribution on the right interface ? What was the IP/mask/gateway/DNS received on the client ? That info should correspond to with the pfSense portal NIC.
pfSEnse doesn't handle the the AP <=> Client radio (wifi) connection.
if the AP is an AP and router, the pfSense portal only sees the IP and MAC of the router, not the IP and MAC of the clients. Ones a first client is logged in, all the others will pass without seeing a login screen.

@mbunal merhaba AP'lerde ağ için parola tanımlaması yaparsanız ağa bağlanmak isteyen her cihaz için önce wifi parolası girilmesi istenir sonrasında captive portal ekranına girerek oturum açmaları istenir. eğer ağlara bağlanan cihazlar aynı ise captive portal üzerinden mac adreslerine tek tek izin verebilirsiniz.

Vielen Dank @JeGr @mike69 . Wieder einiges dazu gelernt.. :)

@budweiser

Check here Home > pfSense® Software > Captive Portal and read some questions.
You'll notice that they are all written in a language you don't seem to use ... ;)

@viktor_g I will update it as soon as possible.

Install the Patch package.
Read the Patch package manual (Netgate's pfSense doc).

Or : as you already found out, it concerns only the edit of a file, a couple of lines.
A good text editor like Ultraedit or Notepad++ and a tool like SmartFTP or FileZilla (both can handle SFTP access) and your do it as is done old fashioned way - ans still today : with your fingers. Btw : and keyboard.

@wickeren said in Freeradius with LDAP backend and 802.1x:

Have set Active Directory Compatibility in the Freeradius LDAP settings and played around with the EAP settings. For now the default is PEAP, in the EAP-PEAP section the default is MSCHAPv2 and Copy Request to Tunnel is set to Yes. According to some info I have found this should be OK, but in my case it isn’t however. Still think it must be something there, but can’t figure it out yet.

Hi , I tried to configure free-radius on Pfsense (authentication via ldap or Kerberos) , i have AD 2008 .
can you share your configuration please