Hi Sebastian, maybe due to load-sharing 10.1.66.51 takes other path back than 10.1.66.84? So maybe one hop is missing a route or has a wrong one? Just tapping in the dark because I didn't saw working traceroute forward and backward. Christian