Tracroute from compute node instance to physical system?

asked 2016-03-29 14:10:20 -0600

BobH gravatar image

updated 2016-03-29 14:13:33 -0600

I get this when using traceroute from my compute node, which is in a virtual machine on the physical server with address 10.32.201.185

traceroute 10.32.201.185
traceroute to 10.32.201.185 (10.32.201.185), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * 10.32.201.185 (10.32.201.185)  0.248 ms  0.231 ms

ping shows:

ping 10.32.201.185
PING 10.32.201.185 (10.32.201.185) 56(84) bytes of data.
64 bytes from 10.32.201.185: icmp_seq=1 ttl=64 time=0.085 ms
64 bytes from 10.32.201.185: icmp_seq=2 ttl=64 time=0.093 ms
64 bytes from 10.32.201.185: icmp_seq=3 ttl=64 time=0.124 ms
64 bytes from 10.32.201.185: icmp_seq=4 ttl=64 time=0.078 ms
64 bytes from 10.32.201.185: icmp_seq=5 ttl=64 time=0.139 ms
64 bytes from 10.32.201.185: icmp_seq=6 ttl=64 time=0.132 ms

If it was some security rule thing, i'd expect traceroute to never work. Is this expected? Things seem to work fine, it's just traceroute a bit odd.

edit retag flag offensive close merge delete

Comments

I would not expect traceroute understand OVS bridging ( just guessing ).

dbaxps gravatar imagedbaxps ( 2016-03-29 14:37:48 -0600 )edit

this particular setup is linuxbridge, maybe same reason....

BobH gravatar imageBobH ( 2016-03-29 14:48:16 -0600 )edit