IPv6 testing feedback

Z

Zuldritch

Active Member
Joined
Mar 19, 2009
Messages
54
Reaction score
18
Hi,

Just some feedback on when I'm testing IPv6 over OpenServe.

Today I hit a significant blocker which has forced me to disable IPv6. When in a Microsoft Teams meeting I can't start or stop meeting recordings, it doesn't show an error, it just never actually starts the recording. When I disable IPv6 in Windows 11 advanced network adapter options it works fine again.

I normally use the Microsoft Teams desktop app, but just to test I tried using https://teams.microsoft.com/v2/ and when I'm running IPv6 I can't join meetings at all, it just waits forever.

For now I'll have to turn off IPv6 until we work out what's going on here.

Otherwise, it feels like some initial connections to websites are a little slower, I'm not sure if the IPv6 DNS resolution is slower, or perhaps my computer first tries IPv6 connections, gives up and then falls back to IPv4.

I've also occasionally had git push errors to https://github.com/ (which doesn't support IPv6) when using TortoiseGit (something to effect of "unable to establish connection"), but if I retry, or visit https://github.com/ in my browser first, then the error goes away.
 
Zuldritch said:
Hi,

Just some feedback on when I'm testing IPv6 over OpenServe.

Today I hit a significant blocker which has forced me to disable IPv6. When in a Microsoft Teams meeting I can't start or stop meeting recordings, it doesn't show an error, it just never actually starts the recording. When I disable IPv6 in Windows 11 advanced network adapter options it works fine again.

I normally use the Microsoft Teams desktop app, but just to test I tried using https://teams.microsoft.com/v2/ and when I'm running IPv6 I can't join meetings at all, it just waits forever.

For now I'll have to turn off IPv6 until we work out what's going on here.

Otherwise, it feels like some initial connections to websites are a little slower, I'm not sure if the IPv6 DNS resolution is slower, or perhaps my computer first tries IPv6 connections, gives up and then falls back to IPv4.

I've also occasionally had git push errors to https://github.com/ (which doesn't support IPv6) when using TortoiseGit (something to effect of "unable to establish connection"), but if I retry, or visit https://github.com/ in my browser first, then the error goes away.
Click to expand...
Hi, thanks for the feedback. We are actually busy assisting with this issue on the main thread as well.
Currently, we have reached out to Fastly regarding Github, and Akamai regarding Nvidia, I will mention to the team regarding the Teams issue you mentioned, as I'm not aware of issues on that front.
 
The Teams issue could be MTU related perhaps, are you able to try lowering your MTU to see if the teams issuepersists? Perhaps try 1400 and below

Via

Cool LG

Cool LG
lg.cisp.co.za
PING teams.microsoft.com(2603:1063:27:2::14 (2603:1063:27:2::14)) 56 data bytes
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=1 ttl=52 time=0.754 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=2 ttl=52 time=0.651 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=3 ttl=52 time=0.645 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=4 ttl=52 time=0.635 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=5 ttl=52 time=0.624 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=6 ttl=52 time=0.629 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=7 ttl=52 time=0.598 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=8 ttl=52 time=0.653 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=9 ttl=52 time=0.733 ms
64 bytes from 2603:1063:27:2::14 (2603:1063:27:2::14): icmp_seq=10 ttl=52 time=0.633 ms

--- teams.microsoft.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 18ms
rtt min/avg/max/mdev = 0.598/0.655/0.754/0.046 ms, ipg/ewma 2.001/0.680 ms

Reset
 
I had already thought it would be worth trying to lower MTU and temporarily set it to 1300 and then re-tested now with 1400 MTU, still no joy. I also turned off my personal firewall and added a rule on my pfSense box to allow all IPv6 traffic through, also with no effect.

If you want to test from your own browser, you can use the link I've PM'ed you. Choose the option to continue on your browser, enter any name and after pressing "Join Now", it should show "Connecting..." for a second or so and then the following:

1737488417576.png

Instead it gets stuck connecting:
1737488632793.png

And after a while the following:

1737488668820.png
 
Zuldritch said:
I had already thought it would be worth trying to lower MTU and temporarily set it to 1300 and then re-tested now with 1400 MTU, still no joy. I also turned off my personal firewall and added a rule on my pfSense box to allow all IPv6 traffic through, also with no effect.

If you want to test from your own browser, you can use the link I've PM'ed you. Choose the option to continue on your browser, enter any name and after pressing "Join Now", it should show "Connecting..." for a second or so and then the following:

View attachment 1789974

Instead it gets stuck connecting:
View attachment 1789976

And after a while the following:

View attachment 1789977
Click to expand...
Thank you for the additional information. Will share it with the team to test , as I don't have IPV6 available as yet.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter