On Mon, 22 Nov 2021 at 16:08, Rahul Makhija <rahul.m@estointernet.in> wrote:
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 <contact@daryllswer.com> wrote:Hi Rahul
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.On Mon, 22 Nov 2021 at 15:57, Rahul Makhija <rahul.m@estointernet.in> wrote:Hi Daryll,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.RahulOn Mon, Nov 22, 2021 at 3:39 PM Daryll Swer via INNOG <innog@innog.net> wrote:_______________________________________________Hi Folks
Does anybody know who I can reach out to for the following issue?
My freshly allocated prefix (103.176.189.0/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 103.176.189.0/24.
INNOG mailing list -- innog@innog.net
To unsubscribe send an email to innog-leave@innog.net
