OK. There was a static route (from an old loopback interface
test not related to the CARP setup) that pointed to the IP of
the carp interface. Seems that this is not supported with CARP.
Not documented, so let's do it here:
The message
"arpresolve: XX.YY.16.3: route without link local address"
can be provoked as follows:
1.) Configure a CARP Interface with the IP XX.YY.16.3
2.) Configure a static route that points to the carp interface:
route add XX.YY.99.99 XX.YY.16.3
3.) If the machine (router) receives packets for XX.YY.99.99,
then the above arpresolve error will show up.
- Christian
