Full NAT in SFOS 18... how?

Why don’t you use a Masq Nat? That will give you network to network.

ian

You need to use Ranges. Networks are not supported by NAT right now. 

If I understand you right I would have to create two new ranges:

• Range 1:
  10.3.100.1 to 10.3.100.254
• Range 2:
  192.168.100.1 to 192.168.100.254

And then create a NAT rule with Range 1 as original destination and Range 2 as DNAT destination.

If I understand you right I would have to create two new ranges:

• Range 1:
  10.3.100.1 to 10.3.100.254
• Range 2:
  192.168.100.1 to 192.168.100.254

And then create a NAT rule with Range 1 as original destination and Range 2 as DNAT destination.

Correct. 

This will be picked up by XG.

You need to select 1:1 under Advanced. 

Hi LuCar,

it worked.

Thanks for the help.

Alexander

... that is good to know, thanks for the info!

But why can't SNAT do the same?

For example I have 2 B-networks (/16)
Original source 192.168.0.1 - 192.168.255.254
Translated source (SNAT) 10.10.0.1 - 10.10.255.254

Unfortunately this function is not available there!

In principle it works, but ...
I would like to have a direct assignment here!

So 192.168.55.12 becomes 10.10.55.12 ...

This would need a 1:1 Mapping on SNAT. The 1:1 Mapping was implemented in the first step for DNAT to keep the netflow open. 

Unfortunately this did not made the cut for SNAT. So it will either use the IP (MASQ) or random ip out of the SNAT range, if you select a Range. 
From a network perspective, this works fine. Reporting Tools on the other hand are not going to work proper.  

I made the same observation and this is exactly the problem, on the "following device" no clear allocation to the source can be made in logging (in my case a web proxy) ...

For example "Peter Sample" comes from 192.168.55.5 and would leave a log entry with the source 10.10.55.5 when calling Google.com.

Thanks for your answer - we hope it will be implemented soon.