From: Joel Newkirk <netfilter@newkirk.us>
To: Ben Russo <ben@umialumni.com>, netfilter@lists.netfilter.org
Subject: Re: snmptraps incomming on udp port 162 REDIRECT to 4162 not working?
Date: Tue, 5 Nov 2002 12:43:11 -0500 [thread overview]
Message-ID: <200211051243.11962.netfilter@newkirk.us> (raw)
In-Reply-To: <1036512998.8715.44.camel@ben.mis.tnsi.com>
On Tuesday 05 November 2002 11:16 am, Ben Russo wrote:
>
> I tried the following:
>
> iptables -t nat -p udp -m udp --dport 162 -j REDIRECT --to-ports 4162
iptables -t nat -A PREROUTING -p udp --dport 162 -j REDIRECT --to-ports 4162
should redirect all incoming for port 162 to port 4162. You needed to specify
what chain in the nat table (IE, PREROUTING to catch them as they first hit
the firewall). If it still fails then make sure you are allowing packets for
port 4162 through the INPUT chain of the filter table, since that's where
they should pass, and the dport they should indicate.
j
next prev parent reply other threads:[~2002-11-05 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 16:16 snmptraps incomming on udp port 162 REDIRECT to 4162 not working? Ben Russo
2002-11-05 17:43 ` Joel Newkirk [this message]
2002-11-05 18:29 ` Antony Stone
2002-11-05 19:13 ` Ben Russo
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=200211051243.11962.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=ben@umialumni.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