net/ndproxy 3.3.1501000

net/ndproxy: Update 3.2 => 3.3, fix build on 15+

Commit log:
https://github.com/AlexandreFenyo/ndproxy/compare/v3.2...v3.3

Improve port:
- Add patch with fix build on 15+.
- Replace PORTVERSION with DISTVERSION.
- Add option DOCS.
- Fix warnings from portclippy.

PR:		291782
Approved by:	Alexandre Fenyo <fbsd.bugzilla@fenyo.net> (maintainer, implicit - inactive since 2019)
Co-authored-by:	David Hauweele <david@hauweele.net>

net/ndproxy: Mark as broken on FreeBSD 15 and 16

ndpacket.c:186:46: error: incomplete definition of type 'struct ifnet'

net/ndproxy: Moved man to share/man

Approved by:    portmgr (blanket)

net/ndproxy: fix build on FreeBSD kernel >= 14

Adding support for pfil version 2 interface.
Patch already submitted upstream as pull request:
https://github.com/AlexandreFenyo/ndproxy/pull/6

PR:		275884
Reported by:	Lorenzo Zolfanelli <dev@zolfa.nl>

net/ndproxy: Mark BROKEN on FreeBSD 14

Fails to build with no member named 'pa_func' in 'struct pfil_hook_args'

pa_func routine has been removed from base.

Approved by:	portmgr (blanket)
Sponsored by:	The FreeBSD Foundation

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

One more small cleanup, forgotten yesterday. Reported by:	lwhsu

all: Remove all other $FreeBSD keywords.

Remove # $FreeBSD$ from Makefiles.

Convert to UCL & cleanup pkg-message (categories n)

(and missed 3 missed files from previous categories.)

net/ndproxy: add -Wno-error=strict-prototypes to CFLAGS when using GCC

This is needed to fix build:
ndproxy.c:51: function declaration isn't a prototype

PR:		237296
Approved by:	fbsd.bugzilla@fenyo.net (maintainer), mat (mentor)
Differential Revision:	https://reviews.freebsd.org/D20013

net/ndproxy: Fix USE_GITHUB usage

net/ndproxy: Update to 3.2

This release contains fixes for API changes to pfil hooks in CURRENT

PR:		235864
Submitted by:	maintainer

Mark ports broken on mips64 that are already broken on powerpc64.  In most cases, the failure mode is the same.  Also, mark them broken on mips when necessary.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)

Mark ports broken on powerpc64, categories g-n.

While here, pet portlint and do some other cleanup.

Approved by:	portmgr (tier-2 blanket)

The ndproxy(4) kernel module implements IPv6 Neighbor Discovery proxying with many options to handle several use-cases.

It replies to a neighbor solicitation with a specific neighbor
advertisement, in order to let the PE uplink router send further
packets to a CPE downlink router, that may or may not be the same
node that the one which runs ndproxy.

The main difference with the ndp(8) command-line tool is that, with
ndproxy(4), the host running ndp can be used only to redirect
packets to another IPv6 internal router, for instance a dedicated
one with hardware support of IPv6 routing processes.

WWW: http://www.fenyo.net/newweb/ndproxy.html

PR:		219622
Submitted by:	Alexandre Fenyo (maintainer)
Reviewed by:	matthew (mentor), mat
Approved by:	matthew (mentor)
Differential Revision:	https://reviews.freebsd.org/D11892