Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opportunistic IPv4/IPv6 connection #915

Closed
quite opened this issue Mar 6, 2017 · 9 comments
Closed

Opportunistic IPv4/IPv6 connection #915

quite opened this issue Mar 6, 2017 · 9 comments

Comments

@quite
Copy link
Contributor

quite commented Mar 6, 2017

I had IPv6 connectivity loss on my server for a while, and noticed Profanity failing to connect at all. It would be great with some kind of googley eyes behaviour, probably for each and every one of the connections it tries to establish.

@kaffeekanne
Copy link
Contributor

The domain of my server is reachable via IPv4 and v6. However the xmpp service only listens on IPv4. Being configured like this i can not connect to my server with profanity. If connection through one method fails, the other should be tried as well. Other clients like mcabber and conversations had no problem.

My server admin was unaware about missing IPv6 connectivity and is going to fix it. On the other hand from 1000 clients nobody seemed to have an issue with that in 5 years 😅

@jubalh
Copy link
Member

jubalh commented Oct 15, 2019

@pasis can we do this?

@pasis
Copy link
Member

pasis commented Oct 15, 2019

yes, this is libstrophe issue, please, open ticket there to check all possible addresses until one succeeds. Now, libstrophe checks them one by one until one only starts connecting successfully. But this is not enough if port is closed on the remote side for a particular address family.

@pasis
Copy link
Member

pasis commented Oct 27, 2019

Does anyone know domain/address of such a server to check a solution? Where server runs only on IPv4, but address is resolved to both IPv4 and IPv6.

@Zash
Copy link
Contributor

Zash commented Jun 3, 2020

Bad XMPP has a few intentionally misconfigured hosts for testing against, including IPv4+IPv6 where one will not connect. The tests are however currently only for server-to-server connections, tests for clients are planned but not there yet. For socket-level connectivity testing this might still work, if you can change the SRV service name to xmpp-server instead of xmpp-client while testing.

@pasis
Copy link
Member

pasis commented Jun 3, 2020

@Zash This will help a lot, thanks!

@pasis
Copy link
Member

pasis commented Jun 22, 2023

The feature has been added to libstrophe master (strophe/libstrophe#221). Use latest sources or wait for the next libstrophe release.

@pasis pasis closed this as completed Jun 22, 2023
@jubalh
Copy link
Member

jubalh commented Jul 4, 2023

For future reference: users will need libstrophe > 0.12.2 (we maybe dont hard require this)

@jubalh jubalh added this to the next milestone Jul 27, 2023
jubalh added a commit that referenced this issue Aug 2, 2023
Among other things for:
* #915
* #1849
@jubalh
Copy link
Member

jubalh commented Aug 2, 2023

libstrophe 0.12.3 with the fix has been released. Profanity 0.14.0 will depend on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants