[Bug 203695] [patch] net/mpd5: Add RFC 4638 client support (PPPoE MTU > 1492)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Oct 11 10:53:06 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203695
Bug ID: 203695
Summary: [patch] net/mpd5: Add RFC 4638 client support (PPPoE
MTU > 1492)
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Keywords: patch
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: mav at FreeBSD.org
Reporter: david at wood2.org.uk
Keywords: patch
Assignee: mav at FreeBSD.org
Flags: maintainer-feedback?(mav at FreeBSD.org)
Created attachment 161904
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161904&action=edit
Patch adding RFC 4638 client support (generated using svn diff)
Kernel support for the RFC 4638 PPP-Max-Payload tag was added to HEAD in base
r287654 and MFCed to stable/10 in base r288918 .
The user space support has been developed by Dmitry Luhtionov, one of the mpd5
maintainers. I backported the RFC 4638 support to mpd-5.7, debugged and tested
it - see https://sourceforge.net/p/mpd/bugs/54/#14d2 for details.
The attached patch is is patch-rfc4638 and patch-rfc4638-supplementary from the
bug comment merged together, then split into one source file per patch file,
following normal FreeBSD ports tree practice. I have built and tested the
resulting port on my machine, which works correctly.
The patch should not affect the compilation or operation of mpd5 on machines
that lack kernel support for the PPP-Max-Payload tag.
DOCUMENTATION
To set an MTU less than or equal to 1492:
set link mtu <n>
(as normal)
To set an MTU greater than 1492:
set pppoe max-payload <n>
(do not use set link mtu, as this leads to a configuration error before being
ignored)
IMPORTANT
You must set the MTU of the interface(s) used for PPPoE to a minimum of 8 bytes
higher than the desired PPPoE MTU. This means jumbo frame support is required
for a PPPoE MTU > 1492.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list