Hotspot Bug - some clients fail to get to the login page
Posted: Mon Oct 20, 2008 4:04 am
Hi All,
I've come across what I'm pretty sure is a bug in the mikrotik hotspot.
I'm running RouterOS 3.15 (tried 3.14 - same issue).
My laptop is running ubuntu linux and is unable to get to the login page for the hotspot, for example if I connect to the hotspot network, and then try to go to google, the redirect to the hotspot url works, but the connection is reset when my browser tries to get to the login page.
I've tracked down the issue to the fact that the mikrotik hotspot daemon (running on port 64873) sends an ack directly to my computer, rather than the packet being rewritten to make it come from port 80. See the wireshark packet capture below. This causes my computer to reset the connection, and the login page doesn't load.
One workaround (which allows me to access the hotspot ) is to block incoming traffic to my laptop from port 64873/TCP, but that is obviously far from an optimal solution.
Windows XP clients seem to work fine, I guess they ignore the packets from the wrong source-port. I haven't tested with any other operating systems.
Has anyone else come across this strange behaviour?
Cheers,
Jonesy
I've come across what I'm pretty sure is a bug in the mikrotik hotspot.
I'm running RouterOS 3.15 (tried 3.14 - same issue).
My laptop is running ubuntu linux and is unable to get to the login page for the hotspot, for example if I connect to the hotspot network, and then try to go to google, the redirect to the hotspot url works, but the connection is reset when my browser tries to get to the login page.
I've tracked down the issue to the fact that the mikrotik hotspot daemon (running on port 64873) sends an ack directly to my computer, rather than the packet being rewritten to make it come from port 80. See the wireshark packet capture below. This causes my computer to reset the connection, and the login page doesn't load.
One workaround (which allows me to access the hotspot ) is to block incoming traffic to my laptop from port 64873/TCP, but that is obviously far from an optimal solution.
Windows XP clients seem to work fine, I guess they ignore the packets from the wrong source-port. I haven't tested with any other operating systems.
Has anyone else come across this strange behaviour?
Cheers,
Jonesy