os-tailscale: Don't create unique route for every peer

[Leseratte10]

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• When the request is meant for an existing plugin, I've added its name to the title.

Is your feature request related to a problem? Please describe.
I've set up the Tailscale plugin and noticed that while the plugin only created one route for the IPv6 subnet (fd7a:115c:a1e0::/48 -> tailscale0); for IPv4, there's a dedicated route entry for every single client connected to my Tailscale network (100.64.0.1 -> tailscale0,, 100.64.0.2 -> tailscale0, 100.64.0.3 -> tailscale0 and so on).

This makes the list of routes unnecessarily large.

Describe the solution you'd like
Is there a reason why IPv4 doesn't behave the same as IPv6? I would have expected a single route for 100.64.0.0/10 to be added that points to the tailscale0 interface, just like the one for IPv6.

Or is this behavior triggered by Tailscale itself and not by the OPNsense integration? I haven't seen this behavior on any of my other Tailscale clients, the routing table is always nice and neat.

Describe alternatives you've considered
The alternative would be leaving everything as it is, filling the routing table with tons of entries ...