Hi, On Thu, Sep 22, 2022 at 04:49:36PM +0100, Sebastian Arcus wrote: > Thank you for getting back to me. I think the route specificity > shouldn't come into play here - as seen from the routing table below, > there are two entries for 192.168.112.0/24 network - one through the vpn > and one through the wired connection. They are both equally specific - > so the route metric, if Windows 10 behaved as expected, should determine > which one is chosen - unless I'm missing something? Sorry for the line > wrapping pushing the route metric value to the next line
This actually gives you a nice opportunity - if the .113.0/24 is free,
you could try pushing a route to 192.168.112.0/23 (note "/23") - normal
routing rules would prefer /24 vs. /23, so "LAN = 24" would always
win before "VPN /23".
Metric is helpful for "/24 vs /24", but if that can be avoided by going
for more-specific-wins, better.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
