Nftables src NAT with port range allocation

Nftables src NAT with port range allocation

[Joshua Moore]

Hello,

I am wanting to do a determinate src NAT IP/port range allocation
leveraging nftables. For example, for every "original src
address:original src port" there is a mapped "new src address:new src
port". The original source address is known but the original source
port is unknown. The new src address is known and the new src port is
from a known range or ports.

I thought about leveraging maps to do this but I'm unsure of the best
way to dynamically capture the unknown src address. Any suggestions?

Thanks!

--
Joshua Moore

Re: Nftables src NAT with port range allocation

[Pablo Neira Ayuso]

On Thu, Aug 27, 2020 at 06:02:58PM -0500, Joshua Moore wrote:
> Hello,
> 
> I am wanting to do a determinate src NAT IP/port range allocation
> leveraging nftables. For example, for every "original src
> address:original src port" there is a mapped "new src address:new src
> port". The original source address is known but the original source
> port is unknown. The new src address is known and the new src port is
> from a known range or ports.
>
> I thought about leveraging maps to do this but I'm unsure of the best
> way to dynamically capture the unknown src address. Any suggestions?

table ip nat {
        chain prerouting {
                type nat hook prerouting priority dstnat; policy accept;
                dnat ip addr . port to ip saddr . th dport map { 2.2.2.2 . 80 : 3.3.3.3 . 443 }
        }
}

This is mapping:

       IP saddr     th dport        IP daddr    dport
        2.2.2.2  .     80     ->     3.3.3.3     443

IIRC, this is available since nft 0.9.4, I'm testing with current git
snapshot.

Nftables src NAT with port range allocation

[Joshua Moore]

Hello,

I am wanting to do a determinate src NAT IP/port range allocation
leveraging nftables. For example, for every "original src
address:original src port" there is a mapped "new src address:new src
port". The original source address is known but the original source
port is unknown. The new src address is known and the new src port is
from a known range or ports.

I thought about leveraging maps to do this but I'm unsure of the best
way to dynamically capture the unknown src address. Any suggestions?

Thanks!

-- 
Joshua Moore