This is the documentation for the 21.07 version. Looking for the documentation of the latest version? Have a look here.

TNSR 19.02.1 Release Notes

About This Release

This is a maintenance release for TNSR software version 19.02 with bug fixes and Azure support.

See also

For more information on changes in TNSR version 19.02, see TNSR 19.02 Release Notes.


  • TNSR is now supported on Azure [974]


  • Fixed a problem with removing MAP entries after restarting TNSR [1653]

Known Limitations


  • Attempting to create an ACL containing only a description fails [1558]

    Workaround: Define one or more rules on the ACL.


  • Attempting to change a BFD local/peer address fails [1549]


  • TNSR does not send BGP updates without restarting service with redistribute from connected option [746]

  • Route with aggregate-address via next-hop does not appear in TNSR route table [832]

  • BGP sessions may fail to establish or rapidly reconnect when receiving more prefixes than defined by maximum-prefix limit [858]

  • The maximum-prefix restart command does not work [859]

  • TNSR installs multiple paths for received routes even though support for multiple paths is not enabled [885]

    Workaround: Run systemctl reset-failed frr from the shell to clear the error which will allow the BGP service to start again.

  • Changing update-source from an IP address to loop1 allows a session to establish but remote prefixes do not appear in the FIB until reboot [1104]

  • IPv6 BGP neighbors get entered as peer-groups only in bgpd.conf [1190]

  • BGP import-check feature does not work [781]


  • show route table causes the backend to die with large numbers of routes in the table [506]

    For example, this crash happens with a full BGP feed.

  • Using service dataplane restart can cause clixon_backend to lose its configuration [1383]


  • The DHCP server does not function if an interface is configured as a DHCP client [1801]

    Corrected in the next release under development (19.05).

  • DHCP server uses default VPP interface IP address (169.254.0.x) as a source address for DHCP packets and as a DHCP Server Identifier [1222]

  • Adding a DHCP reservation without a MAC address causes Kea to fail and the entry cannot be removed [1530]

    Workaround: A MAC address is required for DHCP reservations, so always enter a MAC address when creating an entry.

  • Configuring Kea to log all names with * does not work [1307]

    Workaround: Configure each name separately instead of using a wildcard.


  • Local zone FQDN handling for forward (A) and reverse (PTR) data is inconsistent, only allowing one or the other to work as expected for a given FQDN [1384]


  • nginx does not behave as expected with authentication type none and TLS [1086]

    This mode is primarily for testing and not production use.

    Workaround: Use password or certificate-based authentication for RESTCONF.

  • HTTP server runs even though it’s not configured to run after TNSR services restart [1153]

    Workaround: Manually stop the nginx service using systemctl.

  • RESTCONF get of /restconf/data/ does not properly return state data [1534]

  • RESTCONF query replies may contain CDATA tags in JSON [1463]

  • Adding an ACL rule entry via RESTCONF may appear to add a duplicate ACL [1238]


  • Loopback interface responds to ICMP echo from an outside host even when in a Down state [850]

  • Unable to delete an interface if has had an ACL or MACIP applied [1177, 1178]

    Workaround: Remove the entire ACL or MACIP entry. Then, the interface may be removed.

  • MACIP ACL remains in the interface configuration after being removed [1179]

  • Bond interfaces in LACP mode will send LACPDUs even when configured for passive mode [1614]

  • Non-LACP bond interfaces may experience packet drops when a bond member interface is down [1603]

  • MAC address change on tap interfaces may not be reflected in the dataplane until the dataplane is restarted [1502]

    Workaround: Restart the dataplane after changing an interface MAC address.

  • MAC address change on bond interfaces may not be reflected in the dataplane until the dataplane is restarted [1502]

    Workaround: Set the MAC address when creating the bond interface.

  • VLAN tag rewrite settings are only available in subinterfaces [1344]

  • Packets do not pass through a subinterface after the subinterface configuration has been modified [1612]

  • QinQ VLAN termination is not working [1550]

  • ARP replies received from another host on a VLAN subinterface are not processed correctly [1326]


  • An IPsec tunnel which was removed and then added back in may take longer than expected to establish [1313]


  • Permitted default read and write operations cannot be executed if default exec policy is set to deny [1158]


  • twice-nat does not work [1023]

  • NAT mode is not deleted from VPP startup configuration after TNSR services restart [1017]

  • NAT forwarding is not working for in2out direction [1039]

  • NAT static mappings are not added as expected when only the port-local value differs [1100]

  • NAT static mapping with defined ports leads to clixon-backend crash after restart [1103]

  • DS-Lite is not functional; B4 router sends encapsulated IPv4-in-IPv6 packets, but AFTR replies with an error [1626]

  • DS-Lite B4 endpoint is not shown by show dslite command [1625]

  • Unable to view a list of NAT sessions [975, 1456]


  • Deleting a non-empty route table fails with an error and the table remains in the configuration, but it cannot be changed afterward [1241]

    Workaround: Remove all routes from the table before deleting. Alternately, copy the running configuration to startup and restart TNSR, which will make the route table appear again so the routes and then the table can be removed.

User Management

  • When deleting a user key from the running configuration it is not removed from the user’s authorized_keys file [1162]

    Workaround: Manually edit the authorized_keys file for the user and remove the key.

Reporting Issues

For issues, please contact the Netgate Support staff.