It would help you to understand how traceroute works.
When you send an IP packet, there is a TTL field on that packet.
Every time the packet passes by a router, that TTL number is decremented.
When the number reaches 0 at some router, then the router will not forward the packet anymore, and send back a message to the originating computer (you) saying "hey this is router 123.123.123.123, I got your packet but TTL has reached 0 so I'm not forwarding it anymore".
This is a measure against infinite loops on the internet (the packet being forwarded in a loop forever).
Traceroute takes advantage of that, by sending a packet with TTL set to 1, then taking note who sent it back with the "TTL expired" message, then sending a packet with TTL = 2, etc, until the destination is reached.
So you're not really pinging 192.168.101.2. If you do a ping 192.168.101.2 it is very possible that the packet will go somewhere else totally. This device has probably two interfaces, one facing the internet, and one facing the internal network (you), on which they might be using a private address to spare IP addresses and use public addresses only when necessary, since it's a limited and possibly expensive resource.
ILIA_93 wrote
1) Why does pinging the next hop 77.42.129.13 router yields a ~30ms latency time! If this router is directly connected, what is causing this high latency.
And I'm still wondering what is this IP address that I see in my connection information...
Maybe that's the part that goes over the DSL network. What comes after that would be happening inside ogero's (hopefully) fiber backbone, and maybe international fiber. These things are very fast. I'm just guessing. Someone also said that Google have some kind of relay (or a proxy?) in Lebanon.
ILIA_93 wrote
2) I still don't understand how a fixed line connection can change its IP, if i'm connected to a router interface, let's say G0/1, how can it change IP every day! That doesn't make sense...
There is not such thing as "the IP of the connection". The IP address is related to an interface on a device, or a connection enpoint, so I cannot know clearly what you're talking about - I can only guess. I also don't know if 77.42.129.13 is your router or not. If you do "ipconfig /all" from the Window command line it would help us know. Anyway if that's the address of your "gateway" router, I don't know. Maybe the connection resets itself every night and you get assigned a new IP. If that's the address of a router further down the line, then routing is a variable thing and can change all the time, that's normal.