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

Add option to set the DHCP Interface MTU parameter #79

Open
craigpratt opened this issue Feb 15, 2022 · 0 comments
Open

Add option to set the DHCP Interface MTU parameter #79

craigpratt opened this issue Feb 15, 2022 · 0 comments
Assignees
Labels

Comments

@craigpratt
Copy link
Member

In order to support tunneling inter-AP traffic over vxlans on a network with 1500-byte MTUs the MTU on the micronets network needs to be reduced so the addition of the vxlan headers doesn't exceed the 1500-byte limit.

The DHCP "Interface MTU Option" is supposed to accomplish this proactively - and avoid having to resort to Path MTU Discovery - which can cause some latency during connection establishment. The description of this option is below.

It probably makes sense to add a MTU size parameter to the Micronets definition. But it's TBD if this is set as a NetReach AP parameter or as an agent configuration value.


   This option specifies the MTU to use on this interface.  The MTU is
   specified as a 16-bit unsigned integer.  The minimum legal value for
   the MTU is 68.

   The code for this option is 26, and its length is 2.

    Code   Len      MTU
   +-----+-----+-----+-----+
   |  26 |  2  |  m1 |  m2 |
   +-----+-----+-----+-----+```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant