@stephenw10 The Assisted Mode has IPv6 fully working again with no errors in the log. As a 'promising' side-effect, my HomePods have suddenly remembered how to play an Apple Music playlist again; something that stopped a few Apple updates ago. If I select SLAAC again, Apple Music becomes stupid again. I didn't think this issue would be IPv6 related, especially with IPv6 apparently working (at least for the most part). I still have no idea what is up with SLAAC though, so this issue may still impact others, but Assisted Mode works for me. Anyway, thanks Steve, 2 issues resolved for the price of 1. ️

@GennP said in Wake on Lan default port: But all applications I have seen use port 9 So? Again doesn't matter.. Like I said 7 and 9 have become common use for such applications. Has zero to do with wol working or not. 9 is the old discard protocol. Not like the nic for the wol is waiting to see traffic on a specific port.. Its waiting to see its mac in a frame.. What port used by some application as it puts it on the wire is meaningless.. Unless you were looking to forward that through router maybe when above layer 2.. As to why they landed on 40000 vs say 9, have no idea really - but doesn't matter at all.. They could of used 42666 or 9999, it makes no difference.

@Gertjan Thanks!!!!! At the moment I have everything updated. But to check the script, I run: "/usr/local/bin/php -q /root/pkg_check.php" manually. The answer is: "pfSense version 23.05.1 (installed) is current" This is fine? Now wait for some kind of update? :)

I've got what seems to be the same issue. I've had 2.6.0 for some time with no issues. I did a clean install of 2.7.0 on a second PC and imported the config. I had trouble getting it to connect and then it suddenly did. It's been working OK for a week through a few reboots but it has suddenly stopped connecting again. Tried several reboots but still wouldn't connect. Gone back to the old 2.6.0 PC and connected straight away. Please do post if you find a solution to this issue. D.

The built-in setting for cookie protection uses the new syntax in the newest version of the package on Plus 23.05.1/CE 2.7.0: https://redmine.pfsense.org/issues/13343 You may be able to use the syntax from that as a guide for your custom settings if you even still need them rather than using the GUI options.

Take a look at: https://youtu.be/FJSHMyrd29E?t=1299

@stephenw10 No, it only does after I've imported my configs Nothing is preventing the FW to connect out, same hardware (hardware settings, KVM/QEMU VM, same Linux Debian host, same switches config, ISP.. all the same) Yes, it does on every page, unfortunately

TAC subscriptions are valid from purchase so I would expect that to have expired. If you send me the NDI in chat I can check it. Steve

LOL, this smarty pants tried upgrading the pool, too, with equivalent results. My user (me) was very angry with the sysadmin (me)!

The OpenVPN logs can be seen in the gui in Status > System Logs > OpenVPN. If you want full content logging you will need to use Squid in full intercept mode: https://www.youtube.com/watch?v=xm_wEezrWf4&t=274s

Did you have other certs or CAs already defined and/or in use?

Then I would post in the main pfatt thread, someone else there has probably hit this: https://forum.netgate.com/topic/99190/att-uverse-rg-bypass-0-2-btc/537

Can you ping anything other than the two configured DNS server IPs? 8.8.4.4 for example. Setting those adds static routes for them in pfSense which could potentially be wrong. Can pfSense itself connect out? Install packages? Or ping out from Diag > Ping? What you have configured looks OK. Do you actually see the auto outbound NAT rule created for 10.10.1.0/24?

What's the WAN actually connected to? Is it actually losing link like that? Not that the WAN flapping should cause php to get hung up like you're seeing. What's in the main system logs when that happens?

I don't believe it can be added to the included packaged version. And I don't think it's possible to pull in the pro version from their repos to 23.05. The build versions would not be matched.

Hmm, that php error looks like this: https://redmine.pfsense.org/issues/13562 But that should have been fixed. You might want to add your result there.

What's actually broken here? You are just seeing that error? Something is trying to connect to somewhere that has no route. So usually that's because the firewall lost it's default route (otherwise it would have a route). It could also be some local gateway that has stopped responding that it needs for a route. OVH is notorious for weird addressing/subnetting schemes so you might have something odd like a gateway outside the local subnet. Steve

@ozanbabatas My problem is solved. Now I can connect VPN to the modem through a remote server and access it. Thanks

If you do that I recommend unchecking Backup SSH keys when you backup the config so you don't end up with the same keys on all hosts. That also affects the auto-config-backup key which you would want to be unique. Steve