ABE exception rule for accessing wireless extender

Ask for help about NoScript, no registration needed to post
User avatar
mikolajek
Posts: 18
Joined: Wed Mar 19, 2014 5:46 pm
Location: Warsaw, Poland
Contact:

ABE exception rule for accessing wireless extender

Post by mikolajek » Tue Aug 12, 2014 2:10 pm

I've just installed a wireless extender - D-Link DAP-1520. It uses the following page: http://dlinkap.local. for its admin panel.

The problem is that with ABE enabled after typing this address I'm just getting the message that it has been filtered by ABE and no access is granted. I have no problems with accessing the admin panel with ABE disabled.

Since ABE scripting is a black magic to me - can anyone provide me with some support on how to put a rule that would make an exception in this filter and allow accessing this local link?

Many thanks in advance!
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

User avatar
Giorgio Maone
Site Admin
Posts: 8742
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: ABE exception rule for accessing wireless extender

Post by Giorgio Maone » Tue Aug 12, 2014 9:24 pm

Could you please report any [NoScript ABE] line you get in your Browser Console (Ctrl+Shift+J) when this happens?
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

User avatar
mikolajek
Posts: 18
Joined: Wed Mar 19, 2014 5:46 pm
Location: Warsaw, Poland
Contact:

Re: ABE exception rule for accessing wireless extender

Post by mikolajek » Wed Aug 13, 2014 9:20 am

Certianly! But there's not too much in here, apart from duplicating ABE settings... Hope it helps!

Code: Select all

[ABE] <LOCAL> Deny on {GET http://dlinkap.local./login.htm <<< http://dlinkap.local./ - 6}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

User avatar
Thrawn
Senior Member
Posts: 3106
Joined: Mon Jan 16, 2012 3:46 am
Location: Australia
Contact:

Re: ABE exception rule for accessing wireless extender

Post by Thrawn » Wed Aug 13, 2014 12:25 pm

The first thing to try is adding

Code: Select all

dlinkap.local.

to the noscript.ABE.localExtras preference in about:config. If that doesn't work, then we can try writing a rule.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.

True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0

User avatar
mikolajek
Posts: 18
Joined: Wed Mar 19, 2014 5:46 pm
Location: Warsaw, Poland
Contact:

Re: ABE exception rule for accessing wireless extender

Post by mikolajek » Wed Aug 13, 2014 12:55 pm

Unfortunately it's not a good solution - it does the trick to connect to dlinkap.local. but at the same time it kills all non-local connections - i.e. I can't access any web page.
Removing the proposed entry gets web access back.
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

barbaz
Senior Member
Posts: 9280
Joined: Sat Aug 03, 2013 5:45 pm

Re: ABE exception rule for accessing wireless extender

Post by barbaz » Wed Aug 13, 2014 2:15 pm

What NoScript version are you using?
Does it work in a clean profile with or without the entry in noscript.ABE.localExtras?
What if you access the router by IP address instead?
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 SeaMonkey/2.28

User avatar
mikolajek
Posts: 18
Joined: Wed Mar 19, 2014 5:46 pm
Location: Warsaw, Poland
Contact:

Re: ABE exception rule for accessing wireless extender

Post by mikolajek » Wed Aug 13, 2014 2:30 pm

I have latest NoScript version - meaning 2.6.8.36.
There's no difference in a completely fresh profile - same happen.
Yet, when accessing the extender by typing its IP address, there's no such problem - all admin panel pages work smoothly.
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

barbaz
Senior Member
Posts: 9280
Joined: Sat Aug 03, 2013 5:45 pm

Re: ABE exception rule for accessing wireless extender

Post by barbaz » Wed Aug 13, 2014 2:35 pm

When you add the entry to noscript.ABE.localExtras, and all web browsing is blocked, do you see anything related in the Browser Console when it fails?
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 SeaMonkey/2.28

User avatar
mikolajek
Posts: 18
Joined: Wed Mar 19, 2014 5:46 pm
Location: Warsaw, Poland
Contact:

Re: ABE exception rule for accessing wireless extender

Post by mikolajek » Wed Aug 13, 2014 3:04 pm

Well... I've cleared the console log, changed the parameter (by adding dlinkap.local. to noscript.ABE.localExtras;) and accessed the random page.
I got blocked and the only new entry that showed up in the console was:

Code: Select all

ReferenceError: banXxByPoz is not defined 0,0.html:156
Use of getUserData() or setUserData() is deprecated.  Use WeakMap or element.dataset instead. requestNotifier.js:63
Use of getUserData() or setUserData() is deprecated.  Use WeakMap or element.dataset instead. requestNotifier.js:63

However, I can't say whether it's related to NoScript.
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

User avatar
Giorgio Maone
Site Admin
Posts: 8742
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: ABE exception rule for accessing wireless extender

Post by Giorgio Maone » Wed Aug 13, 2014 3:30 pm

Please try dropping the localExtras setting (set it to default) and modify the SYSTEM local rule this way:

Code: Select all

Site LOCAL
Accept from LOCAL ^https?://dlinkap\.local\./
Deny
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

User avatar
mikolajek
Posts: 18
Joined: Wed Mar 19, 2014 5:46 pm
Location: Warsaw, Poland
Contact:

Re: ABE exception rule for accessing wireless extender

Post by mikolajek » Wed Aug 13, 2014 7:10 pm

Work as a charm without any problems!

Many thanks for providing this solution!
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

Post Reply