<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[(http_inspect) source and destination ports are all 80]]></title><description><![CDATA[<p dir="auto">We got a SG-8860-IU<br />
mirrored our WAN port<br />
connected to the WAN interface of the SG-8860-IU<br />
LAN is connected to production network for managing the device<br />
Installed the Snort package, followed the configuration guide<br />
All I see is (http_inspect) source and destination port is 80 matched with random source and destination ports<br />
Ran a few penetration testing tools and hit our internet facing IPs, it does not show up in the alerts tab<br />
What did I miss?</p>
]]></description><link>https://forum.netgate.com/topic/93059/http_inspect-source-and-destination-ports-are-all-80</link><generator>RSS for Node</generator><lastBuildDate>Sat, 10 Oct 2026 08:35:39 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/93059.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 15 Dec 2015 23:30:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to (http_inspect) source and destination ports are all 80 on Thu, 17 Dec 2015 20:34:28 GMT]]></title><description><![CDATA[<p dir="auto">First I would check if Snort actually see HTTP Port 80 traffic and in which direction.</p>
<p dir="auto">Rune these two custom rules just to make sure the traffic is inspected/seen</p>
<pre><code>alert tcp $EXTERNAL_NET 80 -&gt; $HOME_NET [1024:] (msg:"Incoming HTTP Port 80 Traffic"; metadata:service http; classtype:policy-violation; sid:72171001; rev:1;)
alert tcp $HOME_NET [1024:] -&gt; $EXTERNAL_NET 80 (msg:"Outgoing HTTP Port 80 Traffic"; metadata:service http; classtype:policy-violation; sid:72171002; rev:1;)
</code></pre>
<p dir="auto">You can even test AppID with this rule</p>
<pre><code>alert tcp $EXTERNAL_NET 80 &lt;&gt; $HOME_NET [1024:] (msg:"appID HTTP On Known Port"; appid: http; classtype:policy-violation; sid:72171002; rev:1;)
</code></pre>
<p dir="auto">If these rules triggers when surfing HTTP, not encrypted traffic on port 80, then everything is working…if not, maybe your EXTERNAL, HOME, or HTTP port arent set properly..</p>
<p dir="auto">F.</p>
]]></description><link>https://forum.netgate.com/post/591462</link><guid isPermaLink="true">https://forum.netgate.com/post/591462</guid><dc:creator><![CDATA[fsansfil]]></dc:creator><pubDate>Thu, 17 Dec 2015 20:34:28 GMT</pubDate></item></channel></rss>