xheralt wrote:My www access is sporadic and depends on public wifi, which is why it's taken me this long to respond.
There was another go-round before that; the thread was either locked or deleted.
Ah, thanks. Yeah, that must be it, one Mod used to delete "go-round" type threads here. He's no longer forum staff and we don't delete such threads anymore.
xheralt wrote:So you've saved me from having to ask "what next"?
I just remembered, I might be able to save you something else too. I actually happen to have an exception in my own SYSTEM ruleset for the same type of access point as you encountered in the other thread. Maybe having that in full could help in this case.
Here is my entire SYSTEM ruleset (WiFi access point name obscured) -
Code: Select all
# ******* WiFi haxx
Site .nnu.com
Accept
# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny
How did I figure out what to put in? Well, all public WiFi access point exceptions work the same way:
1) Check the Browser Console (Ctrl-Shift-J) for message like this -
https://noscript.net/abe/users.html
2) Plug in the blocked sites (site1.com site2.com site3.com)
at the very top of the SYSTEM ruleset, in this form
Code: Select all
Site .site1.com .site2.com .site3.com
Accept
Or if IP addresses, skip the leading dot:
3) You're done. Enjoy the Internet.
Still seem "guru-y" to you? Let's de-mystify it then.
So, you're looking at the console message. See where it says MATCHING_SITE and ORIGIN1[, ORIGIN2, ...], ORIGINAL_ORIGIN in Giorgio's example? Those will be the sites that you pull out of the console message for the exception. If you see any of those beginning with
chrome:, ignore that one, it will be automatically taken care of.
Then, the next trick is to make sure to
combine *all* matching domains on the *same* Site line. For my access point, it was a couple different subdomains of nnu.com, which made that easy (note the leading dot in the ruleset). In your case here, perhaps just
10.0.0.1? Each different site is separated by a single whitespace.
Finally, as said, these public Wi-Fi access point exceptions are always the same template as how I did it above. So just plug in your site(s) and you should be good. If that doesn't cut it, try again because you may have another site to add to your Site line. Once it works, you're done.
There, that cuts through all the guru-y stuff a bit, doesn't it? Now just plug in your sites and enjoy your WiFi.
Does that help?
[quote="xheralt"]My www access is sporadic and depends on public wifi, which is why it's taken me this long to respond.
There was another go-round before that; the thread was [s][color=#888]either locked or[/color][/s] deleted. [/quote]
Ah, thanks. Yeah, that must be it, one Mod used to delete "go-round" type threads here. He's no longer forum staff and we don't delete such threads anymore.
[quote="xheralt"]So you've saved me from having to ask "what next"? :)[/quote]
I just remembered, I might be able to save you something else too. I actually happen to have an exception in my own SYSTEM ruleset for the same type of access point as you encountered in the other thread. Maybe having that in full could help in this case.
Here is my entire SYSTEM ruleset (WiFi access point name obscured) -
[code]# ******* WiFi haxx
Site .nnu.com
Accept
# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny[/code]
How did I figure out what to put in? Well, all public WiFi access point exceptions work the same way:
1) Check the Browser Console (Ctrl-Shift-J) for message like this - [url]https://noscript.net/abe/users.html[/url]
2) Plug in the blocked sites (site1.com site2.com site3.com) [b]at the very top[/b] of the SYSTEM ruleset, in this form
[code]Site .site1.com .site2.com .site3.com
Accept[/code]
Or if IP addresses, skip the leading dot:
[code]Site 10.0.0.1 1.1.1.1
Accept[/code]
3) You're done. Enjoy the Internet.
Still seem "guru-y" to you? Let's de-mystify it then.
So, you're looking at the console message. See where it says MATCHING_SITE and ORIGIN1[, ORIGIN2, ...], ORIGINAL_ORIGIN in Giorgio's example? Those will be the sites that you pull out of the console message for the exception. If you see any of those beginning with [u]chrome:[/u], ignore that one, it will be automatically taken care of.
Then, the next trick is to make sure to [b]combine *all* matching domains on the *same* Site line[/b]. For my access point, it was a couple different subdomains of nnu.com, which made that easy (note the leading dot in the ruleset). In your case here, perhaps just [u]10.0.0.1[/u]? Each different site is separated by a single whitespace.
Finally, as said, these public Wi-Fi access point exceptions are always the same template as how I did it above. So just plug in your site(s) and you should be good. If that doesn't cut it, try again because you may have another site to add to your Site line. Once it works, you're done.
There, that cuts through all the guru-y stuff a bit, doesn't it? Now just plug in your sites and enjoy your WiFi. :)
Does that help?