Apple laptops stuck at login / registration process HSNM Front-end Welcome Portal general discussion about HTML, CSS, layout, custom apps, templates

[Gerard]

Any news?
Some clients (MWC Hotels in Barcelona) are getting anxious.

Thanks.

[HSNMSupport]

Hi,
in the last days we performed many other tests and we are sure to have discovered what the problem is: it's related to Apple devices' DNS (probably not on all iOS/MacOS version).

When the Apple device connects to a wifi network it checks, trying to reach a specific control's URL, if it has an internet access; if the Apple device can't reach this URL it pops up the CNA (Captive Network Assistant) and, unfortunately, also the DNS client stops working.
Then, if in the Mikrotik gateway is set a "DNS Name" under Hotspot configuration (generally set if you are using HTTPS on Welcome Portal),

MikrotikHotspotDNSName.jpg

having DNS not running on the Apple device, on HSNM version prior to 5.0.167 a blinking green circle is displayed without any message

BlinkingGreenCircle.jpg

instead on HSNM version later than 5.0.167, after 30 seconds, an error saying "Error. The login procedure can not contact the gateway" occurs.

Error.jpg

To solve this issue you can:
1) Not set a "DNS Name" (mandatory if you are using HTTPS on Welcome Portal) under Hotspot configuration on the Mikrotik Gateway;
2) Disable the Apple CNA on the gateway configuration inside HSNM

DisableAppleCNA.jpg

With the CNA disabled, the APPLE device is able to reach the control's URL so it thinks to have an internet access and so it doesn't stop the DNS client working.

Hope this help

Best regards

[HSNMSupport]

Hi Guys
I am glad to inform you that we have just release a new HSNM version (5.0.171) that adds a workaround for the macOS and iOS issue mentioned above.
With this version it is not necessary to disable Apple CNA or DNS Name inside the Mikrotik Gateway in order to fix the  problem during the login phase on some iOS and macOS Apple devices.

I hope you appreciate

Regards

[Gerard]

Yes! It's working now! Thank you

[Andrushka]

Does this workaround involve only a back end change or does it also require changes to the Mikrotik gateway configuration?

[HSNMSupport]

Hi,

you don't have to do anything at Mikrotik side.

Best Regards.

[Gerard]

Hi,
This issue reappeared with 5.0.182
It only happens when a DNS Name is set in the hotspot profile (Mikrotik)

[HSNMSupport1]

Hi Gerard,

We will have our development team investigate it and we will get back to you as soon as possible.

Best Regards,