Issues connecting with Peers on Different Networks about p2pt HOT 8 OPEN

@subins2000 . I'll look into it on Kerala Vision to Kerala Vision and Kerala Vision to other providers as well.

from p2pt.

This problem with Keralavision has been reported before. I have no idea what's different on them. Either it's the problem of the modems they're giving to customers or it's something on the ISP infrastructure level. Same unexplainable issue with Asianet ISP too.

cc @akash-santhosh

from p2pt.

What bout IP Pools, I've heard Mobile operators use IP Pools with IPv6 addresses rather than IPv4 to accommodate the subscribers. Lemme look into this too... seems related to what I faced when using 3G Netsetter.

from p2pt.

IPv6 only devices can't connect to IPv4 and vice-versa. Maybe it's that issue.

Some things I found, but no conclusion yet

• https://groups.google.com/g/discuss-webrtc/c/qBuwkOI9jjk
• https://tools.ietf.org/id/draft-ietf-rtcweb-ip-handling-04.html
• https://bugs.chromium.org/p/webrtc/issues/detail?id=2831
• pion/webrtc#810 (comment)

from p2pt.

I did some trials ...and it turns out, what works right now are:

• Jio - Jio
• Keralavision-Keralavision
• Jio-Idea
• Idea-Idea

A random similarity seen are IPv4 - IPv4 and IPv6 - IPv6 works...but not between them.

from p2pt.

@elvistony that makes sense because of how UDP hole punching works

from p2pt.

although (generally) IPV6 addresses provide an IPv4 fallback just for this case, I'm not sure if this can be programmatically resolved

from p2pt.

There are devices which doesn't have that IPv4 fallback, those devices can't connect to other IPv4 devices. Yeah, I don't think we can solve this on our side. It's something on the physical-OS level which p2pt doesn't have a control of.

from p2pt.