All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Snodgrass <ssnodgra@pheran.com>
To: netfilter@lists.netfilter.org
Subject: Netfilter dropping packets with valid conntracks on RHEL4?
Date: Wed, 18 Jan 2006 19:47:15 -0500	[thread overview]
Message-ID: <20060119004715.GA11129@shadow.pheran.com> (raw)

I'm running a firewall on RHEL4 (kernel 2.6.9-22.0.1.ELsmp) and have been
seeing some strange problems affecting the IMAP connections from my mail
client, mutt.  It seems that occasionally netfilter will decide to start
dropping packets from an IMAP session that has been established and running
fine for hours, causing mutt to hang.  Here's an example (this is the
output from the LOG target before the default deny statement at the end
of the iptables rules):

Jan 18 17:04:40 xxxx kernel: IN=eth1 OUT=eth0.21 SRC=192.168.10.9
DST=192.168.0.10 LEN=1500 TOS=0x00 PREC=0x00 TTL=62 ID=31009 DF PROTO=TCP
SPT=143 DPT=35857 WINDOW=63712 RES=0x00 ACK URGP=0

But, this entry exists in the conntrack table:

tcp      6 431979 ESTABLISHED src=192.168.0.10 dst=192.168.10.9 sport=35857
dport=143 packets=823 bytes=666482 src=192.168.10.9 dst=192.168.0.10 sport=143
dport=35857 packets=629 bytes=257842 [ASSURED] use=1

The very first rule in iptables is:

ACCEPT     all  --  anywhere   anywhere    state RELATED,ESTABLISHED

Has anyone seen this before?  Is there anything I can do to further
debug this?  Unfortunately I do not have any way to cause this behavior
at will, it just seems to happen at random.

-- 
Steve Snodgrass * ssnodgra@pheran.com * Network and Unix Guru(?) at Large
Geek Code: GCS d? s: a C++ U++++$ P+++ L++ w PS+ 5++ b++ DI+ D++ e++ r+++ y+*
"If you want to be somebody else, change your mind."  -Sister Hazel


                 reply	other threads:[~2006-01-19  0:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060119004715.GA11129@shadow.pheran.com \
    --to=ssnodgra@pheran.com \
    --cc=netfilter@lists.netfilter.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 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.