On Fri, 29 Jul 2022 11:16:09 +0200 Freek de Kruijf wrote:
Lately, due to another problem, I needed to investigate access problems and I used "sudo /sbin/traceroute -T -p x -m y -n dns_name". With -T you send TCP- SYN, -p x, x is the port you try to access and which has a listener, -m y limits the number of packets send, default is 30 and -n gives only IP addresses. This might give you some indication where it gets stuck.
On my system to Fritz!Box, via dns_name (global IP address), and back to my system, qq is the port forwarded to my port 22. $ sudo /sbin/traceroute -T -p qq -m 5 -n dns_name traceroute to dns_name (149.143.xx.yy), 5 hops max, 60 byte packets 1 192.168.178.1 0.603 ms 0.599 ms 0.630 ms 2 149.143.xx.yy 3.360 ms 3.321 ms 3.310 ms 3 149.143.xx.yy 5.029 ms 4.990 ms 5.025 ms As you see it gets a reply after 3 hops.
I'm not familiar with traceroute, but the result of the command you gave looks promising: bob@antikythera:~> sudo /sbin/traceroute -T -p 8197 -m 5 -n 51.148.xx.yy traceroute to 51.148.143.104 (51.148.143.104), 5 hops max, 60 byte packets 1 192.168.178.1 3.808 ms 3.772 ms 3.760 ms 2 51.148.xx.yy 6.360 ms 6.349 ms 6.337 ms 3 51.148.xx.yy 3004.722 ms !H 3004.711 ms !H 3004.696 ms !H 11:05 bob@antikythera:~> What does !H in the third line mean? The manpage doesn't mention it. -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/