Date: Tue, 18 Jul 2017 12:52:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219622] [NEW PORT] net/ndproxy: Implementation of IPv6 Neighbor Discovery proxy Message-ID: <bug-219622-13-RjhTKYb1pe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219622-13@https.bugs.freebsd.org/bugzilla/> References: <bug-219622-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219622 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbsd.bugzilla@fenyo.net Keywords| |feature, needs-qa Flags| |maintainer-feedback?(fbsd.b | |ugzilla@fenyo.net) Summary|New port: net/ndproxy The |[NEW PORT] net/ndproxy: |ndproxy(4) kernel module |Implementation of IPv6 |implements IPv6 Neighbor |Neighbor Discovery proxy |Discovery proxying with | |many options to handle | |several use-cases. | Status|New |Open --- Comment #6 from Kubilay Kocak <koobs@FreeBSD.org> --- Thank you for your contribution Alexandre, It's quite normal for there to be a delay/queue associated with new ports, = so hang tight :) One thing I can suggest that may assist/prompt action is to confirm that th= is port passes QA. I see that you have run portlint, but further testing with poudriere can identify major issues associated with ports that portlint can= t. For more information and instructions, see: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.= html --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219622-13-RjhTKYb1pe>