CARP IP on LAN question
-
Hi,
I have a question regarding the CARP IP on LAN when doing trace route. HA is working fine otherwise.
Node1 IP: 192.168.1.2
Node2 IP: 192.168.1.3
CARP IP on LAN: 192.168.1.1computer on LAN IP: 192.168.1.33
If I trace route for example to google.com then it of coure reaches the end, but I would expect that traceroute would use CARP IP (192.168.1.1) as the second hop, but instead it is using the current master node IP (192.168.1.2):tracert google.com
Tracing route to google.com [216.58.212.142]
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms 192.168.1.2
2 3 ms 3 ms 2 ms 89.212.XXX.197
3 3 ms 3 ms 3 ms 84.255.XXX.190
4 4 ms 4 ms 4 ms 84.255.XXX.9
... etcIs this correct and by design or it should work differently?
Thank you.
-
@damirj79 said in CARP IP on LAN question:
If I trace route for example to google.com then it of coure reaches the end, but I would expect that traceroute would use CARP IP (192.168.1.1) as the second hop, but instead it is using the current master node IP (192.168.1.2):
The LAN device will send its upstream packets to the CARP VIP if it is stated as gateway. However, when the master responses to the client he uses its interface IP as source.
-
Thank you. I thought it is correct behavior, just wanted to confirm.