From: Ben Russo <ben@umialumni.com>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: snmptraps incomming on udp port 162 REDIRECT to 4162 not working?
Date: 05 Nov 2002 14:13:46 -0500 [thread overview]
Message-ID: <1036523634.8715.58.camel@ben.mis.tnsi.com> (raw)
In-Reply-To: <200211051829.gA5ITOe19773@vulcan.rissington.net>
On Tue, 2002-11-05 at 13:29, Antony Stone wrote:
> On Tuesday 05 November 2002 4:16 pm, Ben Russo wrote:
>
> > Hi,
> >
> > I tried the following:
> >
> > iptables -t nat -p udp -m udp --dport 162 -j REDIRECT --to-ports 4162
> >
> > Any ideas on how to make this work?
>
> You should have a "-A PREROUTING" in there. I'm not sure about the "-m udp"
> - I presume this is something to do with loading modules for different
> protocol support ? (I don't use modules, but I've seen this sort of thing
> in other people's rules before.)
>
> Antony.
Thanks Antony and Joel,
I'm sorry I was a little confusing there... I had the "-A PREROUTING" in
there when I typed it on the host, just not in the e-mail I sent to the
list. Hopefully this will clear it up a little.... It still doesn't
seem to work, but here is the output of the "iptables-save"
# Generated by iptables-save v1.2.5 on Mon Nov 4 16:06:52 2002
*nat
:PREROUTING ACCEPT [11:2077]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A PREROUTING -p udp -m udp --dport 162 -j REDIRECT --to-ports 4162
COMMIT
# Completed on Mon Nov 4 16:06:52 2002
# Generated by iptables-save v1.2.5 on Mon Nov 4 16:06:52 2002
*filter
:INPUT ACCEPT [1814:266793]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [1073:147564]
COMMIT
# Completed on Mon Nov 4 16:06:52 2002
-Ben.
prev parent reply other threads:[~2002-11-05 19:13 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
2002-11-05 18:29 ` Antony Stone
2002-11-05 19:13 ` Ben Russo [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=1036523634.8715.58.camel@ben.mis.tnsi.com \
--to=ben@umialumni.com \
--cc=Antony@Soft-Solutions.co.uk \
--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