Can traceroute detect a load balancer sitting between an application server and a database? After running a traceroute from application server to database I only received one hop. The hop was the destination database
Hi I have strange behavior of a traceroute to one of my public IP's In one of a line I have multiple hostnames with timing like in the folowing example, on the 5th line
traceroute to dns.abc.com (111.222.333.444), 30 hops max, 60 byte packets
1 router.example.com (192.168.0.1) 1.137 ms 0.712 ms 0.641 ms
2 * * *
3 * * *
4 212.2.102.1 (212.2.102.1) 39.234 ms 38.799 ms 38.762 ms
5 wawbal-i1-BE11.plusnet.pl (212.2.102.189) 45.306 ms pozche-i2-BE15.plusnet.pl (212.2.102.214) 38.787 ms 38.667 ms
6 wawbal-i2-BE12.plusnet.pl (212.2.102.210) 45.495 ms 35.135 ms 34.872 ms
7 xe-2-0-0-48.r5.isp-rs.thinx.atman.pl (212.91.0.13) 34.402 ms 39.241 ms 40.592 ms
......
has anyone seen anything like this before ? What is it means ?
Much thanks for an answer. M
If nothing block the traffic, traceroute normally ends with the destination IP as the last hop. (10.1.1.10 in this case)
Normal traceroute would be like this.
user@linux:~$ traceroute 10.1.1.10
traceroute to 10.1.1.10 (10.1.1.10), 30 hops max, 60 byte packets
1 10.2.8.2 (10.2.8.2) 0.572 ms 0.692 ms 0.837 ms
2 10.1.9.50 (10.1.9.50) 202.638 ms 10.1.9.78 (10.1.9.78) 202.547 ms 10.1.9.50 (10.1.9.50) 202.139 ms
3 10.1.4.9 (10.1.4.9) 202.508 ms 202.483 ms 10.1.4.13 (10.1.4.13) 204.149 ms
4 10.1.1.10 (10.1.1.10) 202.133 ms 202.100 ms 202.692 ms
user@linux:~$
Recently, I encountered an issue whereby there was an additional hop (10.1.1.9) in the traceroute output (look at hop 5).
Source IP Address: 10.2.8.8
user@linux:~$ ifconfig | head -2
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.2.8.8 netmask 255.255.255.0 broadcast 10.2.8.255
user@linux:~$
Destination IP Address: 10.1.1.10
Additional hop: 10.1.1.9 ???
user@linux:~$ traceroute 10.1.1.10
traceroute to 10.1.1.10 (10.1.1.10), 30 hops max, 60 byte packets
1 10.2.8.2 (10.2.8.2) 0.572 ms 0.692 ms 0.837 ms
2 10.1.9.50 (10.1.9.50) 202.638 ms 10.1.9.78 (10.1.9.78) 202.547 ms 10.1.9.50 (10.1.9.50) 202.139 ms
3 10.1.4.9 (10.1.4.9) 202.508 ms 202.483 ms 10.1.4.13 (10.1.4.13) 204.149 ms
4 10.1.1.10 (10.1.1.10) 202.133 ms 202.100 ms 202.692 ms
5 10.1.1.9 (10.1.1.9) 6201.720 ms !H * *
user@linux:~$
Also, if you look at hop 2 and 3, there is additional IP Addresses (10.1.9.78 & 10.1.9.50)
Why did this happen? I've never seen anything like this before.
Was this because of the server configuration?
I understand how a client can trace a route to a server (using traceroute, or tracert). But is there a way for a server to trace a route to a client?
The problem is that I have a group of internet users who live in a remote area and they are complaining that their internet access is slow. I am planning to build some software that allows them to run a download test easily, then store the results. Once we have collected a reasonable amount of data we will hopefully be able to find a pattern.
In conjunction with the download data it would be great to have traceroute data. I can't see how I could initiate this from the client without writing some client software, which is something I don't want to do. Thus I am trying to find a mechanism which collects route information but is initiated by the server.
My preference would be to work with a linux server.
I m using RHEL 6.5 and eth0 interaface
Interface Ip is 100.x.x.x and when i traceroute to 100.x.x.x it showing one hop that too ip address of interface itself.
For eg traceroute to 100.65.111.14 from 100.66.28.75 gives 100.66.28.75 3000ms 3214ms 3245ms It quits after this.
But when I use other than 100.x.x.x segment traceroute is morethan one hop.
Moreover i able to ping default gateway but unable to traceroute ..