Summary: | net/socat: IPv6 for OPENSSL-CONNECT no longer works with 1.8.0.0_1 | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Kolbjørn Barmen <freebsd> |
Component: | Individual Port(s) | Assignee: | Emanuel Haupt <ehaupt> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Some People | CC: | freebsd |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ehaupt) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Kolbjørn Barmen
2024-02-27 02:45:59 UTC
This looks related: https://cgit.freebsd.org/ports/commit/net/socat/Makefile?id=4c6bb66915d405ad49d3d843c6fdd2857e9371c8 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275653 Can you try adding the -6 argument? *** This bug has been marked as a duplicate of bug 275653 *** (In reply to Emanuel Haupt from comment #1) I can confirm that using -6 works, and more I can confirm that setting SOCAT_DEFAULT_LISTEN_IP=0 (or 6) also works (which doesn't appear so intuitive, I'm not using socat to listen, but to connect). What I find "astonihing" is that default behaviour now to never even try IPv6, even when target host resolves _only_ AAAA-record. I recommend addressing the concern by reaching out directly to the upstream project. You can do so by contacting them at socat@dest-unreach.org or visiting their website at http://www.dest-unreach.org/socat/ for more information. |