Pull request: 5281-dhcp-mtu-opt
Merge in DNS/adguard-home from 5281-dhcp-mtu-opt to master Updates #5281. Squashed commit of the following: commit fd97ab7ca4745c7ac2f82261dce42d377dede8b7 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Mar 7 15:40:33 2023 +0300 all: fix docs commit eb4ecc12efab1acb3755e4ff2708a490adf6855d Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Mar 7 15:37:07 2023 +0300 all: imp docs, log changes commit 887a28af8590da454763725b298baee2d022ce38 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Mar 7 14:35:12 2023 +0300 dhcpd: rm default mtu
This commit is contained in:
@@ -263,15 +263,12 @@ func (s *v4Server) prepareOptions() {
|
||||
|
||||
// IP-Layer Per Interface
|
||||
|
||||
// Since nearly all networks in the Internet currently support an MTU of
|
||||
// 576 or greater, we strongly recommend the use of 576 for datagrams
|
||||
// sent to non-local networks.
|
||||
// Don't set the Interface MTU because client may choose the value on
|
||||
// their own since it's listed in the [Host Requirements RFC]. It also
|
||||
// seems the values listed there sometimes appear obsolete, see
|
||||
// https://github.com/AdguardTeam/AdGuardHome/issues/5281.
|
||||
//
|
||||
// See https://datatracker.ietf.org/doc/html/rfc1122#section-3.3.3.
|
||||
dhcpv4.Option{
|
||||
Code: dhcpv4.OptionInterfaceMTU,
|
||||
Value: dhcpv4.Uint16(576),
|
||||
},
|
||||
// [Host Requirements RFC]: https://datatracker.ietf.org/doc/html/rfc1122#section-3.3.3.
|
||||
|
||||
// Set the All Subnets Are Local Option to false since commonly the
|
||||
// connected hosts aren't expected to be multihomed.
|
||||
|
||||
Reference in New Issue
Block a user