Date: Fri, 03 Jan 2020 18:27:42 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 243062] man ppp: mention default ppp_nat="YES" for rc.conf Message-ID: <bug-243062-9@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243062 Bug ID: 243062 Summary: man ppp: mention default ppp_nat=3D"YES" for rc.conf Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Manual Pages Assignee: bugs@FreeBSD.org Reporter: contact@evilham.com CC: doc@FreeBSD.org I just lost some time over this and didn't think of checking rc defaults or rc.conf, except when someone mentioned it on IRC. There was a related bug for the handbook: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D44443 Having that patch in the handbook would have also saved me the surprise, as= man ppp basically suggests that the NAT functionality is disabled by default, b= ut starting ppp with rc.conf contradicts that. I would think mentioning this behaviour with a hint to man rc.conf would be enough, this can be done under: NETWORK ADDRESS TRANSLATION (PACKET ALIASING) But would also be useful on the second paragraph of the description, where = the -nat flag is introduced. I am willing to propose a patch for this and to re-open 44443 and propose a patch for it too if this approach were acceptable. FTR, this is what I was working on when I discovered this issue and would re-use bits of it as real-life examples of using ppp(oe) on FreeBSD. https://evilham.com/en/blog/2019-FreeBSD-eXO-router/#pppoe https://evilham.com/en/blog/2020-FreeBSD-home-router-legacy-ipv4/#local-leg= acy-ipv4-networking-nat-implementing (as of this bug report these are quite advanced drafts but require more editing) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243062-9>