Subcategories

  • Discussions about TNSR

    18 Topics
    56 Posts
    P
    We’re excited to announce the release of Netgate TNSR 26.02, our latest update packed with powerful new features, expanded capabilities, and over 30 bug fixes and enhancements. What’s New in version 26.02? VPF High Availability State Synchronization Allows peers to automatically re-synchronize connection data when they restart VPF Statistics Output Filters Users can now filter VPF connection statistics output by connection type. This makes troubleshooting and gathering NAT statistics simpler and easier to read. Dynamic Routing Prefix-List Sequence Numbers Input validation no longer allows sequence numbers to start at 0. Upgrading TNSR will renumber entries in the prefix list starting at 1 VPP and DPDK Updates VPP is updated to version Stable/2510, and DPDK is updated to 25.07 Release Notes: https://docs.netgate.com/tnsr/en/latest/releases/release-notes-26.02.html Blog Post: https://www.netgate.com/blog/netgate-releases-tnsr-software-version-26.02 Learn More: https://www.netgate.com/tnsr
  • Discussions about TNSR

    41 Topics
    113 Posts
    P
    Feels like it’s been a while since this topic was brought up, and so much has happened since then. TNSR has really filled out but I’m sure there’s other features our users would love see in future releases. So with that said, please share your feature requests here and let’s see what we can do! —pfGeorge
  • Discussions about installing or upgrading TNSR software

    50 Topics
    196 Posts
    patient0P
    @shood said in install pfsense on opnsense DEC2700: Did you face any problems after installing pfSense on DEC OpenSense? Nope, all working normal. But I did use only the 10Gbit ports (ax0, ax1).
  • This topic is deleted!

    1
    1
    0 Votes
    1 Posts
    7 Views
    No one has replied
  • TNSR and PFSense or just TNSR?

    4
    0 Votes
    4 Posts
    2k Views
    A
    TNSR is a high-performance software router. If you have a need for 10, 40, 100+ Gbps then TNSR may be the solution for you. This overview video may help as well. You can see a list of features of TNSR here. Against other options out there, we feel the price for performance can't be beaten.
  • Introducing the Netgate 6100 Max with TNSR

    4
    2 Votes
    4 Posts
    2k Views
    matlearM
    @jimp said in Introducing the Netgate 6100 Max with TNSR: The page is listing the different platforms on which TNSR is available, that sentence doesn't have any bearing on installation media. There aren't different TNSR software installer images for different bare metal hardware variations like there are for pfSense. Currently the TNSR installation process for hardware only requires a single ISO and that ISO supports everything. Thanks for clearing this up. :)
  • 2 BGP Session dropping randomly same time

    14
    0 Votes
    14 Posts
    4k Views
    DerelictD
    @nbhatti As has been said, we don't know. For what you are describing to happen there would need to be practically zero traffic passing, to both BGP peers, at the same time, for long enough to trigger the hold timer expiration. It doesn't sound like that is the case from what you have stated. Some occasional packet loss will not cause two TCP sessions to stop passing traffic at the same time and not recover. I would packet capture the BGP sessions to the peers (TCP port 179) and try to capture the event. Then load it up into wireshark and see what happened to the session(s). This would best be done at from place in the topography like a switch mirror port mirroring the traffic of the port connected to the tnsr node.
  • [Feature Request] PPPoE with VDSL & PVID capabilities

    1
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • TNSR as NAT problem with setting up forward rule

    7
    0 Votes
    7 Posts
    3k Views
    A
    It is even more odd now. I have it working the only thing I needed to change was the number of CPU assigned. The VM is using 4 threads so I did "dataplane cpu main-core 3" and this prevents the crashing when I reboot after the NAT rule. I still have this message after a reboot in the log though: Jun 18 07:11:40 tnsrrouter vpp[1044]: /usr/bin/vpp[1044]: perfmon: skipping source 'intel-uncore' - intel_uncore_init: no uncore units found Jun 18 07:11:40 tnsrrouter vpp[1044]: /usr/bin/vpp[1044]: perfmon: skipping source 'intel-core' - intel_core_init: not a IA-32 CPU Jun 18 07:11:40 tnsrrouter /usr/bin/vpp[1044]: perfmon: skipping source 'intel-uncore' - intel_uncore_init: no uncore units found Jun 18 07:11:40 tnsrrouter /usr/bin/vpp[1044]: perfmon: skipping source 'intel-core' - intel_core_init: not a IA-32 CPU
  • TNSR vs. PFSense+

    2
    0 Votes
    2 Posts
    2k Views
    H
    @sheebz tnsr is needed for speeds >= 10GBe
  • NAT Reflection (Pure NAT)

    Moved
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Multicore forwarding

    19
    0 Votes
    19 Posts
    6k Views
    L
    @oudenos check private message
  • problem on listing fullroute table with received-routes command

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • TNSR Keyboard Layout (Question Mark Key)

    7
    0 Votes
    7 Posts
    3k Views
    weehooeyW
    @jimp Ah! Cool. Thank you -- I appreciate your patience. Sorry for the false alarm.
  • IPv6 RA / DHCPv6

    3
    1 Votes
    3 Posts
    3k Views
    VentrescaV
    Hello,, any news? :) Cheers. Fabio.
  • tnsr/linux vs pfsense/freeBSD

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Bridge not talking to Bridgeloop Interface

    3
    0 Votes
    3 Posts
    2k Views
    DerelictD
    @fargox Sorry for the delay. In my testing of this I had no trouble using two physical interfaces as bridge members but as soon as I started trying VLAN subifs and Bonds I saw inconsistent behavior. I never saw exactly what you are describing but siminlar things like the ability to ARP in one direction but not the other, etc. I have opened an internal bug report on the matter. Thank you for posting.
  • DNS queryes source interface

    5
    0 Votes
    5 Posts
    2k Views
    VentrescaV
    @jimp said in DNS queryes source interface: The name resolution at the OS level uses systemd-resolve which as far as I can see in its docs (not the TNSR docs, but the docs for the OS) does not support specifying a source address. Using unbound to control this behavior isn't a workaround, it's the most flexible and potentially only way to configure the behavior you want. Ok, now is perfectly clear, thank you again for your help! :)
  • TNSR API payload requirements

    5
    0 Votes
    5 Posts
    3k Views
    F
    @jimp Thanks!
  • Unexpected random crash & reboot

    5
    0 Votes
    5 Posts
    2k Views
    N
    @derelict When you said what are you running it on, I thought you were asking for the hardware :) Anyway, I have turned down the config to just 1 worker. 4 were working fine since last reboot, but since a single core should also service the purpose, I'll put that to 1 worker to see if that works fine. Thanks for the help.
  • TNSR initial config issues

    7
    0 Votes
    7 Posts
    3k Views
    H
    @derelict Thanks, I was not aware this would imply a certain direction from the router. I appreciate the help. I solved the issue which wasn't present on my previous design (pfsense only). It was indeed the mikrotik switch and how it handled vlans in this context a bit differently. I was able to routing going after fiddling with bridge vlans on that device. Sadly, my throughput did not increase as I expected from placing TNSR in as a router for the network, tried some tuning with the dpdk and it just did not get where I was hoping it to go. I'll revisit tnsr when I get my GNS3/CML lab up and running.
  • Prometheus exporter service keeps on crashing

    2
    0 Votes
    2 Posts
    2k Views
    N
    Turns out the service will not work without adding any filters in there. Once I add /interface as a filter, Prometheus service stands up fine showing metrics/data expected. Thanks
  • System monitoring with cores 100% utilized

    2
    0 Votes
    2 Posts
    2k Views
    jimpJ
    TNSR is unlike traditional firewalls and routers (including pfSense). The way TNSR works it is in a tight CPU loop looking for items to process. It's completely normal and expected for it to be using 100% of its configured CPU cores. Monitoring by CPU usage isn't going to be helpful as it has zero bearing on how busy the system is. You can get better stats from Prometheus and look at some of the rate values there, such as vector rate per worker, input rate, and vector rate. Pretty sure this is all well covered by previous threads as well, so search around on those terms and you should find more info.
Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.