Failure to bond SRTLA - IPv6 issue?

[scyc314]

User has active cellular and wifi connections, bonding does not include the cellular connection and only the wifi connection will be used. Appears to occur only on T-Mobile and may be due to the cellular connection only being assigned an ipv6 ip.

If wifi is disabled, cellular quickly takes over. If wifi is re-enabled, bonding begins to work with cellular and wifi. (If wifi is disabled at the beginning of a stream and is enabled midstream, bonding begins to work with cellular and wifi.)

Bonding works properly when specifying the stream url as an IPv6 IP in the format of ####:####:####:####:####:####:####

Bonding works properly when specifying the stream url using a domain name in the format xyz.abc.com only if using the new "system" DNS strategy (domain name based url did work in earlier versions before srtla relay changes were made, I believe)

Log files attached:
Mob Test - Domain URL System DNS (WORKS).txt
Mob Test - Domain URL IPV4 DNS (DISABLE WIFI, REENABLE WIFI).txt
Mob Test - Domain URL IPv4+IPv6 DNS.txt
Mob Test - Domain URL IPv4 DNS.txt
Mob Test - IPv4 URL.txt
Mob Test - Domain URL IPV4+6 DNS (DISABLE WIFI, REENABLE WIFI).txt
Mob Test - IPv6 URL (WORKS).txt
Mob Test - Domain URL IPv6 DNS.txt

[arneeichhorn]

you could try the latest test flight version that contains a bonding fix, seems for me like your problems are a mix of the dns resolving issue and the bonding issue?

be11413

[eerimoq]

The fix is in Test Flight, so can install from there

[scyc314]

The fix appears to have resolved the issue. Using a domain name based URL works regardless of the dns lookup strategy.

I am also now able to use the ipv4 ip address based URL (ie, no dns lookup) without issue. I started using the domain based URL as that was the only way I could get bonding to work on T-Mobile in the past.

[eerimoq]

cool