@Gertjan Your solution involving the modification of the captiveportal_blocked_mac function in the /etc/inc/captiveportal.inc file has been tested successfully. Following your guidance, I implemented the updated function you provided. The modifications have brought about the desired outcome, enabling us to effectively block MAC addresses using mask values. Your willingness to share your knowledge and solution has not only resolved the technical challenge but has also showcased the strength and support of the community. I appreciate your dedication and time spent on investigating and addressing this issue. Thanks again.

Please check here for a tutorial installing Freeradius with a modern Web GUI: https://administrator.de/tutorial/freeradius-management-mit-webgui-6972997853.html

@viktor_g Why you are talking about custom error page while the CORS issue with PORTAL_ACTION URL?

@hsrtreml Google gave me a good tip. I asked : Mac Pro OS 12.6.8 captive portal connect and found a probable issue. The thing is : you've probably used this device already to the SSID and router/firewall pfSense when there was no captive portal activated. So your MAC is not going tot auto prrtal detects, as it knows that that isn't the case - but now it is. Solution : delete the SSID profile in your MAC, and connect again. This time, the captive portal detection will work (because it's, after all, a new 'unknown' network).

@Gertjan hello, thank you for your suggesion i will try to scan the disk

@prochid thank you

@Gertjan Thanks to reply..

@mindf No DHCP .... No MAC filtering / let's hope the client can still do some DNS against 10.1.1.1, as that would give you (might give you) the "auto portal login page". I guess that's not possible as your devices use static IP settings. For me, the captive portal is a LAN NIC thing. Wireguard, is a WAN thing. I've been using an OpenVPN client for a while, and my setup was : LAN devices are all using the WAN, this was the pretty straight classic setup. And all Captive portal users on NIC LAN2 (another LAN) are routed out over the OPENVPN client (so tunneled over my WAN) and ended up somewhere in {whatever I had chosen as an end point}. I presume that 'OpenVPN' or 'Wireguard' is just a choice, both should work. When you say @mindf said in [Captive Portal] No internet access after successful authentication: I have configured Wireguard with captive portal what do have to imagine ? What I've said above ? Different ? Btw : cpzoneid_2_auth/10.1.1.2_32 rules/nat contents: ether pass in quick proto 0x0800 l3 from 10.1.1.2 to any tag cpzoneid_2_auth dnpipe 2000 ether pass out quick proto 0x0800 l3 from any to 10.1.1.2 tag cpzoneid_2_auth dnpipe 2001 that looks fine. It's a authenticated portal user. The next hurdle would by : the rules you have on the GUI portal interface firewall list. If that one contains a pass (all), then your traffic enters the interface, is in the 'system' and ready to be routed (out == leaving some other interface).

@bendida I have the same problem after upgrading to pfSense 2.7

@guntery said in CP using IP address for radius session not username: nothing to do with radius or auth. I agree. @guntery said in CP using IP address for radius session not username: it disregards mac and username It looks like that portal_allow() returns with the $sessonid. Portal firewall rules are not modified, so, while the IP is the same, the MAC will be different. No login page is presented, and no "Internet access" : that's your issue ? That is, I could not create a situation with my setup where another device (another MAC) was using an IP that had already a session. Typically, for my usage, Idle timeout (Minutes) is set to 360 and Hard timeout (Minutes) is set to 720 or 12 hours. The latter will remove sessions. My DHCP leases on my captive portal are set to 86400 sec or 24 hours. @serginho said in CP using IP address for radius session not username: for the developer to recognize and correct this error Feel free to enumerate. And as you walked through the code, you should be able to add lots of details.

@Chooks said in Captive Portal not redirected after successful login: I'm using the latest version. 23.05.1 ? This : [image: 1688710246161-3c06064e-e679-421e-b8ef-8ae0286e7c88-image.png] looks like the OS - or program - knows or suspects that the device hasn't a direct Internet connection. It's part of the portal detection. Normally, the GET (www.example.tld)/connecttest.txt should return a 'page' like this one that shows the word (for example) "Success.". If it doesn't, because another page came back : the pfsene captive portal login page, the OS should pop up a message, notification, or even a browser directly in front of the user. If it doesn't do that ... well ... After successful portal login : [image: 1688710845403-d7c6be7a-64af-4e2d-88fd-3c4917acbd46-image.png] 192.168.2.6 - - [07/Jul/2023:08:19:56 +0200] "POST /index.php?zone=cpzone1 HTTP/2.0" 302 0 "https://portal.brit-hotel-fumel.net:8003/index.php?zone=cpzone1&redirurl=http%3A%2F%2Fcaptive.apple.com%2Fhotspot-detect.html" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148" 302 = Redirect. You can also see the URL parameter "?zonecpzone1&redirurl=http%3A%2F%2Fcaptive.apple.com%2Fhotspot-detect.html" see the "http://captive.apple.com/hotspot-detect.html" : [image: 1688717282186-b8693d06-cfb9-4078-b69a-94e313943dd0-image.png] Because I've set : [image: 1688713813218-9582e267-23f6-4b26-a378-ec51189fede9-image.png] I was take to https://www.google.com/ If my "After authentication Redirection URL" was empty, I would see the [image: 1688717455410-fd83eba8-4ed9-4cab-ab1f-c7778b48ea29-image.png] and that's a bit stupid. But correct my iPhone wanted to go to that page (that page because it uses it to detect the prence of a captive portal). When the captive portal authentification was done, it will show the page. My phone is now happy : the device has a working "Internet connection". Look at /usr/local/captiveportal/index.php - that is the page PHP that shows the login page. But it does more then that. See /etc/inc/captiveportal.inc tells the whole (rather complex) story.

@susobaco I answered you in your post. Please create a bug yourself - maybe you can better convey to the developers with your words that it is a regression of this current firmware. Then note the device key under "AutoConfigBackup" and reinstall to 2.6.0 and restore a config from 2.6.0 with the device key. Then we'll be right back. Let's hope that the developers will adjust the firmware and get the captive portal up and running again.

@dochy Ah. Your using an ancient version. [image: 1688382846934-5ae2a4b1-a046-4732-8a2e-edc2aded1058-image.png] That's ok of course, but I can't recall what I did 'yesterday'. And before yesterday, I was using 23.05, and before that 23.01 and before that ... 22.0x and before that 2.6.0. 2.7.0 isn't ok for you ? I suggest you use the use the "forum search", as I'm pretty sure some one has writing about mysql in the past. Double check the PHP version pfSense 2.6.0 uses.

@mhmd said in How can I allow the subdomains of one hostname in Captive Portal?: My exact problem is that the domain IP is different from the subdomains it has. And what is these 2 fqdn exactly? https://docs.netgate.com/pfsense/en/latest/captiveportal/allowed-hostnames.html#allowed-hostnames A daemon periodically resolves the hostnames to IP address(es) and allows them through the portal without authentication in this zone.

@LadiesMan217 https://docs.netgate.com/pfsense/en/latest/captiveportal/allowed-hostnames.html#allowed-hostnames

@Gertjan It is exactly like that When I first started CP, we had a virtual machine that everyone called Remote Desktop and used it for Internet-related matters, and when one of the users authenticated, the rest of the users also authenticated in CP without needing to authenticate. CP was passing and it was very funny.

Thank you very much for this detailed answer. I appreciated very much your explanation of the redirecting technique. @Gertjan said in Captive Portal redirect does not work for a few clients: First things first : you have this package installed, and activated the patches : [image: 1686729786540-05481e7a-0815-410a-93dd-d28cd13e58ed-image.png] Btw : you might want to use 2.7.0-beta, is close to release. This package indeed needs an update. Will do so this evening. We won't use a beta version in this production environment. But we have a Dev cluster and will check this on that. The solution is always the same : Delete the wifi profile on the phone - it doesn't contain any user settings as a password (portal networks don't use password - they use a TLS connection to authentify against the portal web server, and from then on all connection are TLS anyway[ok, except DNS]) - and re connect. It always works for me. Yes, this also worked for our test client! You mean pfSense can't see the MAC addresses of the connected captive portal users ? Exactly You didn't mention the most important criteria of a portal : DNS. A connecting device should obtain an IP, network, gateway and DNS. Then it throws out a hidden http request (see above) and for that to work, DNS should work. Not some "8.8.8.8" DNS, as all non local DNS are not accessible at this moment. By default, the DNS will work on the pfSense portal interface. Did you test that ? Yes, DNS works good on the inside interface of the pfsense, with host override for the portal page redirect. In the past, this page Troubleshooting Captive Portal was mandatory. It still is, but these days it talk about the new firewall 'pf', as Netgate made 'pf' MAC aware. 2.6.0. uses ipfw, which was ditched after 2.6.0. I am aware of this page, thank you. The problem is also with troubleshooting in the Prod environment. I cannot change some settings just to test if it works. There would be the risk to interrupt the connectivity of the 300-400 working clients. I have to do non-invasive things like packet capture and log examination. If this issue remains or even spreads to more clients or the "Wifi forget" on the phone won't help anymore we would need to reproduce the setting in a testing environment. Again thank you R.