Remove $FreeBSD$: one-line nroff pattern

Remove /^\.\\"\s*\$FreeBSD\$$\n/

divert(4): maintain own cb database and stop using inpcb KPI

Here go cons of using inpcb for divert:
- divert(4) uses only 16 bits (local port) out of struct inpcb,
which is 424 bytes today.
- The

divert(4): maintain own cb database and stop using inpcb KPI

Here go cons of using inpcb for divert:
- divert(4) uses only 16 bits (local port) out of struct inpcb,
which is 424 bytes today.
- The inpcb KPI isn't able to provide hashing for divert(4),
thus it uses global inpcb list for lookups.
- divert(4) uses INET-specific part of the KPI, making INET
a requirement for IPDIVERT.

Maintain our own very simple hash lookup database instead. It
has mutex protection for write and epoch protection for lookups.
Since now so->so_pcb no longer points to struct inpcb, don't
initialize protosw methods to methods that belong to PF_INET.
Also, drop support for setting options on a divert socket. My
review of software in base and ports confirms that this has no
use and unlikely worked before.

Differential revision: https://reviews.freebsd.org/D36382

show more ...

divert: declare PF_DIVERT domain and stop abusing PF_INET

The divert(4) is not a protocol of IPv4. It is a socket to
intercept packets from ipfw(4) to userland and re-inject them
back. It can dive

divert: declare PF_DIVERT domain and stop abusing PF_INET

The divert(4) is not a protocol of IPv4. It is a socket to
intercept packets from ipfw(4) to userland and re-inject them
back. It can divert and re-inject IPv4 and IPv6 packets today,
but potentially it is not limited to these two protocols. The
IPPROTO_DIVERT does not belong to known IP protocols, it
doesn't even fit into u_char. I guess, the implementation of
divert(4) was done the way it is done basically because it was
easier to do it this way, back when protocols for sockets were
intertwined with IP protocols and domains were statically
compiled in.

Moving divert(4) out of inetsw accomplished two important things:

1) IPDIVERT is getting much closer to be not dependent on INET.
This will be finalized in following changes.
2) Now divert socket no longer aliases with raw IPv4 socket.
Domain/proto selection code won't need a hack for SOCK_RAW and
multiple entries in inetsw implementing different flavors of
raw socket can merge into one without requirement of raw IPv4
being the last member of dom_protosw.

Differential revision: https://reviews.freebsd.org/D36379

show more ...

IFC @r269962

Submitted by: Anish Gupta (akgupt3@gmail.com)

Merge head from 7/28

Sync to HEAD@r269943.

use .Mt to mark up email addresses consistently (final part)

PR: 191174
Submitted by: Franco Fichtner <franco at lastsummer.de>

IFC @ r238370

Merge head r233826 through r236168.

MFC

mdoc: Avoid playing tricks with Ns: If Nm is present in the SYNOPSIS section,
it will be output on its own line. Ns cancels this effect however. This change
is also consistent with the rest of our ma

mdoc: Avoid playing tricks with Ns: If Nm is present in the SYNOPSIS section,
it will be output on its own line. Ns cancels this effect however. This change
is also consistent with the rest of our manual pages.

show more ...

- move steps describing how to gain ipdivert support to SYNOPSIS and
follow the style of other section 4 manual pages
- add ipfw(4) to SEE ALSO section

Reviewed by: ru
Approved by: trhodes (mentor

- move steps describing how to gain ipdivert support to SYNOPSIS and
follow the style of other section 4 manual pages
- add ipfw(4) to SEE ALSO section

Reviewed by: ru
Approved by: trhodes (mentor), keramida (mentor)

show more ...

Expand contractions.

Expand *n't contractions.

Sort sections.

Scheduled mdoc(7) sweep.

Bump .Dd

Reminded by: ru

Note that send(2) is no longer applicable to divert(4) sockets.

Noticed by: Dmitry Dvoinikov
Wording by: cperciva
MFC after: 3 days

Refuse to unload the ipdivert module unless the 'force' flag is given to kldunload.

Reflect the fact that IPDIVERT is a loadable module in the divert(4) and ipfw(8)
man pages.

Be explicit that packets passed from a 'ipfw tee' action will not be reassembled.

Prodded by: ru

Mechanically kill hard sentence breaks and double whitespaces.

Correct to match reality regarding interface names.

PR: 51006
Submitted by: "Dmitry Pryanishnikov" <dmitry@atlantis.dp.ua>
mdoc clue by: "Simon L. Nielsen" <simon@nitro.dk>
MFC after: 10 days

Hiten's patchset for section four manpages, slightly edited by me.

Fix syntax error.

mdoc(7) police: Use the new .In macro for #include statements.