@Сергей-3 In your case, the gateway IP should be 10.100.94.53, just like the TUN IP. To restore the TUN IP, restart the Xray instance. By the way, that's what I was saying, I had to tinker with hev-socks5-tunnel, but tune2socks worked right away. Still working on fixes...

With pfSense Plus, the new if_pppoe backend doesn’t handle CARP/HA the same way as MPD—especially when PPPoE is layered over a CARP VIP—so your previous setup won’t work as expected; the practical option is to bind PPPoE directly to the VLAN/physical interface on both nodes and accept slower failover, or continue using MPD if you require fast and seamless HA switching, since there’s currently no official migration path that preserves the same behavior.

redmine: https://redmine.pfsense.org/issues/16784

@stephenw10 said in DHCPv6 Blocks LAN Subnet Changes — How to Fix: Don't believe everything AI tells you! QFT

@w0w I rebooted 26.03-RC prior to upgrading to 26.03 release and noticed that it was working again at that stage.

It is a shame you on 2.7.2, considerable work was done on the widgets prior to 2.8.0 release, much of it performance related, some of it accuracy related. I remember reading each redmine report for details, and I think at least some of your stuff is new, it would be great if you could do 2.8.x patches. If not I will see if I can make 2.8.1 versions, and if I succeed and you ok with it, will post them in this thread.

I kindly ask a moderator/administrator to remove this post if I posted something inappropriate. If so, I apologize.

I was able to compile what seems to be a working xdebug.so module against FreeBSD-16.0-CURRENT-amd64-zfs-20260216-e4bcfe4ebf03-283952 & php85-8.5.2 I've got a decent set of steps one can follow to compile this and get it working. It's a bit of work to document it all though, so if anyone wants to see this please post here.

Hi, Can you update this step here? from v0.4.8 [image: 1771067979617-3f49a6f1-0c9f-45ce-800c-48d4f23ff05b-image.png] Thanks...

@SteveITS AI isn’t going anywhere. It will continue to evolve—becoming more capable, more autonomous, and in many cases, more difficult to control. But I sometimes wonder whether parts of it could become “trapped in time.” If the forums and websites that once fueled its training data slowly fade into inactivity—turning into digital ghost towns—future AI systems might rely heavily on outdated discussions and legacy knowledge. As communities shift away from traditional platforms, what happens to models that were shaped by them? For example, I’m curious whether usage has declined on major platforms like Stack Overflow and similar long-standing forums. If participation drops, does that eventually affect the freshness and diversity of knowledge available for training future systems? Here’s an updated list of AI systems, including the new addition: [ "Claude", "ChatGPT", "OpenAI", "Gemini", "Grok", "SecAI (Netgate/OpenSense/FreeBSD....(add more here) Forum Driven)" ] The forums of the past have evolved and became a data mine for many AI models. Usage trends should already start seeing this. Haha it has a S now for security ... only a matter of time and it will ...

@marcosm said in 25.11 : IPv6 gateway status UNKNONW after boot: The function find_interface_ipv6() shouldn't be returning null at that point since gateway monitoring is done after the interfaces have been configured. ... See if you can find out what's happening when interfaces_configure() gets called in rc.bootup. ... If that command fails it should log something to the system log. Thank you for looking into it, I'll check the function/return value and let you know what I find.

@tinfoilmatt Hi, are you reffering to these modules? [image: 1767033343348-8829c0b6-56af-46cd-a413-6202038b8632-image.png] Unfortunatelly I cannot test it because I don't own any, I'm on x86. @Gertjan uchcom, uart, isci, iscsi, cfiscsi, ctl

@stephenw10 said in Missing tags in the repo: @ohmantics said in Missing tags in the repo: 3008f30d2c2cabdd7e17f7fb922139da8681ffbd That is in 25.11 builds. Thanks! I think my next step is to change off of vtnet to some other virtual NIC type and try to keep the same MACs.