I have a /32 route that is on-link to an interface. If I make that ip address the gateway for another network, the route is always inactive, even if I tell it to not check gateway.
The use case is I assign /32 routes to DHCP customers with DHCP option 121, then I make a static route to them with the gateway on the interface, this works fine. If I add a network for this customer, the network never becomes active even though I can ping the gateway just fine.
That explicitly sends the routing to the right host, but not sure why I need to build all of that when the router is already tracking the mac address of 63.116.158.74.
You need to set the target-scope value of the dst-address=63.116.158.80/30 gateway=63.116.158.74 route to be at least the scope value of the dst-address=63.116.158.74/32 gateway=vlan44_vrrp route.
Routes with a scope greater than the maximum accepted value are not used for next-hop lookup. Each route > specifies the maximum accepted scope value for its nexthop in the target-scope property. > The default value of this property allows nexthop lookup only through connected routes, with the exception of iBGP routes that have a larger default value and can lookup nexthop also through IGP and static routes.
Routes with interface name as the value of gateway are not used for nexthop lookup. If route has both interface nexthops and active IP address nexthops, then interface nexthops are ignored.
This is what I’m doing, my nexthop is a route with an interface as the gateway.