[Bug 243062] man ppp: mention default ppp_nat="YES" for rc.conf

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243062

            Bug ID: 243062
           Summary: man ppp: mention default ppp_nat="YES" for rc.conf
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Manual Pages
          Assignee: bugs at FreeBSD.org
          Reporter: contact at evilham.com
                CC: doc at 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=44443

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, but
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-legacy-ipv4-networking-nat-implementing
(as of this bug report these are quite advanced drafts but require more
editing)

-- 
You are receiving this mail because:
You are on the CC list for the bug.