I run an application on a computer in my lan network that offers me a REST interface to query status information, ... .
That computer runs windows 7, and is identified by hostname myhostname, and has two network interfaces(one lan, and one wifi)
I share my firefox profile over several computers in my home network, including the stationary mentioned above, and some notebooks.
Therefore, I access the REST interface using the hostname to get a url that works from all places (opposed to using localhost which only works on the desktop, or lan address that doesn't work over wifi):
http://myhostname:12345/service/status
When I type the url in the addressbar, everything works fine. But when I attempt to click a hyperlink (http://myhostname:12345/help returns a website listing all available operations), the ABE warning comes up:
Okay, the warning offered me to tweak the options, so I clicked that. Unfortunately, instead of a simple e.g. Temporarily allow myhostname I am presented with the rule-list dialog. While the ? gives some information on how it's supposed to work (wtf is the syntax only in a pdf?), there is no information about the dialog. E.g. what are System rulesets, what User, how is their precedence, what is the precedence of rules, what is the WAN IP \elem LOCAL thing ...Request { GET http://myhostname:12345/service/status <<< http://myhostname:12345/help, http://myhostname:12345/help - 6} filtered by ABE: <LOCAL> Deny
So, in the dialog the comment for the main rule claims, it only allows lan sites to access lan ressources.
Now that is obviously wrong.
Based on what I've read the past 3 hours here in the forums, a dns is only then marked as local, if all ip addresses it points to are part of the private ip range.
Now myhostname has the following ip addresses:
The lan / wifi addresses are all private/link-local, but the Teredo tunneling thing has a public IPv6 (cf. http://en.wikipedia.org/wiki/Teredo_tun ... addressing).Wireless LAN adapter Wireless Network Connection:
Link-local IPv6 Address . . . . . : fe80::xxx
IPv4 Address. . . . . . . . . . . : 10.x.x.x
Ethernet adapter Local Area Connection:
Link-local IPv6 Address . . . . . : fe80::xxx
IPv4 Address. . . . . . . . . . . : 192.x.x.x
Tunnel adapter Local Area Connection* 11:
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
IPv6 Address. . . . . . . . . . . : 2001:0:xxx
Link-local IPv6 Address . . . . . : fe80::xxx
Now, I did not install Teredo myself, it came shipped with windows (already since vista I believe).
So basically, I can't access any modern windows computer by its hostname in my lan?
Anyways, I just thought I'd probably have to include myhostname to the system rule that blocks everything:
Code: Select all
# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL myhostname
Deny