On Tue, 16 Mar 2021 13:59:20 +0100, Klemens Nanni wrote: > It doesn't hurt however to mention the specific message such that users > can tell *when* that happens; perhaps add it under DIAGNOSTICS as the > various wifi driver manuals, e.g. athn(4) do?
I think it makes more sense to have the information in the MTU/MSS ISSUES section where people are more likely to look for it. There are other surprising things about how pppoe(4) behaves with respect to MTU that could use documenting. For example, it stashes the MTU of pppoedev and doesn't refresh it when the MTU of pppoedev changes. - todd
