public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Todor" <tbelev@globaltech-bg.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel 2.4.6 problem with iptables
Date: Fri, 13 Jul 2001 14:36:21 +0300	[thread overview]
Message-ID: <000601c10b90$09febc50$600ba8c0@int.globaltechbg.com> (raw)

Hi all, 
Before 2 hours I Have a good working 2.4.4 with custom Firewall iptables
rules.
After upgrading to 2.4.6 and aplayng the same Iptables rules I'm
receiveing  many messages at kernel log:

Jul 13 12:36:45 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:36:49 ns kernel: ipt_unclean: TCP option 4 at 26 too long
Jul 13 12:36:49 ns kernel: ipt_unclean: TCP option 4 at 26 too long
Jul 13 12:36:55 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:36:55 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:09 ns kernel: ipt_unclean: TCP option 8 at 22 too long
Jul 13 12:37:09 ns kernel: ipt_unclean: TCP option 8 at 22 too long
Jul 13 12:37:10 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:10 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:15 ns kernel: ipt_unclean: TCP option 8 at 22 too long
Jul 13 12:37:15 ns kernel: ipt_unclean: TCP option 8 at 22 too long
Jul 13 12:37:16 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:16 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:25 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:25 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:26 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:26 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:35 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:35 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:36 ns kernel: ipt_unclean: TCP option 2 at 40 too long
Jul 13 12:37:36 ns kernel: ipt_unclean: TCP option 2 at 40 too long

I'm using the same configuration from the old kernel.
Please help me !!!

Thanks 
Todor Belev
System/Network Administrator
Globaltech-BG 
Sofia, Bulgaria


                 reply	other threads:[~2001-07-13 11:36 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='000601c10b90$09febc50$600ba8c0@int.globaltechbg.com' \
    --to=tbelev@globaltech-bg.com \
    --cc=linux-kernel@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