Saltar al contenido

T-Mobile Users Can't Connect

0

Users from T-Mobile eg 172.56.249.x and 172.56.25.x can't connect to my application on port 1001 with UDP. My public IP is 3.213.214.x and private IP is 172.26.0.x. All other users can connect fine, the problem is only with T-Mobile users. What should I do?

preguntada hace 6 meses151 visualizaciones
2 Respuestas
0

Given that your issues is with T-Mobile users only and not with users on other networks the problem is (most probably) somewhere in the T-Mobile network. You'll need to contact them and see if they are blocking your IP address for some reason. Note that they might not just be blocking your IP address - they may have decided to block (say) 3.213.214.0/24 and you're just a side-effect of that.

I know it's disruptive but you could try using a different Elastic IP address which is not in the same range and see if that helps. Probably worthwhile setting up a test system on a different Elastic IP and see if the T-Mobile users have an issue with that.

AWS
EXPERTO
respondido hace 6 meses
  • They said the IP isn't blocked. The problem is only from users with IP ranges from 172.56.x.x

0

I have seen this before when a VPC is configured with the same CIDR range as someones public range and the traffic will never return because of a asymetric routing issue. Some have mistaken and setup 172.X.X.X/8 as a 255.0.0.0 previously.

Please can you confirm your VPC CIDR Range?

EXPERTO
respondido hace 6 meses
  • I'm using Lightsail, on VPC I see 172.31.0.0/16 as IPv4 CIDR. My VPC peering is already off from Lightsail

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.