Have you tried wireshark? You could inspect each & every packet leaving your network/devices ( and port numbers thereof ).
On Mon, Nov 22, 2021 at 4:00 PM Daryll Swer firstname.lastname@example.org wrote:
I agree with you and TCP Traceroute/Ping was the first thing on my mind, but unfortunately, I'm unable to determine the port number.
*--* Best Regards Daryll J. L. Swer Mobile Number: +91 700 592 0360 Website: daryllswer.com https://www.daryllswer.com/
On Mon, 22 Nov 2021 at 15:57, Rahul Makhija email@example.com wrote:
Ping is never the ideal tool to conclude if you're able to reach any given destination. Especially ICMP, this is quite common practice to block ICMP responses. I too am not able to "ping" the same host from AS135817 but Jio VoWIFI works just fine for me.
Maybe you want to do a tcp traceroute on the intended port number ( I'm not sure which port number is being used here for VoWiFi ). You'll surely find more useful information.
Thank you. Rahul
On Mon, Nov 22, 2021 at 3:39 PM Daryll Swer via INNOG firstname.lastname@example.org wrote:
Does anybody know who I can reach out to for the following issue?
My freshly allocated prefix (*22.214.171.124/24 http://126.96.36.199/24) *is unable to communicate with Reliance Jio's VoWiFi end-point on AS55836. And hence my Jio numbers are unable to work with VoWiFi when the source IPv4 address is originating from 188.8.131.52/24. [image: image.png]
*--* Best Regards Daryll J. L. Swer Mobile Number: +91 700 592 0360 Website: daryllswer.com https://mailtrack.io/trace/link/130c0a88b762eb0214b0b77a47d5197bfd294fe9?url=https%3A%2F%2Fwww.daryllswer.com&userId=2153471&signature=91e9e3a1e9058563 _______________________________________________ INNOG mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org