"Recent posts
#81
Portuguese - Português / Re: Estações não navegam na in...
Last post by mshonorato - February 11, 2026, 02:13:27 PMConsegui resolver o problema.
Se alguém passar por esse problema a solução é:
Em INTERFACES - WAN, lá no final em "IPv4 gateway rules" tem que escolher seu Gateway.
Mas aí surgiu outro problema, quando marquei essa opção, não consegui mais acessar o fw pela WAN, mesmo com a regra de firewall já criada.
A solução para isso foi modificar a regra já criada lá em FIREWALL - RULES - WAN, em Gateway, tem que escolher a opção 127.0.0.1, a regra não funciona se estiver como Default ou com o Gateway padrão.
Tentei anexar um print para aqui para facilitar para quem precisar, mas nesse segundo post não tem como anexar.
Obrigado pelo espaço cedido.
Se alguém passar por esse problema a solução é:
Em INTERFACES - WAN, lá no final em "IPv4 gateway rules" tem que escolher seu Gateway.
Mas aí surgiu outro problema, quando marquei essa opção, não consegui mais acessar o fw pela WAN, mesmo com a regra de firewall já criada.
A solução para isso foi modificar a regra já criada lá em FIREWALL - RULES - WAN, em Gateway, tem que escolher a opção 127.0.0.1, a regra não funciona se estiver como Default ou com o Gateway padrão.
Tentei anexar um print para aqui para facilitar para quem precisar, mas nesse segundo post não tem como anexar.
Obrigado pelo espaço cedido.
#82
26.1 Series / Re: IPv6 downstream router (Fr...
Last post by Monviech (Cedrik) - February 11, 2026, 02:04:50 PMI understand the usecase, I'm just saying it could also be solved with money. (I do not mean that in a mean way, just stating how it is).
ISPs are the culprit here, they want you to pay more for a static prefix that allows all of this cleanly with no hoops.
ISPs are the culprit here, they want you to pay more for a static prefix that allows all of this cleanly with no hoops.
#83
German - Deutsch / Re: Upgrade auf 26.1
Last post by Patrick M. Hausen - February 11, 2026, 01:34:42 PMHier war das von Anfang an reibungslos, nachdem ich im RC noch einen bug melden konnte, der von Franco fix behoben wurde.
YMMV.
Mach einen Snapshot und probiers aus 🙂 Dazu sind die da.
YMMV.
Mach einen Snapshot und probiers aus 🙂 Dazu sind die da.
#84
German - Deutsch / Upgrade auf 26.1
Last post by k0ns0l3 - February 11, 2026, 01:23:01 PMHallo Community,
Ist die Upgrade auf 26.1 mittlerweile reibungslos oder gibt es immer noch Probleme.
Danke für Info
Lg
Ist die Upgrade auf 26.1 mittlerweile reibungslos oder gibt es immer noch Probleme.
Danke für Info
Lg
#85
26.1 Series / Re: IPv6 downstream router (Fr...
Last post by GerhardHeus - February 11, 2026, 01:21:29 PMThanks for the insight! To give some context, my home setup is designed primarily to segregate IoT devices and other traffic that I don't want in my home network into separate VLANs, so that all non‑trusted devices are kept outside of the main home network. This allows me to apply more granular firewalling, intrusion detection, logging and overall network management, which dictated the current topology.
Beyond this, there is an ambition to get IPv6 running as cleanly and reliably as possible. One might argue "if IPv4 works, why bother with IPv6?" — but for my use case, I want a consistent and future-proof setup, including autonomous operation of downstream routers like FritzBox.
My observation is that:
Using Track Interface + ISC DHCPv6 + basic RA, the FritzBox operates autonomously and reliably, with PD sub-delegation working for both guest and non-guest networks.
Attempts to replicate the same behavior with IA + KEA + parameterized RA have so far been fragile; small misconfigurations can break downstream IPv6 connectivity.
I'm sharing this to highlight that there are real-world home/own built domotica scenarios where OPNsense essentially behaves like an ISP, even with dynamic PD. It would be useful if future KEA/IA guidance explicitly addressed such use cases, so that advanced setups can migrate cleanly when ISC DHCPv6 is eventually deprecated.
Beyond this, there is an ambition to get IPv6 running as cleanly and reliably as possible. One might argue "if IPv4 works, why bother with IPv6?" — but for my use case, I want a consistent and future-proof setup, including autonomous operation of downstream routers like FritzBox.
My observation is that:
Using Track Interface + ISC DHCPv6 + basic RA, the FritzBox operates autonomously and reliably, with PD sub-delegation working for both guest and non-guest networks.
Attempts to replicate the same behavior with IA + KEA + parameterized RA have so far been fragile; small misconfigurations can break downstream IPv6 connectivity.
I'm sharing this to highlight that there are real-world home/own built domotica scenarios where OPNsense essentially behaves like an ISP, even with dynamic PD. It would be useful if future KEA/IA guidance explicitly addressed such use cases, so that advanced setups can migrate cleanly when ISC DHCPv6 is eventually deprecated.
#86
26.1 Series / Re: 26.1.1 MTU Issues on PPPoE
Last post by hakuna - February 11, 2026, 01:16:39 PMOh wow, so this could be the reason of my problems.
I am trying to setup dual-stack at home and right now I have WAN > DHCP
To cut it short, my ISP wants me back to PPPoE for the WAN > DHCPv6 to receive the reservation.
I spent ages today trying to get PPPoE to work but nothing happens, in previous releases was type username, password, save, and connected.
I checked old backup configs, the PPPoE section is exactly the same but nope.
I am stuck with WAN > DHCP now and without IPV6 which only works via PPPoE for my ISP.
I am trying to setup dual-stack at home and right now I have WAN > DHCP
To cut it short, my ISP wants me back to PPPoE for the WAN > DHCPv6 to receive the reservation.
I spent ages today trying to get PPPoE to work but nothing happens, in previous releases was type username, password, save, and connected.
I checked old backup configs, the PPPoE section is exactly the same but nope.
I am stuck with WAN > DHCP now and without IPV6 which only works via PPPoE for my ISP.
#87
26.1 Series / Re: Unbound: dynamic hostname ...
Last post by Patrick M. Hausen - February 11, 2026, 01:13:23 PMQuote from: hakuna on February 11, 2026, 12:07:08 PMEDIT: If anybody knows please let me know how to report bugs: Unbound does not respect: Flush DNS Cache during reload
Reloading the service is purging the cache every time.
Even if you remove the check mark?
#88
German - Deutsch / Re: Welches DSL-Modem für VDSL...
Last post by k0ns0l3 - February 11, 2026, 01:11:33 PMDanke an alle für eure Zeit und nerven Verbindung zum Vigor ist hergestellt, perfekt 🤩
-VOIP funktioniert
-Modem GUI Verbindung funktioniert
-OPNsense vor Fritz box funktioniert
-IPTV funktioniert
Lg
-VOIP funktioniert
-Modem GUI Verbindung funktioniert
-OPNsense vor Fritz box funktioniert
-IPTV funktioniert
Lg
#89
26.1 Series / Re: Unbound: dynamic hostname ...
Last post by hakuna - February 11, 2026, 01:10:25 PMFor future reference, this is an intended behaviour and the ticket was closed in 2021: https://github.com/opnsense/core/commit/4a1bc9f8b5e65651e85385ce0fc6969cd30b2c13
Unbound by design flushes the cache and reload the config on reload, there is an option to avoid that but.
Unbound by design flushes the cache and reload the config on reload, there is an option to avoid that but.
#90
26.1 Series / Re: 26.1.1 MTU Issues on PPPoE
Last post by Enverex - February 11, 2026, 01:04:56 PMI'm seeing the same issue. I found this thread before upgrading so I blanked all the MTU boxes prior to upgrading, but putting 1508 back into the PPPoE adapter post upgrade also results in breaking a lot of the internet as other people here mentioned. I've had to go back to blank/default for now which isn't ideal.
