Hot answers tagged traceroute
From man 1 traceroute: -m max_ttl Specifies the maximum number of hops (max time-to-live value) traceroute will probe. The default is 30.
When some location is further than 30 hops, it probably means simply that last hops does not replies when TTL exceeds. Unless, it's a story: $ traceroute -m100 188.8.131.52 traceroute to 184.108.40.206 (220.127.116.11), 100 hops max, 52 byte packets (...) 14 episode.iv (18.104.22.168) 173.387 ms 171.638 ms 171.201 ms 15 a.new.hope (22.214.171.124) ...
A likely reason for the difference is that by default Window's tracert uses ICMP, whereas Linux traceroute defaults to UDP. Using the -I option for traceroute should produce the same results as tracert: traceroute -w 10 -I google.it From the traceroute documentation: In the modern network environment the traditional traceroute methods can not be ...
The asterisks you're seeing are servers that your packets are being routed through whom are timing out (5.0+ seconds) and so traceroute defaults to printing the *. NOTE: There's even a warning about this in the traceroute man page. excerpt In the modern network environment the traditional traceroute methods can not be always applicable, because of ...
In /etc/ssh/sshd_config make sure the following is uncommented: AllowTCPForwarding yes Double check your syntax too: $ ssh -N -L [local_port]:[endpoint]:[remote_port] [user]@[host] The error you're seeing is a terribly confusing error that is thrown when a forwarded ssh connection simply can't connect.
From your output, you are not able to reach the destination. The * denotes a timeout. traceroute command shows the path to your destination. packets send to will pass through the routers and you receive a response obeying the time to live (TTL) value for each packets. the * denotes a timeout as a response from the intermediate routers that says the packet ...
When you echo $a, the shell does "word splitting" and all significant whitespace is lost. Try echo "$a" with double quotes. Quoting will also ensure filename expansion does not occur. See http://www.gnu.org/software/bash/manual/bashref.html#Shell-Expansions
There is nothing built-in to IP that lets you do a reverse traceroute, that is, a traceroute from some remote server back to you. That is why network administrators often set up public looking glasses for other network administrators to use. These looking glasses were historically telnet-based interfaces but nowadays are usually available through web ...
The stars mean a device in the chain didn't respond to your ICMP / UDP packet. That can be a router, firewall or a host configured not to respond. They're usually only interesting if you get them mixed in with responses, e.g. 21 * 10 ms * which suggests the device at or around hop 21 is intermittently responding or is intermittently available. Whether ...
It's not just something you can do with pf. The example you cite mentions using VRFs. On OpenBSD you need to create multiple routing domains (rdomains) using the rtable command. You'll need to build a series of routing tables and virtual interfaces so that each hop jumps to a new table. In order to do the Star Wars crawl you'll also need to either edit your ...
You did read the man page, right? -i interface, --interface=interface Specifies the interface through which traceroute should send packets. By default, the interface is selected according to the routing table.
Only top voted, non community-wiki answers of a minimum length are eligible