Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MTU of the Wireguard interface when WAN uses a PPPoE connection #2690

Closed
2 tasks done
KuddelSK opened this issue Dec 7, 2021 · 3 comments
Closed
2 tasks done

MTU of the Wireguard interface when WAN uses a PPPoE connection #2690

KuddelSK opened this issue Dec 7, 2021 · 3 comments
Labels
help wanted Contributor missing

Comments

@KuddelSK
Copy link

KuddelSK commented Dec 7, 2021

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

I connect to my ISP using a PPPoE connection. When i configure wireguard and look at the wg0 interface using ifconfig i see a MTU of 1420 (1500 - 80 for the Wireguard header). This is wrong in case of a PPPoE connection as PPPoE adds 8 Byte on its own. Therefore the MTU should be 1412 in this case.

This is not critical as one can manually adjust the tunnel MTU.

I don't know if its relevant to the bug but i have to use a VLAN which provides the ethernet layer for the PPPoE connection.

To Reproduce

Steps to reproduce the behavior:

  1. Use a PPPoE Wan connection
  2. Install the Wireguard service
  3. Configure Wireguard (leave MTU empty for automatic calculation)
  4. Execute "ifconfig wg0" in a router shell

Expected behavior

MTU of 1412 for wg0 in case of a PPPoE connection.

Describe alternatives you considered

One can set the tunnel MTU manually.

Environment

OpnSense 21.7.6
APU 4D4 (GX-412TC CPU; 4 Nics i211AT )

@fichtner fichtner transferred this issue from opnsense/core Dec 9, 2021
@nzkiwi68
Copy link

I'm not sure that statement of 80 bytes for the Wireguard header is correct. From what I am reading, the Wireguard header is only 60 bytes and thus 1420 automatic MTU is fine for PPPoE and non PPPoE connections for IPv4.

Only IPv6 over PPPoE would require an MTU of 1412.

My reference is here:
https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html

@KuddelSK
Copy link
Author

KuddelSK commented Jan 17, 2022

Sorry. I forgot to mention this information inside the issue description.

I configured WAN to use IPv4 and IPv6. I connect to Wireguard using the public IPv6. I guess this is quite common as a non RFC1918 IPv4 is rare these days for home users.

So i guess my suggestion is that an automatic MTU of 1412 should be used if IPv6 is configured for a WAN interface.

@OPNsense-bot
Copy link

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.

@OPNsense-bot OPNsense-bot added the help wanted Contributor missing label Jun 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contributor missing
Development

No branches or pull requests

3 participants