Categories

  • Discussions about TNSR

    387 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

  • Discussions about pfSense Software, click a category below

    123k Topics
    786k Posts
    M
    @benand20 said in pfSense CE 2.8.0 upgrade stalls after reboot and gets stuck in Stage 2: Ok, now I feel dumb... In one of the other areas of the forum it mentioned there could be EFI issues with the HP DL360/380 systems. I then attempted to switch the system BIOS into "Legacy Mode" which seems to have resolved the problem. So it seems per the other thread, they could very well be correct as there is something in EFI that is causing this problem. I will have to see if I can do the changeover for my primary production router as well. So my next upgrade procedure will be re-install 2.7.x on the legacy BIOS, Import my backup while in legacy bios and then attempt to upgrade to 2.8.1. Sorry to reply to an old post but did this process work? Switching to 2.7.2 with legacy bios and then upgrading. Thanks.

  • Discussions about pfSense software packages

    21k Topics
    131k Posts
    C
    If anyone else is migrating from Avahi to mDNS Bridge, here's something I ran into outside my OpenVPN testing. Avahi documents that its reflector drops the “unicast reply” bit when reflecting queries. That meant replies used the multicast path my firewall rules already allowed: 224.0.0.251, UDP port 5353. mDNS Bridge preserves that bit, so devices can reply directly to pfSense’s interface IP instead. My existing multicast rule didn't cover that destination. I kept the existing rule on each participating VLAN: Pass IPv4 UDP Source: VLAN’s subnets Destination: 224.0.0.251 Destination port: 5353 And added this rule for unicast replies (new rule needed for mDNS bridge): Pass IPv4 UDP Source: VLAN’s subnets Destination: VLAN’s interface address (<VLAN> address) Destination port: 5353 With Avahi, the multicast rules had been enough in my setup. After adding the unicast rules, discovery started working again with mDNS Bridge. Turned out to be the reply path.

  • Discuss pfSense in other languages

    43k Topics
    268k Posts
    C
    Olá! Esse tipo de bloqueio com os sites dos Correios (buscacep.correios.com.br) geralmente acontece por causa da inspeção SSL/TLS (SSL Bump) ou regras de filtragem de URL no SquidGuard / Squid. Como os Correios utilizam certificados específicos e conexões seguras restritas, o proxy acaba interceptando a requisição e gerando falha de handshake ou bloqueio por reputação de IP/domínio. Para resolver isso, você pode seguir estes passos no seu pfSense: Bypass no SSL Interception (SSL Bump): Se você utiliza o Squid em modo HTTPS Inspection, adicione os domínios dos Correios à lista de exceções (Bypass Destinations) para que o proxy não faça o MITM (man-in-the-middle) nos certificados deles. Domínios úteis para liberar: .correios.com.br Ajuste no SquidGuard / ACLs: Verifique se a categoria de IP/URL dos Correios não caiu acidentalmente em alguma blacklist genérica (como "Marketing", "Suspicious" ou "Dynamic DNS"). Adicione a URL na aba Target Categories como uma regra de Allow (Permitir) sem restrição de tempo. Verificação de DNS / Resolver: Garanta que o pfSense está utilizando servidores DNS públicos confiáveis (como Google 8.8.8.8 ou Cloudflare 1.1.1.1) e que o DNS Forwarder/Resolver não está cacheando respostas antigas de IPs dos Correios que mudam com frequência. Dica de validação e testes: Caso precise testar consultas de CEP ou validar se o problema é restrição de rota/IP da sua rede, você também pode utilizar bases de dados e APIs alternativas de apoio, como a plataforma CEP-BR (cep-br.com), para garantir que seus sistemas continuem operando mesmo se houver instabilidade nos serviços dos Correios.

  • 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
    218 Posts
    P
    @keyser Yes, I would also like to know if this helps anything in 26.10. Thank You,

  • 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

Looks like your connection to Netgate Forum was lost, please wait while we try to reconnect.