Android clients cannot adopt static route on Softether bridge, while Windows clients work fine

[digraf]

Hi all, please any help on the following:
What I want to achieve is to make a LAN to LAN between a main site (site1) and a secondary site (site2) and practically be able to connect any wireless client that is connected on a site2's access point, to a site1's server (so that wireless clients from site2) would not have to install a vpn client on them but transparently see the server from site1.
On site1 I have installed Softether server, it works fine for years.
On site2 I have installed Softether bridge on a windows 10 Pro PC with 2 networks cards. One card(nic1) is connected to site2's router and other card (nic2) has been registered in local bridge while I was installing Softether bridge.
From nic2 there an ethernet cable that connects to a simple unmanaged switch and on the switch I have a simple tplink AP.
On Softether bridge I have enabled SecureNAT and use virtual DHCP so that the devices that connect would not get an IP address from virtual DHCP of site1 (in case there is an internet failure, to be able to talk each other even without internet on Site2).
Finally, I have set a static route on site2's secureNAT (192.168.1.0/255.255.255.0/192.168.100.1) so that the clients from site2 be able to route to the LAN of site1 and if not calling.
192.168.1.0/24 is the LAN of site1
192.168.100.1 is the gateway that is defined in virtual DHCP on site1

Having the above configuration, when I connect a windows 10 laptop on tplink AP of site2, it gets an IP address from the local vDHCP (e.g. 192.168.130.101) and is able to talk to a server from site1 (192.168.1.177).
Sample tracert:
C:\Windows\System32>tracert -d 192.168.1.177
Tracing route to 192.168.1.177 over a maximum of 30 hops
1 673 ms 1531 ms 861 ms 192.168.100.1
2 645 ms 1200 ms 576 ms 192.168.1.177
So, with windows client, everything is OK

When an Android client is connected on tplink AP on site2, it gets ip address from local vDHCP (e.g. 192.168.130.102) but it cannot ping and see the server from site1.
Traceroute from Android device :
1 192.168.130.1 (that is the gateway from the local vDHCP)
2 192.168.30.1 (that is the local physical router of site2)
3. some other IP that is relative to the internet connection of site2's local router, as there is no

So, when using an Android phone it's like the Android device cannot handle the static route defined on local SecureNAT of the bridge, although it gets IP address from that vDHCP.

Please for any help or ideas.
Thank you.

[solo]

"On site2... windows 10 Pro PC" run: route -p add 192.168.1.0 mask 255.255.255.0 192.168.100.1

[digraf]

"On site2... windows 10 Pro PC" run: route -p add 192.168.1.0 mask 255.255.255.0 192.168.100.1

Thank you for your reply, I will check and inform.
But if it works, why Windows clients on site2 work fine and Android not ?

[solo]

But if it works, why Windows clients on site2 work fine and Android not ?

Android ignores your static route. Well, is the workaround OK?