Page MenuHomeVyOS Platform

No NAT translations showing up
Resolved (N/A)PublicBUG

Description

Beneath is an output from when I tried to print NAT translations and on the second attempt I had produced traffic that is translated. Translation is working.

$ show nat destination translations
$ show nat destination translations
Pre-NAT Post-NAT Prot Timeout

Details

Difficulty level
Unknown (require assessment)
Version
1.3-rolling-202101071430
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

dmbaturin added a project: test.
dmbaturin changed Is it a breaking change? from Behavior change to Perfectly compatible.
dmbaturin added a subscriber: dmbaturin.

Source translations are showed correctly as of 1.3.0-rc5. Destination NAT needs verification.

As requested, checked in 1.3.0-rc and it shows the destination translations with basic configuration.

Configuration:

set interfaces ethernet eth1 address '10.2.0.15/24'
set nat destination rule 10 destination address '30.30.30.2'
set nat destination rule 10 inbound-interface 'eth1'
set nat destination rule 10 log
set nat destination rule 10 translation address '10.2.0.15'

Testing:

vyos@vyos6# run sh nat destination translations
Pre-NAT              Post-NAT             Prot  Timeout
30.30.30.2           10.2.0.15            icmp  12
30.30.30.2           10.2.0.15            icmp  29

15:18:04.076019 IP (tos 0x0, ttl 63, id 44132, offset 0, flags [DF], proto ICMP)
    10.1.0.1 > 30.30.30.2: ICMP echo request, id 2289, seq 94, length 64
15:18:04.076127 IP (tos 0x0, ttl 64, id 25163, offset 0, flags [none], proto IC)
    30.30.30.2 > 10.1.0.1: ICMP echo reply, id 2289, seq 94, length 64
15:18:05.077956 IP (tos 0x0, ttl 63, id 44375, offset 0, flags [DF], proto ICMP)
    10.1.0.1 > 30.30.30.2: ICMP echo request, id 2289, seq 95, length 64

[edit]
vyos@vyos6# run sh ver

Version:          VyOS 1.3.0-rc5
Release Train:    equuleus

Thanks! This is definitely a non-issue then, closing.

SrividyaA changed the task status from Resolved to Resolved N/A.Aug 30 2021, 3:31 PM
SrividyaA set Issue type to Bug (incorrect behavior).