I thought I understood how route selection works: Most specific route is
always selected.
So if you have a route for 10.0.0.0/8 and another for 10.0.0.0/24 then the
/24 will be selected when the destination falls within the /24
This works as expected.
However, if I add a /32 route e.g. 10.0.0.42/32 then it gets prioritized
_lower_ than the /8 and /24
Why does this happen and is there anything I can do about it?
Example:
ip route add 10.0.0.42/32 src 10.0.0.1 dev eth0
ip route add 10.0.0.0/24 src 10.0.0.1 dev eth0
ip route
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1
10.0.0.0/8 dev eth0 proto kernel scope link src 10.0.0.1
10.0.0.42 dev eth0 proto kernel scope link src 10.0.0.1
Aaaa! Why is the /32 all the way at the bottom?
In other news: Made some progress on extender node stuff tonight. I decided
to use VLANs to put both the open and adhoc networks on the extender nodes
and have updated the configs for tp-link and extender node accordingly.
--
marc/juul