Search the Community
Showing results for tags 'noscript'.
Found 1 result
Is this a misconfiguration issue? I observed via tcpdump on eth+, Noscript's ABE feature causing 10.x.x.x to contact the Air server ip on port 80 -- outside the tunnel. Then the Air external server replied outside tunnel -- port 80 -- to 10.x.x.x. This should not happen. Correct? This occurred during the usual back and forth to informaction.com and the OCSP response for Noscript's certificate. Additionally I have my firewall configured so that my local interface *only* connects to the modem/router and Air server ips. It's the AirVPN recommended firewall settings for linux. Anyone else experienced this?