barbaz wrote:I think NoScript is fingerprinting the device on your WAN IP so that it can protect it better - notably, as said in one the already linked articles, it checks every 5 minutes or so to see if the fingerprint changed, and if it has, it re-obtains the WAN IP. It's maybe also checking to see if you're on a proxy?
I don't really know more about the WAN IP fingerprinting feature than that, sorry.
If you are deliberately port-forwarding from your modem to this server, why are you worried by & surprised at the results of NoScript fingerprinting your WAN IP?
I don't see how it has anything to do with obtaining my WAN IP that NoScript contacts to my LAN server. As I've said previously, problem is not that NoScript "fingerprints" my WAN IP. Problem is that A) NoScript does something it's not supposed to (visits a server in LAN) and B) somehow makes it look like my modem would've been the one that visited, instead of the originating PC.
Also, if we assume that this is some sort of misbehavior for NoScript combined with my equipment and their settings, I'd consider this something serious, since I haven't done anything really fancy with my modem. Unless you consider it as "really fancy" when a person customizes LAN IP range and does port-forwarding for port 80.
If it is by purpose that NoScript visits my LAN server, then I can only ask: why?
Thrawn wrote:Well, the fact that the originating IP is your modem is not surprising. The IP address being used to connect to the server is on a different network, so your traffic goes through the gateway (the modem), and the modem hides what is behind it and provides its own IP address as the source.
It makes no sense that modem would hide source IP, when a LAN device contacts LAN device, especially since I have not (knowingly) enabled/setup anything to make so. I actually just ensured
that when I connect the server with Firefox, apache records my laptop's IP as supposed to.
Thrawn wrote:As for why something is connecting to that server...hard to say, really. It would depend on what is running, and how your modem works. What do you use that server for?
I use the server for backups and samba. I'm planning on expanding it's purpose, which is why I've been doing stuff with apache.
It looks like it has no matter is it Linux/Firefox/NoScript (on laptop) or Windows/Firefox/NoScript (on desktop) combo, both visit my LAN server when Firefox is started. I even went as far as to disable all other extensions except NoScript on (desktop) Firefox and restarted it, my server was yet again visited with IP matching my modem, with timestamp being equal to the time when Firefox (re)started up. Only if I disable NoScript, is when this does not happen.