Categories

  • 385 Topics
    1k Posts
    P
    TNSR is a high-performance software router and VPN concentrator, available on Netgate appliances or in the cloud on AWS and Azure, that delivers speed, flexibility, and cost-efficiency. Leveraging technologies like vector packet processing (VPP), TNSR software offers advanced routing and VPN capabilities for enterprises, service providers, and government organizations at an unbeatable total cost of ownership. Today, Netgate has released TNSR software version 26.02.2. This patch release includes some important bug fixes and improvements. All TNSR users are encouraged to update to this latest version. The Release Notes are available for review. This release contains a number of important bugfixes, including: Fixed a VPF HA heartbeat parsing error can lead to excessive state updates Fixed a Buffer leak with no-multi-seg and large MTU sizes Installing the TNSR Version 26.02.2 Upgrade For detailed upgrade instructions, please refer to the Upgrade Guide on our TNSR documentation page. We recommend saving a backup of the TNSR configuration before making any significant changes or upgrades. You will find Backup and Recovery instructions on our TNSR documentation page. Release Notes: https://docs.netgate.com/tnsr/en/latest/releases/release-notes-26.02.2.html Learn More: https://www.netgate.com/tnsr
  • 123k Topics
    786k Posts
    dennypageD
    said in Unable to automatically start PIMD: @inferno480 said in Unable to automatically start PIMD: guess what, it's still broke in 26.03 final release. It's broken in upstream FreeBSD, and the FreeBSD maintainer appears to have gone awol. If you are only using pimd to bridge multicast between local interfaces (not actually using the PIM protocol), I would suggest using the mcast-bridge package as an alternative. The FreeBSD maintainer has forked his own copy of pimd, and that is what he is now using for the upstream FreeBSD releases. As noted above, this new version is not backward compatible with the prior release version, and changes will be required to the pimd package to support the new version. @kikuyu, FWIW it looks like you are simply bridging between two interfaces rather than actually using PIM. You might have a look at mcast-bridge if you haven't already. It's a lot simpler and supports IPv6 as well.
  • 21k Topics
    131k Posts
    SteveITSS
    @Snailkhan Yes, the free Maxmind account+key is required to be able to download the geographical IP lists/data.
  • 43k Topics
    268k Posts
    R
    @Falcrow said in Ajuda com o LoopBack: Ola pessoal, eu tive de colocar uma internet de 50MB da GVT no local, pois nenhuma outra operadora não fornecer serviços aqui, dentro eu tenho um workflow que responde em um determinado link, no link temos o endereço do ipfixo da internet, porem de dentro não consigo acessar pelo link externo, e preciso do link externo acessando dentro, o modem não faz o loopback. Para ficar mais claro,  link do workflow  http://ipfixo:8099/messenger//emp02/pedcom/000003a2027df8107c6c.htm?user=000003 se eu mudar o ip fixo para o ip interno o link abre aqui dentro. O pfsense no momento, so faz os direcionamento de portas através do NAT, e o DHCP da rede. Alguém pode me ajudar, por mais que eu configure regra de nat tanto pra wan como pra lan, o link não abre dentro da minha rede. Isso é o chamado NAT loopback ou hairpin NAT. O detalhe é que, se o IP fixo está no modem da GVT e o pfSense está atrás dele, habilitar o NAT Reflection somente no pfSense pode não resolver, porque a conexão passa primeiro pelo modem, que não faz esse retorno para a rede interna. Eu tentaria resolver de uma destas formas: Mais simples: usar o IP interno do servidor quando estiver dentro da rede. Mais organizado: usar um nome DNS no lugar do IP fixo e configurar um Host Override no DNS Resolver do pfSense, fazendo esse nome apontar para o IP interno quando acessado pela LAN. Se precisar manter exatamente o IP público no link: verificar a possibilidade de criar uma regra de redirecionamento NAT na interface LAN do pfSense, direcionando o tráfego destinado ao IP público na porta 8099 para o servidor interno. Isso depende da topologia e das regras atuais. A documentação do pfSense recomenda Split DNS como solução preferencial e também explica como configurar NAT Reflection: https://docs.netgate.com/pfsense/en/latest/nat/reflection.html Antes de mexer em várias regras, eu confirmaria também se o endereço público está no modem ou diretamente na WAN do pfSense. Essa informação muda bastante a solução. E teste o link pelo 4G do celular, fora do Wi-Fi, para confirmar que o redirecionamento externo está funcionando normalmente.
  • Information about hardware available from Netgate

    3k Topics
    21k Posts
    stephenw10S
    Running dmesg simply reshows the existing errors from the console buffer. Unless you are saying you see new errors logged with a current timestamp? That would be very surprising though.
  • Information about hardware available from Netgate

    45 Topics
    216 Posts
    luckman212L
    Great stuff ... thank you for the writeup @cmcdonald
  • Feel free to talk about anything and everything here

    4k Topics
    19k Posts
    AndyRHA
    @KOM I do not understand the scoring either, other than a known bug gets paid less and creative chaining is more. I more enjoy the number of zero day bugs that are stored for the event.
Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
Privacy Policy · Cookie Policy