Captive Portal / MAC Passthrough
-
Thank you,
I just wait ;-)
-
Has this bug been fixed yet? I just updated to 2.4 last night and having this same issue.
-
Sorry, I just saw your message.
I dont think it had been fixed. But I also did not see something like that in the list of issues.
For me it is still not working -
Same here totally dead and a BIG security issue/inconvenience for me.
-
You think so?ย I am impressed how good it is all ready.
Besides Captive Portal it works well for me. And my son loves the fact Captive Portal is disabled on my Pfsense -
My kids are loving also 2.4 โฆ no mac on captiveportal ;-)
Does someone knows when we can expect a working mac authentication?
-
It doesn't appear to be on the bug list either. Hopefully this is fixed soon. Its a real nightmare!
-
I was quite surprised to see a public release today with a bug this big still present. I'd be more ok with it if it were a package add on but a core feature with a major regression?
-
This is only a problem on 2.4, where captive portal is not yet fully implemented.
The release today was 2.3.4. Not 2.4. No such issue in 2.3.x.
-
My bad I read it wrong. Looking at the bug list though I don't see were this issue is even listed.
-
It is all a part of the captive portal reimplementation, which is this ticket:
https://redmine.pfsense.org/issues/6606 -
I notice this ticket has been idle for quite awhile. Is it being worked on? Will this be resolved before the official release? Is there a rough ETA on release or fix or is it still aways off?
-
Yes, it is being worked on. It will be fixed before release.
-
So, captive-portal and freeradius with IETF format of mac-addresses authentication has worked since update from yesterday.
Yesterdays / Todays update has updated freeradius to a newer version now it does not work anymore. We had to disable captiveportal to get internet-connection!Is this a known bug? Before we had version from 2. may and everything was ok.
-
Any updates on this? Last July ticket set to high priority. Still broke.
https://redmine.pfsense.org/issues/6606