FAQ

TNSR^® is Netgate’s a high-performance software router.  It is designed and built from the ground up, using open source software projects including Vector Packet Processing (VPP), Data Plane Developer Kit (DPDK), Free Range Routing (FRR), strongSwan, Clixon, YANG data model and more.  

TNSR software can scale packet processing from 1 to 100 Gbps and beyond on commercial-off-the-shelf (COTS) hardware - enabling a number of secure networking applications to be delivered for a fraction of the cost of legacy brands.

TNSR can be deployed as a bare metal image, VM, or bundled with a Netgate appliance.

It can be managed by CLI or RESTCONF API - the latter enabling multiple instances to be configured and managed via orchestration.

Simply stated, the pfSense project is an open-source firewall software distribution, and TNSR software is an open source-based router.

pfSense software has been in use since 2006, and covers a wide variety of secure networking solution needs. TNSR software is much newer, and to date has been more targeted in its secure networking solution coverage.

While it is entirely possible and plausible that some secure networking use cases can be addressed by either product (albeit with dramatically different performance), TNSR software is not positioned as a “pfSense software replacement”.

For a more comprehensive comparison visit our dedicated TNSR vs. pfSense software page here. 

pfSense software will continue to be developed and supported. TNSR software is meant for users with greater throughput, more stringent traffic needs, and / or prefer multi-instance orchestration management over single-instance GUI management.

There is no plan for a free (Community Edition) version of TNSR software. There is, however, a trial version of  TNSR software. You can get more information about a trial here and pricing here.

Netgate provides a hardware compatibility list (HCL) in our TNSR documentation here.

A bare metal image can be purchased here.

At the time of appliance shipment or bare metal image purchase, the annual subscription software license start date begins and runs for 365 days.

CSPs have their own controls in place for pay-as-you-go and annual subscription license management.

pfSense software users appear in every vertical, and every size / type of organization. Many are likely to remain content with pfSense software for some time. But others, have asked for more than it is designed to provide. TNSR software has been out for a year and has been adopted by customers who needed to solve high-bandwidth (40-100 Gbps) routing and packet filtering problems. TNSR software serves as a product for users with more modest performance requirements - but still beyond the capabilities of pfSense software. Below. we’ve outlined a few use cases where we believe pfSense users may benefit by moving to TNSR software:

As a home user…

1. I have an edge router, firewall and/or VPN appliance equipped with 1 or 10 Gbps NICs. But, the software cannot perform packet processing functions fast enough. This means I am underutilizing my hardware and/or network connection speed.

2. My internet connection now has to deal with more application traffic owing to work at home, household users who are big gamers, an increased use of VoIP, etc. I’ve noticed some performance degradation, specifically slower response time. I’d like to claw that back.

3. I’m really not a big pfSense package user, I just want raw speed for the buck. I built my own appliance. I know the exact access control list (ACL) configuration I want. I just wish I had high-performance firewall software that could keep up with my appliance.

4. I run a homelab. By definition, I can never have too much bandwidth. More importantly, I’m really curious about advanced networking capabilities and want to dive into APIs and Python programming - a necessity for tomorrow’s network engineers. I cannot do that with pfSense software.

As a Small to Medium Business (SMB) user…

1. IoT has led to many more devices using my network uplink, and we are starting to get complaints from our users that things aren’t as fast as the used to be.

2. We bought a new security gateway with 10 Gbps uplinks, but our firewall software cannot run at even 10% of that speed.

3. More and more of our inter-site traffic is sent over IPsec. We know that leads to a sharp throughput decline. Regardless, we still want to use our high-speed links more extensively.

As an Enterprise user…

1. We have to have high-speed IPsec connections between our business locations. The same goes for corporate and remote office links to our data center and cloud instances. 1 and 10 Gbps speeds are de rigueur for us. We’ve spared no expense on for the fastest hardware. We need secure networking software that doesn’t cause it to sputter under load.

2. Intellectual property protection is everything for us. Tight control over each employee and contractor’s application access is a must for us. When a risk is identified, we must be able to administer access control changes in an instant. IT automation is critical.

As a Service Provider…

1. We are running out of IPv4 address space. We need a scalable, performant way to translate large volumes of IPv4/IPv6 addresses.

2. We face severe competition, and must constantly find ways to cut cost and add services quickly and easily. We see open-source software as essential to our long term viability, but do not want to be saddled with having to productize it ourselves.

TNSR has outstanding packet per second (PPS) and Megabits per second (Gbps) throughput. Exact performance will, however, always depend on software release, underlying hardware, and of course, the type of traffic.

See our performance page below for a list of criteria to consider, our latest test setup and results:

https://www.tnsr.com/performance

TNSR can be managed via Command Line Interface (CLI), RESTCONF API (an HTTP-based protocol that provides a programmatic interface for accessing data defined in a YANG data model), or Simple Network Management Protocol (SNMP).

Available commands and capabilities are chronicled in our documentation.

CLI detail can be found in our documentation here:

https://docs.netgate.com/tnsr/en/latest/basics/index.html

RESTCONF API detail can be found in our documentation here:

https://docs.netgate.com/tnsr/en/latest/api/

SNMP detail can be found in our documentation here:

https://docs.netgate.com/tnsr/en/latest/monitoring/snmp.html 

Yes. A growing number of API code modules are already written and openly shared in our documentation here, including the ability to choose exact syntax by TNSR software release.

Currently, TNSR can be trialed for free by filling out the form here, and wording with our sales / sales engineering team to first ensure that the product is suitable to address your secure networking need.

Every network is different, solution needs are often quite detailed in terms of required features / protocols, and TNSR is evolving rapidly. As a result, we are finding that a little bit of up front dialog about your need goes a long eway to us ensuring a successful trial outcome. 

Our trial process is roughly as follows:

1. Trial form submitted
2. Problem / solution discussion with sales
3. Customer support engineer assigned
4. Trial scope meeting
5. Evaluation plan created
6. Evaluation plan walk through
7. Trial start
8. Checkpoint meetings
9. Trial complete