From: leroy christophe <christophe.leroy@c-s.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>, arturo.borrero.glez@gmail.com
Cc: netfilter@vger.kernel.org, GUITTON Alex <alex.guitton@c-s.fr>
Subject: Re: Problem setting up nftables dnat : dport set to 0 instead of requested value (22)
Date: Thu, 11 Dec 2014 14:12:46 +0100 [thread overview]
Message-ID: <5489984E.2050601@c-s.fr> (raw)
In-Reply-To: <20141210182244.GA5622@salvia>
Le 10/12/2014 19:22, Pablo Neira Ayuso a écrit :
> On Wed, Dec 10, 2014 at 03:39:04PM +0100, leroy christophe wrote:
>> Hi,
>>
>> I'm trying to redirect incoming tcp connections for port 222 to
>> local port 22 (because I will dnat incoming connections for port 22
>> to another destination).
> Then you have to use "redirect" instead of "dnat". "redirect" will be
> available since the upcoming 3.19-rc.
>
> Cc'ing Arturo, he has worked on the redirect support.
>
> @Arturo: Could you add documentation for your 'redirect' support to ?
>
> http://wiki.nftables.org/wiki-nftables/index.php/Performing_Network_Address_Translation_%28NAT%29
>
> Thanks.
>
Thanks for the information.
I have now applied patches 8d13edd, 9de920e and e9105f1 on my 3.18
kernel, so now the redirect rule is accepted, but I still get the same
issue: dport gets value 0 instead of 22 after the redirect, see below
Is there any other patch to apply ?
Christophe
[ 932.304106] redir IN=eth0 OUT=
MAC=08:00:51:20:44:5b:08:00:27:fe:42:1e:08:00 SRC=172.25.231.37
DST=172.25.231.5 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=22863 DF PROTO=TCP
SPT=55116 DPT=222 WINDOW=14600 RES=0x00 SYN URGP=0
[ 932.304523] rejected IN=eth0 OUT=
MAC=08:00:51:20:44:5b:08:00:27:fe:42:1e:08:00 SRC=172.25.231.37
DST=172.25.231.5 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=22863 DF PROTO=TCP
SPT=55116 DPT=0 WINDOW=14600 RES=0x00 SYN URGP=0
# nft list ruleset -nn
table ip filter {
chain input {
type filter hook input priority 0;
oifname "lo" accept
ct state established,related accept
ct state new tcp dport 22 log prefix "ssh " accept
ip protocol icmp accept
udp dport { 631, 137, 68, 67, 1534, 17500, 138} drop
log prefix "rejected " reject with icmp type
host-prohibited
}
}
table ip nat {
chain prerouting {
type nat hook prerouting priority 0;
tcp dport 222 counter packets 1 bytes 60 log prefix
"redir " redirect :22
}
chain postrouting {
type nat hook postrouting priority 0;
ip saddr 192.168.0.3 oif eth1 masquerade
}
}
next prev parent reply other threads:[~2014-12-11 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 14:39 Problem setting up nftables dnat : dport set to 0 instead of requested value (22) leroy christophe
2014-12-10 18:22 ` Pablo Neira Ayuso
2014-12-10 20:29 ` Arturo Borrero Gonzalez
2014-12-11 13:12 ` leroy christophe [this message]
2014-12-12 10:08 ` leroy christophe
2014-12-12 10:16 ` bug : nft_redirect port byteorder issue leroy christophe
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=5489984E.2050601@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=alex.guitton@c-s.fr \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=pablo@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