C:\Users\Alexander>tracert 192.168.45.254Routenverfolgung zu 192.168.45.254 über maximal 30 Hops 1 * 1 ms 1 ms OPNsense [192.168.40.254] 2 * * * Zeitüberschreitung der Anforderung. 3 * * * Zeitüberschreitung der Anforderung. 4 * * * Zeitüberschreitung der Anforderung. 5 * * * Zeitüberschreitung der Anforderung. 6 * * * Zeitüberschreitung der Anforderung. 7 * * * Zeitüberschreitung der Anforderung. 8 * * * Zeitüberschreitung der Anforderung. 9 * * * Zeitüberschreitung der Anforderung. 10 ^CC:\Users\Alexander>
Hi, I also had a problem with Wireguard after the upgrade, I solved the problem:1) Firewall > NAT > Outbound: Changed: Automatic outbound NAT rule generation (no manual rules can be used) >>> Hybrid outbound NAT rule generation(automatically generated rules are applied after manual rules)2) Added rule for Wireguard ip pool.
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/route -q -n add -'inet' '/' -interface 'wg1'' returned exit code '68', the output was 'route: bad address:'
2024-03-17T21:57:03-07:00 Notice wireguard wireguard instance main (wg0) started 2024-03-17T21:57:03-07:00 Notice wireguard /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: ROUTING: entering configure using 'opt7' 2024-03-17T21:57:03-07:00 Notice wireguard wireguard instance main (wg0) can not reconfigure without stopping it first.
Add me to the no problems with wireguard list. I'm on 24.1.2_1.(1) Do you use DNS entries as endpoint addresses?I use a dynamic DNS entry for the server endpoint.(2) Do you use tunnel addresses on your instances?I have a /24 tunnel address set on my server instance and a /32 on my client.(3) Do you have allowed IPs on your peers?I have my clients configured as peers on the server instance and 0.0.0.0/0 for my client allowed peers.(4) Do you have the instances assigned as interfaces?I have my server instance assigned as an interface.(5) If yes for (4) do you have an IPv4/IPv6 mode set in the interface?Both IPv4 and IPv6 are set to None on my interface. Also, I don't use IPv6 for my dynamic DNS entry.(6) If yes for (4) do you have VIPs assigned to these interfaces?N/AHope this helps, and I'm happy to try and provide more info for comparison/troubleshooting.
I upgraded to 24.1_3 from 23.7 and immediately experience wireguard problems. No connections worked, no handshake. My wireguard logs showed this entry whenever I restarted the service.
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/ifconfig 'wg2' inet '192.168.200.1'/'24' alias ' returned exit code '1', the output was 'ifconfig: ioctl (SIOCAIFADDR): File exists'
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: ROUTING: gateway IP could not be found for 192.168.200.0/24
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: ROUTING: not a valid opt3 interface