Yes you will need a least that. But you may also need the IGMP proxy configured, possibly at both ends, so that clients can see the streams and subscribe to them.

@Gertjan said in Dynamic DNS client "extracted from local system": To know if the WAN IP really changed ? Easy. Store the latest succeeded updated WAN IPv4 address locally. This is the cache file. Compare the actual WAN IPv4 with the cache ;: Just going to take this opportunity to point out that this causes a problem in the case where we restore to a replacement router in our lab before delivery. DDNS is updated to our office IP. Live router will not update because its cached IP didn’t change. (Workaround is to manually modify the file on disk to fool it, as I recall)

I went and changed to yes and the logs seemed to clear up. Thank you again.

@stephenw10 system - advanced - networking - ipv6 options - no checks, but... the WAN - IPv6 Configuration Type - DHCP6 so I changed to none. Thank you sir!

Thnx guys

::1 is IPv6 localhost. Unbound should listen on that address by default but you may have disabled that. Or if you have enabled the forwarder instead. If you have upgraded from a much older version you might have it added specifically in System > General Setup and can remove it from there.

@stephenw10 Well, we're at 48 hours without an incident after switching the ethernet cable that connects the ONT to the router, so it's pretty safe to say you were correct saying it was hardware Thank you for your support, honestly I wouldn't have guessed a damaged cable would cause something so intermittent and short Kind Regards, Mylo

@stephenw10 that is insane.. I had a device that had a multicast mac set on it, company screw up.. It could work - but it could also cause some problems. It was a networking bridge for electric consumption meter, current cost by envi if I recall.. Had to be 10 years ago, I remember it working until I moved it something other than a dumb switch - then I ran into issues.. I remember having to do something with igmp snooping.

An update for anyone who may be experiencing this issue. This issue is caused by ATT's RG firmware. The latency spikes and jitter are resolved on the BGW320-505 as of firmware 6.30.5. This issue was somewhat widely discussed at /r/ATTFiber. Shame on ATT for taking 8+ months to release a firmware which fixed it. And I was only able to get the firmware update by working with a redditor who had a high-level engineering contact at ATT, who was able to MANUALLY push the firmware update to my device. Who knows when it would have rolled out to me... Thank you to @stephenw10 for the help along the way.

@stephenw10 cheers. We shall wait!

I will say that I've only ever seen issues like that when using UFS without RAM disks enabled. Using ZFS or enabling RAM disks should prevent it for the vast majority of cases.

Graylog has taken care of this for me. Creating reports for top dst IP and ports

@mucip said in Internet lost in PfSense but VPN or everythingelse work well?: the monitoring and what is used for? And nice stats : [image: 1731513090451-79f298d6-5237-4445-8459-f960de6df354-image.png] Monitoring the device in front of your pfSense, the ISP router, only tells you something about the cable between them and nothing much about your entire WAN connection. Monitoring for example 8.8.8.8 tells you something about the 'quality' of the connection up until 8.8.8.8. This will includes your entire 'ISP' WAN connection.

@stephenw10 said in Route pfsense itself over VPN.: Hmm, well it sure seems like it's set to serial as primary console from what you're seeing. But as I say you should be able to see which is set at the vga console. Success !!! I made the mistake when creating a static route by typing ip address of openvpn server and then selecting the subnet. Selecting the subnet was a mistake that caused pfsense to be stuck at boot. I created new static route by typing the openvpn server address, chose the appropriate WAN and saved the setting. After reboot, pfsense booted just fine. I created additional static routes for the remaining vpn clients and everything just worked. Rebooted once again, no issues. Then i selected openvpn client as a default gateway and that was it. All tailscale clients are now going through vpn, and all vpn clients connect without any issues after reboot. Thank you very much Stephen. All this would not be possible without your help. Im marking this thread as resolved. Cheers.

Nice! That does imply some ARP issue. You shouldn't really have to do that. But if you do keep that in place you should add it as a system Tunable: https://docs.netgate.com/pfsense/en/latest/config/advanced-tunables.html

@mvikman oh sorry - I must of hit reply on wrong post, corrected ;) thanks Good idea about redmine, I will look to see if anything in there already - and not make the suggestion

Supplement, for future reference if someone encounters the same problem. I did some tests later and ruled out pf, but the problem was the same. The final result was that the esxi virtual machine would check the mac match by default. If it does not match the mac in the vmx configuration file, the communication will fail. Customizing the mac on the gui can only set a fixed prefix, Reference: https://community.broadcom.com/vmware-cloud-foundation/discussion/custom-mac-address-in-esx-4#bm65eebd63-587b-41e1-8108-b951b7ef03d0 And because the new version of esxi parameter definition checkMACAddress is invalid ethernet1.checkMACAddress = "false" I don't want to enable promiscuous mode in the vds port group, so the final solution is to add a network card to modify the vmx configuration of the virtual machine to define two items: ethernet1.addressType = "static" ethernet1.address = "10:2d:3c:40:55:63" Reference: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-F9243FED-F081-498F-B4A9-EF950292AF77.html Of course, modify mac from the system layer, 1, such as pfsense, modify /etc/inc/interfaces.inc Add mwexec ("/sbin/ifconfig vmx0 ether 10:2d:3c:40:55:63"); Updates will be overwritten 2, Windows system settings network card mac and then enable the three items (Promiscuous Mode, MAC Address Changes, Forged Transmits) on vds. It is feasible and communication is possible. I did not adopt this solution

@VioletDragon said in pfSense Auto Backup: Do you know if this will backup configs for like pfBlockerng, Snort etc? You've missed somehow what pfSense is. Ok, its a firewall router. Like many out there, With tonnes of extras. The main difference with other firewalls is that is is for 99,9 % Web interface driven, and it has just one (1) config file. This file contains everything. Just read it : export it and open it in a text editor. You'll get the picture quickly.

No worries, glad you were able to get back up and running.