netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Eray Bilgin <bilgin@eray.ca>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: connection tracking fails to update udp timer
Date: Tue, 11 Mar 2025 15:48:12 +0100	[thread overview]
Message-ID: <20250311144812.GA12767@breakpoint.cc> (raw)
In-Reply-To: <1958568e9a1.be49b3ad53051.1702359735061948725@eray.ca>

Eray Bilgin <bilgin@eray.ca> wrote:
> i noticed this when my voip phone mysteriously stopped ringing. i use
> a tp-link router as a gateway which i'm certain is running
> linux/netfilters, though i don't know what version. i've observed the
> same problem on my raspberry pi running iptables v1.8.2.
> 
> usually the first thing a sip client does is register with the provider's
> server. this has the effect of punching a hole through any firewalls in
> its path. after that initial registration, my provider keeps the
> connection alive by sending messages every 60 seconds.
> 
> when netfilters sees traffic moving back and forth, the connection should
> transition to the assured state and set the expiration timer to
> nf_conntrack_udp_timeout_stream, which by default is 120 seconds. but in
> this case the timer is reset to nf_conntrack_udp_timeout, which is 30
> seconds. the connection does not appear as "assured".

Replies during first 2 seconds are ignored in order to prevent
DNS requests from triggering assured state + 2m timeout.

  reply	other threads:[~2025-03-11 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 13:33 connection tracking fails to update udp timer Eray Bilgin
2025-03-11 14:48 ` Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-11 18:39 Eray Bilgin

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=20250311144812.GA12767@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=bilgin@eray.ca \
    --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;
as well as URLs for NNTP newsgroup(s).