Hi,
Already since some time my Raspberry Pi 4 is not able to make https
requests over IPv6:
$ curl -6 http://heise.de
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a
href="https://www.heise.de/">here</a>.</p>
</body></html>
$ curl -6 https://heise.de
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to
heise.de:443
I noticed this issue already like a month ago, when "zypper ref" fails
with a "Connection reset by peer" error message. The rest of the IPv6
network works fine, I'm connecting via ssh to the Raspberry Pi using
it's IPv6 address and also a ping works nicely.
$ ping6 heise.de
PING heise.de(redirector.heise.de (2a02:2e0:3fe:1001:302::)) 56
data bytes
64 bytes from redirector.heise.de (2a02:2e0:3fe:1001:302::):
icmp_seq=1 ttl=56 time=14.1 ms
64 bytes from redirector.heise.de (2a02:2e0:3fe:1001:302::):
icmp_seq=2 ttl=56 time=13.3 ms
64 bytes from redirector.heise.de (2a02:2e0:3fe:1001:302::):
icmp_seq=3 ttl=56 time=13.4 ms
^C
--- heise.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 13.315/13.640/14.151/0.377 ms
I'm attaching the strace of `curl -6 https://heise.de` to this email as
well. It is interesting, as it appears to be able to fetch the SSL
Certificate, but then ppoll fails with a series of timeouts.
Could be that it's just a stupid misconfiguration on my side, but I'm
unable to find the culprit.
## System configuration
* Raspberry Pi 4, 4 GB + 8 GB model (tried on both)
* openSUSE Leap 15.2
* Network bridge br0 with eth0
* Wifi is not used
* Native IPv6 prefix in house, works fine with the rest of the network
I'm using wicked, a stable ethernet connection and have configured eth0
to be in a network bridge within YaST. The interface configuration
looks like the following:
2: eth0: