Can I define the default gateway metric with Fortigate DHCP server?

[dan]

I do have a network 192.168.193.0/24 that provides the IP address via linux/dnsmasq. (VLAN1, not tagged). This is the main network. 

I do have another network 10.10.10.0/24 that provides IP address via interface DHCP server of a Fortigate. (VLAN 10 tagged). This is a test network.

The Windows computer accesses both networks with the same interface, whereas the 10.10.10.0/24 network is in a tagged VLAN thus using a virtual network interface.

I end up with the following default routes.

     Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
          0.0.0.0          0.0.0.0       10.10.10.1      10.10.10.31     26
          0.0.0.0          0.0.0.0  192.168.193.100   192.168.193.82     26

For some reason, Windows thinks that the route via 10.10.10.1 is more attractive that the one via 192.168.193.100. But I need the default route to 192.168.193.100 to be used. I can "fix" that by assigning manually a higher Metric to the virtuel interface, but I'd rather like to have this done via the fortigate DHCP.

Is there a way to make sure that the default route coming from Fortigate DHCP has a higher Metric?

Thanks

dan

PS. I can "cheat" the system by assigning a higher "interface" Metric to the virtuel interface itself (i.e. Set-NetIPInterface -InterfaceIndex 8 -InterfaceMetric 30). I just wonder if something with a similar result works via DHCP from a Fortigate..

[funkylicious]

I am not sure u can manipulate the metric from DHCP.

[mvinck]

I would just adjust the static route to have a higher metric.

[dan]

That's what I do. But the changed metric is lost after each reboot. :(

[Christian_89]

The static route should not be deleted after a reboot.
Is only this entry deleted or all changes?