I've noticed that the output from "show nat source rules" or "show nat destination rules" is incorrect.
For example:
tim@ferrari:~$ show nat source rules
Rule Source Destination Proto Out-Int Translation
------ -------------- ------------------------------- ------- ----------------- -------------
200 192.168.0.0/16 192.168.0.7 IP eth1 masquerade
sport any dport 8123
210 192.168.0.0/16 192.168.0.5 TCP eth1 masquerade
sport any dport 8920,8920
220 192.168.0.0/16 192.168.0.3 IP eth1 masquerade
sport any dport 8443
230 192.168.0.0/16 192.168.0.5 IP eth1 masquerade
sport any dport {'range': [60000, 60010]}
500 192.168.0.0/16 192.168.0.5 IP eth1 masquerade
sport any dport 53
1000 192.168.0.0/16 0.0.0.0/0 IP @I_wan-interfaces masquerade
sport any dport anyBut:
set nat source rule 230 description 'Hairpin NAT for Mosh Shell on Micro' set nat source rule 230 destination address '192.168.0.5' set nat source rule 230 destination port '60000-60010' set nat source rule 230 outbound-interface name 'eth1' set nat source rule 230 protocol 'udp' set nat source rule 230 source address '192.168.0.0/16' set nat source rule 230 translation address 'masquerade'
So Proto should show "UDP" for rule 230
Another example:
tim@ferrari:~$ show nat destination rules
Rule Source Destination Proto In-Int Translation
------ ------------------------------------------- ------------------------------- ------- ----------------- -------------
50 0.0.0.0/0 0.0.0.0/0 any @I_wan-interfaces 192.168.0.5
sport any dport 49919Shows Proto "any" but this isn't correct, it's only TCP/UDP.
set nat destination rule 50 description 'rTorrent on Micro' set nat destination rule 50 destination port '49919' set nat destination rule 50 inbound-interface group 'wan-interfaces' set nat destination rule 50 protocol 'tcp_udp' set nat destination rule 50 translation address '192.168.0.5'
This is a very very minor bug - but could potentially cause confusion if someone is looking/auditing rules based off the output.