www.satelliteguys.us
Firefox, Google Chrome, Microsoft EDGE (original non-chromium cannot), Brave can all do it. Not sure about Safari though.
Yours is a different issue and basically blocking from the client side I guess more due to the the guest access configuration in the router but the question is do they even have access to the non-guest side of the router where they have full access or better yet, do they even have access to configure the router as it might be they have parental control turned on for the guest side or for all connections? Interesting the blocking was only on iOS devices or maybe their access list is configured to block things only from certain devices based on the MAC address and not really iOS.
As the response was to be an FYI. It was a Linksys firmware issue and non-reversible. Assigning a DMZ to an IP of a Windows, Android device whether wifi or LAN resulted in no issues. The same as when connected through the guest net. In any config., and Apple device would connect to the net. But no Internet access was avaliable. With the same message that the OP displayed above.A glitch that was cured in the next fw release. A glitch from an automatic firmware update. And was an FYI. I understand the issue here. I've read other instances from different members. Perhaps it was a hint to try connecting to the cellular network to check if the issue remained. Or a VPN if you have one. Perhaps the TOR network. Or maybe even Fireproxy. But thank you for your detailed...info.
That's interesting since it wasn't picky on Windows, Android which is basically Linux. iOS which is really OSX has the actual Berkeley BSD4.4lite original TCP/IP stack as the kernel is Mach, everything else is FreeBSD based which is the standard TCP/IP stack which would have been the one that would have worked as every OS out there uses a implementation of TCP/IP which is based on BSD. Yes, your issue is basically on the LAN side where the Linksys router was the issue while the issue we are talking about is using a browser on this site only and once the cookies are cleared, access is restored which would not make sense if it was the site's firewall blocking a client's IP. Is the issue the same as the one mentioned below since this is OpenWRT being third party which is not the same as the official stock firmware from Linksys:
forum.openwrt.org
Well. A site issue can hopefully be fixed. Time is money and yeah, the first idea was to just install dd-wrt, openwrt, tomato flavors. Funky processor and no support for the thing. So I gave them an AP in the form of an old router to use until we came up with a solution. Besides paying the bill I got a fish dinner and a mess of beers and the router stayed until finding a new fw release for theirs that fixed the issue. There was no shell access on it, of couse.That's interesting since it wasn't picky on Windows, Android which is basically Linux. iOS which is really OSX has the actual Berkeley BSD4.4lite original TCP/IP stack as the kernel is Mach, everything else is FreeBSD based which is the standard TCP/IP stack which would have been the one that would have worked as every OS out there uses a implementation of TCP/IP which is based on BSD. Yes, your issue is basically on the LAN side where the Linksys router was the issue while the issue we are talking about is using a browser on this site only and once the cookies are cleared, access is restored which would not make sense if it was the site's firewall blocking a client's IP. Is the issue the same as the one mentioned below since this is OpenWRT being third party which is not the same as the official stock firmware from Linksys:
iOS (iPhone or iPad) not getting internet when connected to WiFi (openwrt vpn router) but android devices are fine
This indicates that your DNS is probably not working as expected in your configuration. So... looking at DNS specifically -- what are the DNS entries that you've defined in your wan interface? It appears that they're for NordVPN, is that correct? These shouldn't be in your wan, and that could...
Well, Arlo, consider the fact that you are dealing with an astrophysicist with a PhD. It's his nature. Go with it, or not...
Lol. Reminds me of National Lampoon's Vacation.
Yeah, you never mentioned what Linksys model router it was. But with dd-wrt, openwrt, tomato, it will actually be slower because all of those do not contain the Broadcom Driver which is paid and license so the hardware acceleration will not be enabled. So a 300Mbps normal speed will be at 190Mbps or so without the hardware acceleration. I thought they somehow they were actually still using their own router afterwards. I guess depending on what model it is, there is actually a better firmware than even Linksys's stock firmware which has the Broadcom Driver in it, that's a ported version of R-Merlin's ASUS software but you need to have specific models of the LinkSys router(s) for that to work from either XWRT-Vortex available at Home | Xwrt-Vortex which is more limited and only supports the EA6900 or Koolshare which supports over 80 models of Netgear and Linksys routers. Koolshare is available at Merlin-Koolshare Routers - WannaFlix but only supports Linksys router models EA6200, EA6400, EA6500v2, EA6700, EA6900. I usually mess with different software parts only and will go third party as needed since the only reason one needs to even dissect it
www.linksys.com
Depends on the product in question. Not for a router as these are not even real routers and nothing more than something more than a Network Address Translation (NAT) device and routes a real IP on the WAN side to private IPs for multiple devices. If it was limited, there is nothing much you can do except use third party software like XWRT-Vortex on the Netgear R7000 which basically puts it on RMerlin-ASUS firmware that many have done to get better performance and also customization of the features including rooted shell access by ssh. Other than that, you really won't get much with dissecting a router anyways unless you had a bad flash as all you can really use it for is connecting a serial cable to a few pins of the router to reflash it from the computer which others have done with different routers. Other than that, there are others who do a more customized solution and just run pfsense on a PC using ethernet cards to take in the connection and then use things like Ubiquiti for the access points instead which will work better and have better range than the consumer routers. For things like that, dslreports.com is a better resource.
Interesting since I thought all Linksys routers in the last 16 years were Broadcom based, I knew some were Marvell but never really paid attention to the Marvell models. I prefer Qualcomm Atheros over Broadcom. I know others have the Netgear R7000 with XWRT-Vortex and it did AiMesh fine with the RT-68, other ASUS models and even another Netgear R7000 running XWRT-Vortex which is covered in the thread here as I also use a R7000 with XWRT-Vortex:
