When NoScript is active, FireFox tries to reach out to my primary WAN IP (I have multiple addresses on this interface, running through a Unix-based firewall I've configured) and more worrisome than that, my internal administrative port (444) which I access for configuration since I'm using the SSL port for TCP-based OpenVPN (other port being UDP 1194), and to skirt around coffee shops & other public wifi's restrictions for uncensored Internet (e.g. when I need to perform maintenance on remote servers with SSH, and TCP 22 is blocked).
WAN IP & Port 444
WAN IP & Port 444
When NoScript is active, FireFox tries to reach out to my primary WAN IP (I have multiple addresses on this interface, running through a Unix-based firewall I've configured) and more worrisome than that, my internal administrative port (444) which I access for configuration since I'm using the SSL port for TCP-based OpenVPN (other port being UDP 1194), and to skirt around coffee shops & other public wifi's restrictions for uncensored Internet (e.g. when I need to perform maintenance on remote servers with SSH, and TCP 22 is blocked).
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:27.0) Gecko/20100101 Firefox/27.0
Re: WAN IP & Port 444
I think the connection, that you are seeing, is ABE protecting the WAN Interface of your Router.
NoScript has been offering this protection since July 2010.
See http://hackademix.net/2010/07/28/abe-pa ... r-routers/
In NoScript Options, Advanced, ABE you will see the WAN IP that is being protected.
DJ-Leith
NoScript has been offering this protection since July 2010.
See http://hackademix.net/2010/07/28/abe-pa ... r-routers/
In NoScript Options, Advanced, ABE you will see the WAN IP that is being protected.
DJ-Leith
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0