> you just have to put them on separate interfaces I don’t have to do this with normal data link layers. That’s the point of the complaint. Wireguard is not a

> you just have to put them on separate interfaces I don’t have to do this with normal data link layers. That’s the point of the complaint. Wireguard is not a true data link layer. Manually configuring multiple interfaces for something I can do with just one interface with a normal data link layer at runtime is an extra inconvenience. > This is for exactly the same reason that a routing table can only have one default entry. If you want two default entries, make two routing tables. Using nftables I can specify different routers to use based on arbitrarily complex packet rules. Using just one interface. I can’t do this with wireguard, it will only allow me to to route arbitrary packets to a single peer on an interface. This is an inconvenience.