Hello,
I'm afraid you are right. There is currently no way to find out
remote peer's address for QUIC connection.
> Â Â Â int SSL_get_peer_addr(SSL *ssl, BIO_ADDR *peer_addr);
I think SSL_get_peer_addr() above would be the OpenSSL way
to implement it.
thanks and
regards
sashan
On Thu, Sep 25, 2025 at 09:01:02AM -0700, gustafn wrote:
> when accepting a new quic connectionÂ
> Â Â Â Â SSL Â Â Â Â Â Â *conn =
> SSL_accept_connection(listener_ssl, 0);
> how can i determine the peer address (sockaddr) for conn?Â
> It would be nice to have something likeÂ
> Â Â Â int SSL_get_peer_addr(SSL *ssl,Â
>
>         struct sockaddr *restrict addr, Â
>
> Â Â Â Â Â Â Â Â socklen_t *restrict addrlen);
> or
> Â Â Â int SSL_get_peer_addr(SSL *ssl, BIO_ADDR *peer_addr);
> using recvfrom(.... MSG_PEEK...) can't be the solution.
> I have the feeling, i have missed something essential in the
> documentation
> All the best -g
>
> --
> You received this message because you are subscribed to the Google
> Groups "openssl-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [1]
openssl-user...@openssl.org.
> To view this discussion visit
> [2]
https://groups.google.com/a/openssl.org/d/msgid/openssl-users/9827cf
> 3a-fae0-4b13-af8c-7fc26d2fed5cn%
40openssl.org.
>
> References
>
> 1. mailto:
openssl-user...@openssl.org
> 2.
https://groups.google.com/a/openssl.org/d/msgid/openssl-users/9827cf3a-fae0-4b13-af8c-7fc26d2fed5cn%40openssl.org?utm_medium=email&utm_source=footer