Firefox needs to allow access to port 10080 in special cases
Firefox currently blocks port 10080 to protect against a presumed security threat. Linksys routers use port 10080 to allow users to log in to the guest network so Firefox has rendered Guest Network logins to be unaccessable forcing router owner to allow "guests" to log in to the the primary lan and potentially cause issues with the very network they are trying to protect from outside issues. Firefox needs to provide a way for guests to log into the guest network within their software... particularly in the ios and android versions of the Firefox apps. Please provide a reasonable workaround so that I don't put my network at risk by allowing guests to log in to my primary network.
First, could you ask Linksys whether they've got a secret workaround? Seems they like to deal with people individually on this rather than putting out firmware updates:
Both Firefox and Chrome block this port by default. On desktop OS'es they offer an obscure setting to allow the user to enable access to the port. But on mobile... less flexibility.
Mozilla recently started up a new "Ideas" site at https://connect.mozilla.org/ for proposed product changes. I think if you have time, it would be a good idea to post there to get into the current feedback stream.
Thanks for the suggestions.. I already knew that many other router admins were having this issue and that Linksys was failing to provide a fix. I did post the issue on the "connect" website but I don't know if the Mozilla devs will take any notice.
I think that since Mozilla and Google created this problem (even though with the best intentions) it is incumbent on them to provide a reasonable work around so that the port can be accessed when not using the app that they are trying to protect against.
Guest networks are essential for protecting the LANs of home and business network operators. Mozilla: PLEASE FIX THIS ASAP!!
When you say "guest network", is that a second SSID configured with internet access but no LAN access? We all use those at businesses, so I guess either they dedicate a different router to it, or they use a router with more configuration options so they don't need a special port.
I suppose it might be possible to use a second router, but in this case it is not practical. The whole purpose of being able to set up a guest network on a router is to prevent access to the primary LAN while allowing guest internet access. Linksys has chosen to dedicate (hard code) port 10080 as the login access to the guest network so a solution from Mozilla is needed.
Thank you but your suggestion is not practical.
The whole reason that Mozilla and Google have banned port 10080 is because users of the Linux based Amanda backup software (for servers) uses that port and malicious hackers can use that access to install malware and perform other actions that would compromise a server. However, Amanda is not available for either Android or iOS phones and tablets. So it seems to me that Mozilla could allow those devices to use port 10080 without any risk to a network. After all, most of the time guest networks are for visiting friends or relatives to use to access the internet and they don't normally bring a computer with the Amanda backup software.. They are usually using a phone or tablet. So, Mozilla, can you cut us a little slack here and allow phones and tablets to access port 10080 (maybe with a simple override).
Guest login doesn't have access to the other parts of the router. I have NightHawk and you can isolate the Guest login. Is there a feature for linksys that you can't access this on? And mine is a 2017 Router so not sure why your linksys doesn't off this feature.
Dropa, you obviously don't understand the issue.. Linksys routers offer a guest network but they have hard coded the login page for it to the 10080 port that Mozilla has banned due to the Amanda issue mentioned earlier. The browser makers have to make an allowance to let users have access to the guest network login page or they cannot login at all !!
For other potential responders: please don't try to offer suggestions if you don't fully read the full content of this queue. It only confuses and clutters the issue. Thank you.
The reason I mentioned the Connect site is that this is more like an emergency room and suggestions don't get into the product design flow. Since you have a specific argument for mobile platforms, maybe add that to the exception UI bug: