Messages

Thank you, Franco.

The errors there are when I ping 10.1.2.1 from WireGuard client 10.1.2.3:

Code Select Expand

root@OPNsense:~ # netstat -nr 10.1.2.3
            input        (Total)           output
   packets  errs idrops      bytes    packets  errs      bytes colls
        13     5     0       1662          9     0        920     0
        10     9     0       1636          1     0        178     0
        16    10     0       2356          7     0        688     0


The PINNED flag is there either I delete (unassign) the opt1 from wg1 or not.

I have the same problem.

When I run without -q, I get:

Code Select Expand

add net 10.1.2.3: gateway wg1 fib 0: route already in table

I removed the WireGuard twice, even uninstalled the plugin. Didn't help.
However, I don't think running this is necessary as the route is there as it probably got there from the "Tunnel Address" field, which has the CIDER and this is correct:

Code Select Expand

root@OPNsense:~ # route show 10.1.2.1
   route to: OPNsense
destination: OPNsense
        fib: 0
  interface: lo0
      flags: <UP,HOST,DONE,STATIC,PINNED>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0     16384         1         0
root@OPNsense:~ # route show 10.1.2.3
   route to: 10.1.2.3
destination: 10.2.0.0
       mask: 255.255.0.0
        fib: 0
  interface: wg1
      flags: <UP,DONE,PINNED>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1420         1         0


It worked before the 23.7.4 update, soo... waiting for "Note that the WireGuard plugin improvement effort is still going on ..."

Let me know if you need some tests or better diagnostics.