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

iTeamTalk cannot connect on T-mobile network in US #311

Closed
bear101 opened this Issue Jul 25, 2017 · 13 comments

Comments

Projects
None yet
5 participants
@bear101
Contributor

bear101 commented Jul 25, 2017

No description provided.

@Nick6489

This comment has been minimized.

Show comment
Hide comment
@Nick6489

Nick6489 Aug 3, 2017

@bear101 A few friends of mine, and I, tested this quite extensively. What we figured out is that T-Mobile uses some apparatus of its own to translate IPV4 addresses into IPV6. When connecting to a TeamTalk server hosted on an actual IPV6 network, TeamTalk exhibits the same behavior. It is our understanding from this test that TeamTalk does not yet support IPV6 on the iPhone?

Nick6489 commented Aug 3, 2017

@bear101 A few friends of mine, and I, tested this quite extensively. What we figured out is that T-Mobile uses some apparatus of its own to translate IPV4 addresses into IPV6. When connecting to a TeamTalk server hosted on an actual IPV6 network, TeamTalk exhibits the same behavior. It is our understanding from this test that TeamTalk does not yet support IPV6 on the iPhone?

@bear101

This comment has been minimized.

Show comment
Hide comment
@bear101

bear101 Aug 4, 2017

Contributor
Contributor

bear101 commented Aug 4, 2017

@bear101

This comment has been minimized.

Show comment
Hide comment
@bear101

bear101 Aug 7, 2017

Contributor
Contributor

bear101 commented Aug 7, 2017

@tech10

This comment has been minimized.

Show comment
Hide comment
@tech10

tech10 Aug 8, 2017

A friend of mine tested the test flight version of the client. The same result has occurred, no connection unless he's connecting through some VPN service like Private Internet Access. WIFI, of course, works fine. While having an IPV6 capable iOS or mobile client in general would be a good thing, it doesn't solve the issue. Other programs don't work correctly on T-Mobile, either, nor do non-standard ports for icecast or other audio/video streams. In my opinion, T-Mobile is blocking ports that are unused by the majority, in which case, no code within the application itself is likely to solve the problem. It would be on T-Mobile's side of things to correct, which they did for a few days until a carrier settings update, then returned to the prior behavior. This is what gives me the suspicion that T-Mobile is blocking ports, rather than it being an application issue.

tech10 commented Aug 8, 2017

A friend of mine tested the test flight version of the client. The same result has occurred, no connection unless he's connecting through some VPN service like Private Internet Access. WIFI, of course, works fine. While having an IPV6 capable iOS or mobile client in general would be a good thing, it doesn't solve the issue. Other programs don't work correctly on T-Mobile, either, nor do non-standard ports for icecast or other audio/video streams. In my opinion, T-Mobile is blocking ports that are unused by the majority, in which case, no code within the application itself is likely to solve the problem. It would be on T-Mobile's side of things to correct, which they did for a few days until a carrier settings update, then returned to the prior behavior. This is what gives me the suspicion that T-Mobile is blocking ports, rather than it being an application issue.

@OzancanKaratas

This comment has been minimized.

Show comment
Hide comment
@OzancanKaratas

OzancanKaratas Oct 15, 2017

Member

Use unlimited network access for the iOS app.

Member

OzancanKaratas commented Oct 15, 2017

Use unlimited network access for the iOS app.

@stickbear2015

This comment has been minimized.

Show comment
Hide comment
@stickbear2015

stickbear2015 Oct 30, 2017

I forgot this issue existed, latest build, still refuses to work.

stickbear2015 commented Oct 30, 2017

I forgot this issue existed, latest build, still refuses to work.

@tech10

This comment has been minimized.

Show comment
Hide comment
@tech10

tech10 Oct 30, 2017

I suspected that it wouldn't work myself, and a friend of mine, who uses T-Mobile, confirmed that enabling IPV6 didn't resolve the issue. While that's a good thing to have enabled anyway, I suspect that the issue is not within the application, but T-Mobile, who block the majority of non-standard ports, something most people probably wouldn't notice. The same friend told me he couldn't connect to internet streams on port 9000, while 8000 works. This, combine with TeamTalk being unable to connect unless using a VPN, leads me to my suspicions. Whatever the T-Mobile folks or testing says about requiring IPV6 in an application in order for it to properly work, is incorrect.

tech10 commented Oct 30, 2017

I suspected that it wouldn't work myself, and a friend of mine, who uses T-Mobile, confirmed that enabling IPV6 didn't resolve the issue. While that's a good thing to have enabled anyway, I suspect that the issue is not within the application, but T-Mobile, who block the majority of non-standard ports, something most people probably wouldn't notice. The same friend told me he couldn't connect to internet streams on port 9000, while 8000 works. This, combine with TeamTalk being unable to connect unless using a VPN, leads me to my suspicions. Whatever the T-Mobile folks or testing says about requiring IPV6 in an application in order for it to properly work, is incorrect.

@Nick6489

This comment has been minimized.

Show comment
Hide comment
@Nick6489

Nick6489 Apr 29, 2018

This has changed significantly.

IPV4 TeamTalk servers are still unable to connect using iTeamTalk, owing to what appears to be some kind of tunnel that T-Mobile is using to handle IPV4 traffic. Not something we can really do anything about.

However, IPV6 TeamTalk servers do work now. Tested on two T-Mobile iPhones using both the store build and the latest beta yesterday. This is why @QuinnEbert was asking for a build that would disable IPV6_V6ONLY in sockopts in this forum post

Nick6489 commented Apr 29, 2018

This has changed significantly.

IPV4 TeamTalk servers are still unable to connect using iTeamTalk, owing to what appears to be some kind of tunnel that T-Mobile is using to handle IPV4 traffic. Not something we can really do anything about.

However, IPV6 TeamTalk servers do work now. Tested on two T-Mobile iPhones using both the store build and the latest beta yesterday. This is why @QuinnEbert was asking for a build that would disable IPV6_V6ONLY in sockopts in this forum post

@bear101

This comment has been minimized.

Show comment
Hide comment
@bear101

bear101 May 7, 2018

Contributor

Are you able to connect to the IPv6 TeamTalk servers in the public server list?

Contributor

bear101 commented May 7, 2018

Are you able to connect to the IPv6 TeamTalk servers in the public server list?

@bear101

This comment has been minimized.

Show comment
Hide comment
Contributor

bear101 commented May 7, 2018

@Nick6489

This comment has been minimized.

Show comment
Hide comment
@Nick6489

Nick6489 May 8, 2018

Yes, I can connect to both US and UK IPV6 public TeamTalk servers from my T-Mobile iPhone 6S.

Nick6489 commented May 8, 2018

Yes, I can connect to both US and UK IPV6 public TeamTalk servers from my T-Mobile iPhone 6S.

@Nick6489

This comment has been minimized.

Show comment
Hide comment
@Nick6489

Nick6489 May 8, 2018

What I'm about to say doesn't change that I would like one TeamTalk server instance to bind to IPV4 and IPV6 on the same machine in future versions...But your latest beta on the app store suddenly allows me to connect to IPV4 TeamTalk servers through T-Mobile, despite their rather aggressive, ludacris IPV6 tunnel.

Nick6489 commented May 8, 2018

What I'm about to say doesn't change that I would like one TeamTalk server instance to bind to IPV4 and IPV6 on the same machine in future versions...But your latest beta on the app store suddenly allows me to connect to IPV4 TeamTalk servers through T-Mobile, despite their rather aggressive, ludacris IPV6 tunnel.

@bear101

This comment has been minimized.

Show comment
Hide comment
@bear101

bear101 May 8, 2018

Contributor

The v5.3.2.4928 betas you find here can bind to multiple IP-address:
http://bearware.dk/beta/

Contributor

bear101 commented May 8, 2018

The v5.3.2.4928 betas you find here can bind to multiple IP-address:
http://bearware.dk/beta/

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