Created attachment 226490 [details] 20210715-01-ports-comms-conserver-com.diff I've locally updated conserver-com to 8.2.6 to gain IPv6 support. I've not thoroughly tested the release though. The new changes (patch files) have been upstreamed as pull request: https://github.com/bstansell/conserver/pull/66 Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: Makefile modified: distinfo deleted: files/patch-conserver__group.c new file: files/patch-conserver__main.c new file: files/patch-conserver__readcfg.c deleted: files/patch-cutil.c
^Triage: .4 and .5 are bugfix release(s) with .5 incl a FreeBSD fix: MFH: 2020Q3 (bugfix release(s))
The IPv6 bits are not quite ready it seems from trying ocnserver in an ipv6-only setup without all in DNS.
(In reply to Bjoern A. Zeeb from comment #2) Turns out that was a jail ::1 vs. real IPv6 address bind/connect issue given classic jails do magic translating ::1. Seems I can connect to consoles.
Maintainer reset.
Approved by: lwhsu (ports) Bjoern, do you want to take the maintainership?
(In reply to Li-Wen Hsu from comment #5) I am not a ports committer. I am also not sure what the current state of the port or upstream is these days. I can go and have a look but given I reported this and it is assigned to me I wonder how this was supposed to ever move forward?
Port is at 8.2.7 already.