How do I do that? I'm especially interested in how I configure it to use a TCP reset. In firewall rules use action "reject" instead of "drop". "Drop" means silently discard the packet without sending any notice to the requests origin. "Reject" means actively ...

My advice: just block https for unauthenticated users. Use tcp reset so users will get a fast response from browsers. Then users will try another (http) site and see your hotspot pages. How do I do that? I'm especially interested in how I configure it to use a TCP reset. Has anyone looked at the HT...

I realize that The Dude abides, but does it also allow me to manage the entries in the walled garden? I have bunch of Mikrotiks running hotspots (captive portals) and I'd like to update/manage the walled garden entries, hopefully for multiple devices at the same time. Does The Dude help me to do that?

I can't seem to find the 404 errors in the logs. I can easily cause a 404 error by trying to browse to a hotspot page that doesn't exist, but I haven't been able to find it reported in the logs. Which topic is it reported under?

Yes, I know that a 404 is page not found. The mystery is that the page is there, and is found most of the time. The 404 response must be sent from the Mikrotik, so the Mikrotik sometimes either cannot find the file in the hotspot folder, or is sending a 404 for some other error (which would be incor...

Most of the time our login page works fine, but occasionally we get a 404 when the user tries to load the login page. This happens even when the router is barely loaded, like 1% of CPU. I don't know how often it happens, but it happens often enough that I see it while testing. After a few page refre...

We occasionally get the error "already authorizing, retry later", but it's not clear how that client would already be authorizing. The docs say: Solution: wait for the current request to be completed, and then try again I'd be happy to do that, but how do I detect when the current request ...