Martin Pieuchot [m...@openbsd.org] wrote: > Currently we leave RTF_STATIC route entries in the table when the > address they are attached to is removed from a system. > > That's why ifas need to be refcounted and that's why we have *a lot* > of checks in the stack to not use cached routes attached to such ifa. > > I'd like to simplify all of this by simply purging all the routes > attached to an ifa being removed. This behavior is coherent with > the fact that routes *need* an ifa to be inserted in the table. > > This makes the kernel simpler as it no longer try to find a new ifa > when a route with a stale address is being used. >
I'm pretty sure this feature has been broken for a while. Once upon a time in OpenBSD, this used to work: ifconfig em0 192.168.1.2/24 route add default 192.168.1.1 ping 8.8.8.8 reply! ifconfig em0 delete 192.168.1.2 ifconfig em1 192.168.1.2/24 ping 8.8.8.8 reply! For some years, this has been required: ifconfig em0 192.168.1.2/24 route add default 192.168.1.1 ping 8.8.8.8 reply! ifconfig em0 delete 192.168.1.2 ifconfig em1 192.168.1.2/24 **route delete default** **route add default 192.168.1.1** ping 8.8.8.8 reply! It appears, what you're proposing is: ifconfig em0 192.168.1.2/24 route add default 192.168.1.1 ping 8.8.8.8 reply! ifconfig em0 delete 192.168.1.2 ifconfig em1 192.168.1.2/24 **route add default 192.168.1.1** ping 8.8.8.8 reply! As a user (only), I really like the original behavior, it seems to be consistent with the behavior of some other systems, at least in the case of the default router. If there was some way to do this without stupid complexity, it might be worth considering. In any event, what you propose seems much better than the current state of affairs, where you end up with broken routes in the table that need nothing more than to be removed. Chris
