Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Philip Craig <philipc@snapgear.com>
To: John Zornig <j.zornig@uq.edu.au>
Cc: netfilter@vger.kernel.org
Subject: Re: Session tracking failure - ssh packets dropped as INVALID
Date: Mon, 11 Feb 2008 12:10:44 +1000	[thread overview]
Message-ID: <47AFAEA4.2040202@snapgear.com> (raw)
In-Reply-To: <F7BF9AD4-B6CE-4DCB-A2E1-85E16AC38282@uq.edu.au>

John Zornig wrote:
> echo "1" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
> 
> seems to work for my systems. No more INVALID packets.
> 
> Some of the netfilter firewall how-to guides I've found say that  
> ip_conntrack_tcp_be_liberal should never be set on a firewall. So I'm  
> still left wondering if I'm working around a bug and my firewall is  
> not as strict as it should be, or are these how-to's all wrong.

This is just a workaround for a bug.

Are you using a recent kernel?

It would be good to work with Jozsef to get this fixed if you are able
to help debug it.  Also report it on the netfilter-devel list.

To debug, I think the first steps are to enable logging with:

	modprobe ipt_LOG
	echo 255 >/proc/sys/net/netfilter/nf_conntrack_log_invalid

and check your syslog for errors.

Also get a tcpdump of the ssh traffic with something like:

	tcpdump -i eth0 -s 0 -w dump.pcap tcp port 22

  reply	other threads:[~2008-02-11  2:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  3:29 Session tracking failure - ssh packets dropped as INVALID John Zornig
2008-02-10  7:35 ` Eray Aslan
2008-02-10 20:16   ` Martijn Lievaart
2008-02-11  1:08     ` John Zornig
2008-02-11  2:10       ` Philip Craig [this message]
2008-02-11 17:36         ` Jozsef Kadlecsik
2008-02-11 19:32           ` Martijn Lievaart

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=47AFAEA4.2040202@snapgear.com \
    --to=philipc@snapgear.com \
    --cc=j.zornig@uq.edu.au \
    --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