TNSR 18.05 Release Notes

About This Release

This is the first public release of Netgate’s TNSR product.

Please see the TNSR Product Manual for details on the features of TNSR. https://docs.netgate.com/tnsr/en/latest

Known Limitations

[295] Loopback with IPv6 address will not respond to IPv6 pings.

Workaround: none.

[477] Linux route rules for the router-plugin/tap-inject are not cleaned up

If the dataplane crashes, route rules added to the host system network stack are not cleaned up when it restarts.

Workaround: none.

[483] Deleting in-use prefix-list fails

If you attempt to delete an in-use prefix list, the command will fail, but the configuration is left in an inconsistent state.

Workaround: remove the use of the prefix list prior to deleting it.

[490][739] DHCP Server Issues

There are multiple issues with the DHCP Server, it’s use is not recommended at this time.

Workaround: none.

[506] The command “show route table” causes backend crash

A large route table (> 50k routes) can cause the “show route table” command to crash the backend process.

Workaround: Use “vppctl show ip fib” from a shell or vtysh to view route tables when a large number of routes have been added.

[612] RPC error when input includes “<” character

Using the “<” character as input to the CLI can cause an RPC error. The error is properly detected, reported, and handled in the known cases. This affects all cases where there is free-form input.

Workaround: Do not use the “<” character.

[616] Enabling NAT on an outside interface disables services on that interface

If you configure NAT on an outside interface, then that interface cannot provide services (like DHCP, ssh, etc.).

Workaround: none

[618] SLAAC is not supported in dataplane, but host stack interfaces have it enabled.

Workaround: none.

[628] Child SAs can disappear after an IKEv1 SA reauth.

Workaround: none.

[672] Interface speed and duplex show as unknown

The link speed and duplex indicators (visibile with the “show interface” command) can display as “unknown”.

Workaround: Use the “vppctl show interface” command from an OS shell.

[706] Unable to change DHCP client hostname option

The DHCP Client hostname can not be changed.

Workaround: none.

[741] Data plane restart breaks RESTCONF

If you restart the data plane, the RESTCONF service loses it’s connection and does not reestablish it.

Workaround: Restart the data plane via the CLI, which does not have the same issue.

[745] RESTCONF RPC output is invalid JSON

Some RPCs return mutliple line output and the new line characters are not handled properly resulting in the inability of a JSON parser to process the output.

Workaround: none.

[746] BGP updates not being sent when “redistribute from connected” option specified

Routes from connected routers are not propagated when the redistribute from connected option is set

Workaround: none. You can temporarily resolve the problem by resetting the BGP service.

[781] BGP import-check feature does not work

If the import-check option is set and then BGP is configured to advertise an unreachable network then the network is still advertised.

Workaround: none.

[824] unable to create a default route when more than one loopback interface exists

Workaround: none.

[831] Unable to create a second static NAT translation on a loopback interface

Workaround: none.

[832] Route with aggregate-address via next-hop 0.0.0.0 doesn’t appear in routing table

Workaround: none.

[850] Loopback interface can be ping from an outside host even when marked down

Workaround: none.

[858] BGP session constantly flapping when receiving more prefixes than defined in maximum-prefix limit command

Workaround: none.

[859] BGP “maximum-prefix restart” option doesn’t work

Workaround: none.

[860] No warning message in CLI when BGP “maximum-prefix” option is configured

If the maximum number of prefixes is exceeded, there is no indication to a user that this has occured.

Workaround: none.

[861] Unable to set BGP warning-only option for maximum-prefix option.

Workaround: none.

Reporting Issues

For issues, please contact the Netgate Support staff.