All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balazs Scheidler <bazsi@balabit.hu>
To: Tim Gardner <timg@tpi.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: 2.4 SNAT fails randomly
Date: Sun, 16 Nov 2003 10:52:06 +0100	[thread overview]
Message-ID: <20031116095206.GA32471@balabit.hu> (raw)
In-Reply-To: <200311151103.47454.timg@tpi.com>

On Sat, Nov 15, 2003 at 11:03:47AM -0700, Tim Gardner wrote:
> I think I have a case where SNAT is sometimes failing. I have a specific case 
> where UDP SNAT fails repeatedly. However, I have SPOOF log entries on some of 
> our servers that indicate TCP is also failing SNAT once in awhile.
>[snip] 
> This client has a NetGear router connected to our firewall. The NetGear router 
> has a well known bug wherein it attempts to get time/date via UDP/NTP from a 
> hardcoded destination (caesar.cs.wisc.edu). This is the UDP packet that is 
> not being SNAT'd. The packet in question is thus:
> 

NAT mappings are established for NEW connections only, isn't it possible that your 
client sent an NTP request while your rule was not yet established? This means that it
is entered the CONNTRACK table without the NAT manip and anything that comes later is
not NATed as it is not a fresh CONNTRACK.

Try filtering this traffic for 180secs and see it disappear from /proc/net/ip_conntrack, 
then remove the filtering and check whether it traversed the  nat/POSTROUTING chain.

-- 
Bazsi

  reply	other threads:[~2003-11-16  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15 18:03 2.4 SNAT fails randomly Tim Gardner
2003-11-16  9:52 ` Balazs Scheidler [this message]
2003-11-16 16:53   ` Tim Gardner
2003-11-18 15:35     ` Tim Gardner
2003-11-18 16:20       ` Balazs Scheidler
2003-11-19  7:46       ` Eldad Zack

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=20031116095206.GA32471@balabit.hu \
    --to=bazsi@balabit.hu \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=timg@tpi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.