From: Noino <mg8c1zu02@sneakemail.com>
To: netfilter@vger.kernel.org
Subject: Re: local NAT; reconfigured kernel, problems still
Date: Tue, 01 Apr 2008 11:40:14 +0200 [thread overview]
Message-ID: <20080401094014.8143178C95@gam.mel.teaser.net> (raw)
Eljas Alakulppi wrote :
> 1. Are you trying to redirect traffic directed to port 53 to port 10053?
> Use REDIRECT target.
This is overwhelming :-( would you (collective) be so kind as to write out
the needed rule(s) so I can leave you to rest at last ?
>> iptables -t nat -A OUTPUT -o lo -p udp --dport 53 -j DNAT
>> --to-destination :10053
>> iptables: Invalid argument
> 2. DNAT requires destination IP as well.
OK, if I replace an explicit --to-destination 127.0.0.1:10053 , still I'm
getting "Invalid argument" !
Is that diag what you would get ? I suspect my iptables may be out of sync
with my kernel, which is why I dare reiterate my question...
TYVM
--
Noino
next reply other threads:[~2008-04-01 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 9:40 Noino [this message]
2008-04-01 11:00 ` local NAT; reconfigured kernel, problems still Georgi Georgiev
2008-04-01 16:15 ` Noino
-- strict thread matches above, loose matches on Subject: below --
2008-03-31 21:06 Noino
2008-03-31 21:14 ` Eljas Alakulppi
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=20080401094014.8143178C95@gam.mel.teaser.net \
--to=mg8c1zu02@sneakemail.com \
--cc=netfilter@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