From: Christian Reis <kiko@async.com.br>
To: linux-kernel@vger.kernel.org
Subject: DCC masquerading broken in 2.4.19?
Date: Thu, 29 Aug 2002 13:32:39 -0300 [thread overview]
Message-ID: <20020829133239.C7981@blackjesus.async.com.br> (raw)
Hi there,
I'm getting messages like this in my logs, along with DCC sends from the
local network to external hosts failing:
Aug 29 12:44:27 anthem kernel: Forged DCC command from 192.168.99.3: 200.206.134.238:2049
Aug 29 12:44:29 anthem kernel: IN=eth1 OUT= MAC=00:04:75:7d:2b:6b:00:80:37:d9:4f:90:08:00 SRC=200.158.184.167 DST=200.206.134.238 LEN=60 TOS=0x00 PREC=0x00 TTL=60 ID=3428 DF PROTO=TCP SPT=35838 DPT=2049 WINDOW=5808 RES=0x00 SYN URGP=0
Aug 29 12:44:35 anthem kernel: IN=eth1 OUT= MAC=00:04:75:7d:2b:6b:00:80:37:d9:4f:90:08:00 SRC=200.158.184.167 DST=200.206.134.238 LEN=60 TOS=0x00 PREC=0x00 TTL=60 ID=3429 DF PROTO=TCP SPT=35838 DPT=2049 WINDOW=5808 RES=0x00 SYN URGP=0
[...]
anthem:~$ lsmod
Module Size Used by
ipt_MASQUERADE 1232 1 (autoclean)
ipt_LOG 3184 2 (autoclean)
ipt_limit 912 3 (autoclean)
ipt_state 560 28 (autoclean)
iptable_filter 1696 1 (autoclean)
ip_conntrack_irc 2560 0 (unused)
ip_conntrack_ftp 3440 0 (unused)
ip_nat_irc 2416 0 (unused)
ip_nat_ftp 3120 0 (unused)
iptable_nat 13552 3 [ipt_MASQUERADE ip_nat_irc ip_nat_ftp]
ip_conntrack 13792 4 [ipt_MASQUERADE ipt_state ip_conntrack_irc ip_conntrack_ftp ip_nat_irc ip_nat_ftp iptable_nat]
ip_tables 10880 8 (autoclean) [ipt_MASQUERADE ipt_LOG ipt_limit ipt_state iptable_filter iptable_nat]
iptables is 1.2.6a, and I think at least i've applied all pending-patches.
Has anything changed noticeably? lsmod tells me I am all set, so what
could it be?
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
reply other threads:[~2002-08-29 16:28 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=20020829133239.C7981@blackjesus.async.com.br \
--to=kiko@async.com.br \
--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
all inboxes | Powered by JetHome®