Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Daniel L. Miller" <dmiller@amfes.com>
To: Netfilter-Users <netfilter@vger.kernel.org>
Subject: Re: Connection tracking counters increasing
Date: Thu, 07 Mar 2013 10:22:14 -0800	[thread overview]
Message-ID: <assp.0778ac5759.5138DAD6.6040602@amfes.com> (raw)
In-Reply-To: <9C84D171-3207-4A02-81BC-9652F50A254B@alex.org.uk>

On 3/7/2013 10:10 AM, Alex Bligh wrote:
> On 7 Mar 2013, at 17:21, Daniel L. Miller wrote:
>
>> Anything's possible - but I don't have a high-visibility site.  The connection counter increments gradually - a new connection every couple of seconds or so.
> Why would you not expect this to happen? It's an absolute count of the number of
> connections since reboot. Are you quite sure nothing is opening any inbound or
> outbound connections or trying to? Do you have connection tracking on loopback?
>
If it's an informative counter - then I don't care.  If it's active 
state counter - and blocks new connections from happening when it 
reaches the defined maximum - then it's very much a concern.

I'm assuming something has changed - whether it's due to an upgrade, new 
software, or new device on the network I don't know.  I don't know how 
to look at the list of connections to determine what's getting 
opened/accessed/left so I can narrow it down.

At the moment, I have a very small firehol config plus fail2ban. That's 
all I know actively using iptables.  I'm running OpenVPN - at times I 
will setup some iptables dnat/snat for connections to remotes.  So I do 
need to have NAT available otherwise I'd just unload the modules and 
forget about it.  My primary firewall is a Mikrotik router that doesn't 
have these issues - but I want at least a little protection on my main 
server (which this is).

I have a web server running on a VirtualBox virtual machine via a 
bridged interface.  I do not have connection tracking on the VM.  I 
would think the web server would be the primary target of inbound 
connections - for whatever that's worth.  I also run mail and DNS.

I've never had this problem before - but I've been dealing with it for 
about the past month.  I'm sure something's changed - whether it's my 
website's google visibility or a software change I don't know.

-- 
Daniel


  parent reply	other threads:[~2013-03-07 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 16:13 Connection tracking counters increasing Daniel L. Miller
2013-03-07 16:29 ` Jan Engelhardt
2013-03-07 17:07   ` Daniel L. Miller
2013-03-07 17:16     ` Jan Engelhardt
2013-03-07 17:21       ` Daniel L. Miller
2013-03-07 17:44         ` Jan Engelhardt
     [not found]       ` <5138CCB6.3050705@amfes.com>
     [not found]         ` <9C84D171-3207-4A02-81BC-9652F50A254B@alex.org.uk>
2013-03-07 18:22           ` Daniel L. Miller [this message]
2013-03-08  9:08     ` Xiong Wu
2013-03-08 12:19       ` Daniel L. Miller
     [not found]       ` <5139D769.8040606@amfes.com>
     [not found]         ` <17135FC4-FCB8-4E44-843E-3AF0E80C8400@alex.org.uk>
2013-03-08 17:42           ` Daniel L. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=assp.0778ac5759.5138DAD6.6040602@amfes.com \
    --to=dmiller@amfes.com \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox