OPNsense Forum

English Forums => Virtual private networks => Topic started by: MenschAergereDichNicht on December 22, 2021, 01:02:45 PM

Title: Wireguard handshake
Post by: MenschAergereDichNicht on December 22, 2021, 01:02:45 PM
Hi,

i have a problem with the wireguard handshake. It does not succeed anymore after switching WAN from DHCP to PPPoE.

My setup consists of a PPPoE connection inside a VLAN to the provider network. I use an externally visible IPv6 address to connect the client. The wireguard configuration should be ok as i used the same before when i had a fritzbox in front of the router.

If i look at the Wireguard port on the WAN-interface (pppoe0) i see incoming and outgoing UDP packets. But the outgoing packets do have a incorrect checksum. My current assumption is that this is the reason why the handshake answer does not reach the client.

Because of this i disabled all hardware offload features on that interface as i read that this may cause problems for tcpdump. But there is still a checksum error for the outgoing wireguard packets (UDP packets of other sources are valid).

If i look at the MTU of the wg0 interface i think the default value (1420) is not correct as it does not account for the 8 bytes of the PPPoE header (only 80 bytes for Wireguard).

Because of this i changed the tunnel MTU inside the Wireguard settings to 1412. Afterwards ifconfig shows that the wg0 interface respects the setting. Sadly this does not solve the checksum problem.

if i look at the available interfaces i see an additional interface ("--help") which is also a member of the "tun"-group. I did not find any information regarding this interface. But it still has a MTU of 1420 despite my change.

Therefore i have the following questions:
Title: Re: Wireguard handshake
Post by: MenschAergereDichNicht on December 24, 2021, 01:56:40 AM
Regarding topic 4 in the above list:

It looks like this is an artifact from my trials to start the wireguard-go service from the command line. If one uses "wireguard-go --help" to get a command line option description the service creates a "--help" interface.

Now it is a little bit difficult to destroy this interface.

Update: A reboot helps to get rid of the "--help"-interface