Page 1 of 1
ABE gets confused with hostnames that resolve to the WAN IP
Posted: Fri Mar 13, 2015 4:51 pm
by roothorick
Suppose home.example.com resolves to the WAN IP, and a web server on your router/server/etc. serves pages with links to "home.example.com". The already-loaded page is considered local. However, the links to home.example.com i.e. back to the same site are NOT considered local. This creates an odd situation where ABE prevents your router from linking back to itself.
A quick fix would be, if the current URL's hostname resolves to a local IP, then that hostname is assumed to resolve to the same local IP i.e. is automatically local, even though the link IP isn't explicitly "known".
Re: ABE gets confused with hostnames that resolve to the WAN
Posted: Fri Mar 13, 2015 4:53 pm
by barbaz
Workaround: about:config > add it to noscript.ABE.localExtras
Re: ABE gets confused with hostnames that resolve to the WAN
Posted: Fri Mar 13, 2015 5:29 pm
by roothorick
That setting is broken for me -- it stops all traffic.
The real workaround for me was to add the server's hostname to the system rule.
Re: ABE gets confused with hostnames that resolve to the WAN
Posted: Fri Mar 13, 2015 6:25 pm
by barbaz
That works too, but the fact adding it to localExtras blocks your ability to load it at all would seem to indicates that you're accessing it from something that's not LOCAL or browser's chrome. Unless you're running into a bug.
How are you accessing it?
Please post the message you get in the Browser Console (Ctrl-Shift-J) when the addition to localExtras doesn't work. If it trips the spam filter you can send it to me by PM. (We don't need your WAN IP, the exact real domain name, or any other than the first octet of any private subnet IPs, but we do need to know what each IP/domain in the message is. So feel free to censor those details accordingly if you so desire.)
May or may not be relevant, but does a DNS lookup of the home.example.com in your case show anything other than your WAN IP and possibly private subnets?
Re: ABE gets confused with hostnames that resolve to the WAN
Posted: Sat Mar 14, 2015 4:06 am
by roothorick
barbaz wrote:That works too, but the fact adding it to localExtras blocks your ability to load it at all would seem to indicates that you're accessing it from something that's not LOCAL or browser's chrome. Unless you're running into a bug.
How are you accessing it?
Adding it to localExtras prevents me from loading
anything. Even, say, Google.
I reach the site simply by manually typing the URL, i.e.
https://home.example.com/folder/
Please post the message you get in the Browser Console (Ctrl-Shift-J) when the addition to localExtras doesn't work. If it trips the spam filter you can send it to me by PM. (We don't need your WAN IP, the exact real domain name, or any other than the first octet of any private subnet IPs, but we do need to know what each IP/domain in the message is. So feel free to censor those details accordingly if you so desire.)
This is all that shows up in the console:
Code: Select all
ReferenceError: ALL_BUILTIN_ITEMS is not defined BrowserUITelemetry.jsm:452:0
lpmanuallogins.length is 1
Doesn't look very useful to me.
May or may not be relevant, but does a DNS lookup of the home.example.com in your case show anything other than your WAN IP and possibly private subnets?
It only returns the WAN IP, and I just verified the returned IP is correct.
Re: ABE gets confused with hostnames that resolve to the WAN
Posted: Sat Mar 14, 2015 5:59 am
by barbaz
roothorick wrote:Adding it to localExtras prevents me from loading anything. Even, say, Google.
Oh wow, that is definitely a serious bug (and I can confirm it in Firefox 36.0.1 and SeaMonkey 2.32.1 FWIW). "Firefox can't find the server at [anything]".
Thank you for reporting that.
Regarding the original WAN IP domain name issue, it sounds likely another bug but it's possible the ability to reproduce it depends on factors to do with your specific network setup...
@Giorgio?