From: "Dharmendra.T" <dharmu@nsecure.net>
To: Matti Luoma <matti.luoma@bitboys.com>
Cc: netfilter@lists.netfilter.org
Subject: RE: Small problem -> Prerouting
Date: 16 Apr 2003 18:25:48 +0530 [thread overview]
Message-ID: <1050497772.1001.8.camel@india> (raw)
In-Reply-To: <NIENICGJBBAFMLFBMABHGELFCDAA.matti.luoma@bitboys.com>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On Wed, 2003-04-16 at 18:17, Matti Luoma wrote:
Seems to be in use, so i cant remove it, so it
has to be something else...
What module does PREROUTING need anyways?
On Wed, 2003-04-16 at 17:41, Matti Luoma wrote:
Hiya!
Well i upgraded my kernel to 2.4.20 from 2.4.3, and also compiled newest
iptables 1.2.8
now i got this weird problem with
example this line:
iptables -A PREROUTING -t nat -p UDP -d IP -dport port -j DNAT --to IP:Port
It should works, and it works, but not anymore, SSH forwarding like this
works thou
also im gettin some stuff in syslog:
kernel: NAT: 0 dropping untracked packet c66ab6c0
i think these things are related, and probably some module is causing this,
any ideas?
Cheers,
Matti
I guess this is because of conntrack module. Just check do you need this if not remove it.
Do onething, recompile the kernel and enable only the modules which you
want to use.
I guess PREROUTING does not use any external module. If iptables is
enabled PREROUTING will be enabled.
Regards
Dharmu
[-- Attachment #2: Type: text/html, Size: 3620 bytes --]
prev parent reply other threads:[~2003-04-16 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 12:11 Small problem -> Prerouting Matti Luoma
2003-04-16 12:39 ` Dharmendra.T
2003-04-16 12:47 ` Matti Luoma
2003-04-16 12:55 ` Dharmendra.T [this message]
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=1050497772.1001.8.camel@india \
--to=dharmu@nsecure.net \
--cc=matti.luoma@bitboys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox