Re: [PacketFence-users] Newer Model iPhones and Android Devices showing MAC:0 in Captive Portal

2023-01-17 Thread Ian MacDonald via PacketFence-users
Okay, So we have been doing some testing on a pristine 12.1, and the behaviour is the same. It seems that a couple of things are occurring with at least one problem client, an iPhone 12 Pro. Maybe we broke our config somewhere along the way with updates/upgrades and did not realize it, or

Re: [PacketFence-users] Newer Model iPhones and Android Devices showing MAC:0 in Captive Portal

2023-01-11 Thread Diego Garcia del Rio via PacketFence-users
im Guessing it might be related to the rfc7710bis / rfc8910 portal support this means that via dhcp, the client is provided with an URL they can use to check the status of the device in the portal (whether they are still jailed or no) normally this information is served on the same interface as

Re: [PacketFence-users] Newer Model iPhones and Android Devices showing MAC:0 in Captive Portal

2023-01-11 Thread Daniel Silva via PacketFence-users
Good afternoon, We are having the same problem, in the new version people have captured random macs, and they redirect to a page with information on how to disable random macs. Would that really be the best way to solve it? I don't know, I just know that it generates complaints, tickets in our

Re: [PacketFence-users] Newer Model iPhones and Android Devices showing MAC:0 in Captive Portal

2023-01-11 Thread Ian MacDonald via PacketFence-users
Daniel, The random MAC would seem like an obvious culprit, but it is not. On an iPhone, if you click on the little "i" for information next to each connection, you see that the OS uses the same [random] mac per SSID, so it will never change for a given WiFi network after is has connected. It

[PacketFence-users] Newer Model iPhones and Android Devices showing MAC:0 in Captive Portal

2023-01-11 Thread Ian MacDonald via PacketFence-users
Hi Packetfence, We have been struggling with some newer model mobile devices with our WiFi captive portal implementation using Packetfence, and have not seen any change in the behavior on 11.0 thru 12.1 with our current connection profile. We do not use an inline configuration, and now we are