Closed arekm closed 11 months ago
Thanks for reporting the issue, I don't think this worked before. The implemented logic as-is, allows either IP address nexthop or dev nexthop, not both.
I can look into it, but probably not anytime soon. Out of curiosity why do you have to specify both in your setup?
Did bisect. It worked until
commit 4bd9c42dbf58bb5bc4edc46088cdc2901a086f86 (refs/bisect/bad)
Author: Brona <brona@robenek.me>
Date: Sun Mar 20 21:57:14 2022 +0100
Fix blackhole routes and minor clean up
but "worked" means it didn't throw error only
% ./src/ip.py r a 1.1.1.1 via 2.2.2.2 dev xxx
Executing: /usr/bin/sudo /sbin/route add 1.1.1.1 2.2.2.2
I don't need this on this setup (and didn't notice that dev xxx was just ignored earlier). I was using this on Linux commonly though.
(such way can be needed when the same IP is reachable thru multiple interfaces)
1.4.1:
I think it worked before.