Comet fails rapidly to reach some specific capsules. The failure is quite reliable. I get no issue accessing the capsules with Bebop on the desktop.
I get the following error (snipped host and addresses):
failed to connect to <host>/<dest-ipv6> (port 1965) from /<src-ipv6> (port 40993) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
(the 10s timeout is misleading, it fails much more rapidly that that)
An hypothesis is there is no IPv6 connectivity to these capsule, which Android tends to mostly use whereas on the desktop Debian is like eh IPv4 is fine let's use this. Running nmap -p 1965 host shows an open port whereas nmap -p 1965 host -6 shows a closed port. If my suspicion is true, then either Comet should be able to fallback to IPv4 communication but I do not know how achievable that is (do all phones having dual IP stacks? is it doable from the API?), or capsules authors should know that missing IPv6 connectivity means that mobile users will have issues to reach them.
BUT Lagrange on Android can reach those capsules just fine, so what's going on?!
Comet fails rapidly to reach some specific capsules. The failure is quite reliable. I get no issue accessing the capsules with Bebop on the desktop.
I get the following error (snipped host and addresses):
```
failed to connect to <host>/<dest-ipv6> (port 1965) from /<src-ipv6> (port 40993) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
```
(the 10s timeout is misleading, it fails much more rapidly that that)
An hypothesis is there is no IPv6 connectivity to these capsule, which Android tends to mostly use whereas on the desktop Debian is like eh IPv4 is fine let's use this. Running `nmap -p 1965 host` shows an open port whereas `nmap -p 1965 host -6` shows a closed port. If my suspicion is true, then either Comet should be able to fallback to IPv4 communication but I do not know how achievable that is (do all phones having dual IP stacks? is it doable from the API?), or capsules authors should know that missing IPv6 connectivity means that mobile users will have issues to reach them.
BUT Lagrange on Android can reach those capsules just fine, so what's going on?!
phoebos (gemini://bvnf.space) confirmed that their system had an issue with IPv6 and once fixed, Comet could connect just fine, so it most likely is an IPv6 issue.
Now it should be decided whether:
Comet should print a better error message if possible.
Comet should attempt reaching those capsules through IPv4 after a first failure.
Comet should not do anything.
phoebos (gemini://bvnf.space) confirmed that their system had an issue with IPv6 and once fixed, Comet could connect just fine, so it most likely is an IPv6 issue.
Now it should be decided whether:
- Comet should print a better error message if possible.
- Comet should attempt reaching those capsules through IPv4 after a first failure.
- Comet should not do anything.
Comet fails rapidly to reach some specific capsules. The failure is quite reliable. I get no issue accessing the capsules with Bebop on the desktop.
I get the following error (snipped host and addresses):
(the 10s timeout is misleading, it fails much more rapidly that that)
An hypothesis is there is no IPv6 connectivity to these capsule, which Android tends to mostly use whereas on the desktop Debian is like eh IPv4 is fine let's use this. Running
nmap -p 1965 hostshows an open port whereasnmap -p 1965 host -6shows a closed port. If my suspicion is true, then either Comet should be able to fallback to IPv4 communication but I do not know how achievable that is (do all phones having dual IP stacks? is it doable from the API?), or capsules authors should know that missing IPv6 connectivity means that mobile users will have issues to reach them.BUT Lagrange on Android can reach those capsules just fine, so what's going on?!
phoebos (gemini://bvnf.space) confirmed that their system had an issue with IPv6 and once fixed, Comet could connect just fine, so it most likely is an IPv6 issue.
Now it should be decided whether: