public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Troy Piper <jtp@dok.org>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <laughing@shared-source.org>, rusty@rustcorp.com.au
Subject: [Problem] Linux 2.4.5-ac17 ipt_unclean 'fixes'
Date: Sat, 14 Jul 2001 17:00:21 -0500	[thread overview]
Message-ID: <20010714170021.B1391@dok.org> (raw)


[-- Attachment #0: Type: message/rfc822, Size: 1011 bytes --]


Alan, 

I apologise for having taken so long to write this (I have known about 
this problem since 2.4.5ac17 and have not had a chance to document til 
today) but there seems to be a problem with the ipt_unclean fixes by Rusty 
Russell.  ANY incoming packets from any interface (ppp0 and eth0) are 
marked as 'unclean' with some variation on the following syslog entry:

Jul  8 23:16:04 paranoia kernel: ipt_unclean: TCP option 3 at 37 too long
Jul  8 23:16:05 paranoia kernel: ipt_unclean: TCP option 3 at 37 too long
Jul  8 23:16:16 paranoia kernel: ipt_unclean: TCP option 3 at 37 too long
Jul  8 23:16:18 paranoia kernel: ipt_unclean: TCP option 3 at 37 too long

and thus are blocked by my 'unclean packet dropping' firewall (iptables).

I haven't seen any mention of this on the list, nor have I seen any more 
ipt_unclean patches to address this problem, so here's your heads-up 
(albeit a bit late).

Thanks,

J Troy Piper
jtp@dok.org

             reply	other threads:[~2001-07-14 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 22:00 J Troy Piper [this message]
2001-07-14 22:50 ` [Problem] Linux 2.4.5-ac17 ipt_unclean 'fixes' Josh McKinney
2001-07-16 10:28 ` Rusty Russell
2001-07-16 22:09   ` J Troy Piper

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=20010714170021.B1391@dok.org \
    --to=jtp@dok.org \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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