Re: how to determine peeraddr from quic connection

Great! many thanks!

Matt Caswell schrieb am Freitag, 26. September 2025 um 14:09:37 UTC+2:

> I created a feature request for this here:
>
> https://github.com/openssl/openssl/issues/28674
>
> Matt
>
> On Fri, 26 Sept 2025 at 12:57, gustafn <[email protected]> wrote:
>
>>
>> Such a call will be important for all, who a trying to implement a 
>> full-featured HTTP/3 web server (e.g. access logs). 
>>
>> Maybe interesting for others: I've tried for now different alternatives. 
>> The approach with recvfrom(.... MSG_PEEK...) does not work at all, it 
>> returns an empty sockaddr when i call it before SSL_accept_connection() 
>> and in pending conn callback. Similarly, my attempts to 
>> use SSL_get_rbio(ssl) and to get the peer from the bio failed (always NULL 
>> addresses) for these call sites. Maybe an approach creating my own UDP 
>> listening socket and plumbing the data to OpenSSL using BIO_s_dgram_pair 
>> might help, although, this looks like a crazy overhead to me just to get 
>> the peer addr.
>>
>> In case, someone has more ideas, please let me know.
>> Alexandr Nedvedicky schrieb am Donnerstag, 25. September 2025 um 18:40:37 
>> UTC+2:
>>
>>> 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][email protected] 
>>> > 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:[email protected] 
>>> > 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 
>>>
>>> -- 
>> 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 [email protected]
>> To view this discussion visit 
>> https://groups.google.com/a/openssl.org/d/msgid/openssl-users/1dc1b012-76a4-4170-9849-12c7c3ef1245n%40openssl.org 
>> <https://groups.google.com/a/openssl.org/d/msgid/openssl-users/1dc1b012-76a4-4170-9849-12c7c3ef1245n%40openssl.org?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/e3eae05c-0ef7-4c51-90a5-2f212e1d38f1n%40openssl.org.