ABE blocks too frequently and absurdly

[luweitest]

It has been for sometime that ABE blocks too much and very annoying, esp. when click the search result of google, e.g. search "noscript" then click the first result, the page is blocked. Check the error console gives

[ABE] <LOCAL> Deny on {GET http://noscript.net/ <<< http://www.google.com/search?q=noscript - 6}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny

It is driving me crazy. The strange thing is if I visit all pages through a proxy, all is fine. But I don't want to do all things through proxy.

[luweitest]

Seems the forum do not provide email notification. I may not come back to check replies now an then, so please send hints to luweitest at gmail.com, thank you.

[therube]

What do your USER rules show?

[Thrawn]

Something is wrong with your network setup. ABE thinks that noscript.net is a local address, which isn't normal. Can you open a command prompt and run 'ping noscript.net', then tell us what numbered address it resolves to? For me, it is 82.103.134.102.

@therube: No need, that error message shows that it is the SYSTEM rule that is firing.

[GµårÐïåñ]

Seems the forum do not provide email notification. I may not come back to check replies now an then, so please send hints to luweitest at gmail.com, thank you.

Forum gives email notifications when you are registered. When you post anonymously, how is it supposed to notify you? You will just have to check back on your own or if you can't, then probably don't post and leave.

[GµårÐïåñ]

Something is wrong with your network setup. ABE thinks that noscript.net is a local address, which isn't normal. Can you open a command prompt and run 'ping noscript.net', then tell us what numbered address it resolves to? For me, it is 82.103.134.102.

@therube: No need, that error message shows that it is the SYSTEM rule that is firing.

Agreed, this shows something fundamentally wrong with your network configuration and ABE is rightfully protecting you against local access. If you don't want that protection, then just delete the rule and hope for the best.

Also, agreed - therube, the rule is being fired by SYSTEM, it has nothing to do with USER rules and is irrelevant to this error or issues. Something in the OP's system is causing the traffic to be considered LOCAL which suggests either bad NAT configuration or the user is using their WAN IP as their local IP which means they are directly connected which can also cause this problem.