itman 2 Report post Posted March 5, 2015 Came across this in a prior thread in this section: iWarren, on 14 Jan 2015 - 3:09 PM, said: Define local ports. If you mean ports that are only opened on the loopback interface, then no. We don't. They are only accessible to applications running on your system and are used for local inter process communication. If you mean if we block ports opened by Windows services on non-loopback interfaces, then the answer is partially. Systems you specified as trusted can access them. All other systems can't. * Do you block windows local ports? I am seriously considering purchasing Online Armor but application localhost loopback monitor is an important feature for me. Specifically, any application outbound connection to 127.0.0.x and inbound application connection from 127.0.0.x. I thought OA had this as a feature but it is not turned on by default? Quote Share this post Link to post Share on other sites
Fabian Wosar 390 Report post Posted March 5, 2015 Online Armor can intercept connection through the IPv4 loopback interface. Just make sure the "Intercept Loopback interface" option under Options/Firewall is enabled. Quote Share this post Link to post Share on other sites
itman 2 Report post Posted March 5, 2015 That's what I thought. Thanks for the reply. Quote Share this post Link to post Share on other sites
Fabian Wosar 390 Report post Posted March 6, 2015 You are welcome. Quote Share this post Link to post Share on other sites
