[Oisf-users] Suricata Stopping Sophos Web GUI on TCP Port 4444

Leonard Jacobs ljacobs at netsecuris.com
Wed Mar 14 01:14:23 UTC 2018

Why would Suricata be stopping communications to Sophos Web GUI on TCP Port 4444 through an IPSec VPN Tunnel?

The weird thing about this is packet captures on both sides of tunnel from the firewalls don't show the traffic being blocked or dropped.  I disconnect the wan connection from Suricata appliance and connect directly to the firewall and everything works.  Suricata running on the outside of the firewall.

In suricata.yaml, I put this HTTP_PORTS: "[80,443,4444]" and it still does not work.  Does the problem have something to do with how Suricata interacts with the IPSec tunnel?  But this does not make any sense because the tunnel comes up and I can even Putty into the firewall command line console and ping the firewall through the tunnel.  For some reason, Suricata does not like ports 4444 and 443 to the private ip address of the firewall through the tunnel.



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify Netsecuris management at mgmt at netsecuris.com. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Netsecuris Inc. The integrity and security of this message cannot be guaranteed on the Internet 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20180313/78084f1d/attachment-0002.html>

More information about the Oisf-users mailing list