This is after I just reset the device a couple of days back.. it appears to loose the IP address for it’s dns name and then users start calling up saying they don’t get to the login page (and if checked they can’t resolve the dns name)
Does this sound like something wrong with my setup or is this an actual bug?
I have the supout.rif if mt fellows are interested in seeing it.
Note that we use an SSL cert generated for hotspots.ourdomain.com which is put on all MT’s using the hotspot system, so if we turn this off I either have to disable SSL or people will get the cert error coming up all the time.
I find I can do the following and it appears to reset them:
Get the user to find out their IP address, find it on the hotspot “host” list.
Get them to do a repair on their connection just as you delete this entry (or get them to unplug the lan cable, delete the entry then they plug back in)
They then show back up with a D (Dynamic) next to the host, which changes to a H when they try to access another page and are redirected to the login page.
I’ve just had a similar problem with 2.9.48. I used to have 2.9.46 and i’m not sure whether it happened then.
Bypassed hosts got dns working correct, but hotspot users couldn’t login (with dns errors).
I did some sniffing and got mikrotik sending ICMP port 53 unreachable to hosts!!
Also found a dynamic rule redirecting port 53 of unauthenticated users to 64872. Mt did not respond DNS queries on that port.
Rebooting mt was the solution (it had 11 days uptime). Before I tried disabling/enabling “dns requests”, and removing upnp dynamic rules, but didn’t work.
After that it responded on port 53 and 64872 correctly.
I use the “hotspot address” option but not the “dns name” option. It also shows that “ip of dns name” is 0.0.0.0 but it works.
