@Gertjan Correct.

We have seen the same issue after upgrading from 2.5.2 to 2.6.0. The first VLAN in the configuration file doesn't have the problem, all the VLAN after have the extra filename options. It is odd that the filename is different. I haven't found where it is getting that option from.

subnet 192.168.240.0 netmask 255.255.252.0 { pool { option domain-name-servers 192.168.243.254; deny dynamic bootp clients; failover peer "dhcp_lan"; filename "legacy.donotuse"; range 192.168.240.80 192.168.243.249; }

@renemg glad things are working as desired. I too noticed that it took a few minutes before I started getting the logs to output in the format you were seeing. Just depends on the number of times things hit on your firewall rules. Happy packet pushing!

@wmheath586 you might also want to drill down further to the MAC address tables in your router. If you are using a managed switch you should be able to telnet into your router and inspect the MAC address table. This would be relevant if you are running multiple VMs and have left the MAC addresses at their defaults.

Just try to resolve it somewhere. In Diag > DNS Lookup in pfSense for example.

If you use an IP address or something actually resolves it must match the actual address IPSec is using.

https://forum.netgate.com/topic/144636/sg-1100-intermittent-reboots

Solved..... I spent 2 weeks to find this issue, posted here... then I cleared my cache and it did the trick.