Hi, On Fri, Sep 23, 2022 at 11:01:49AM +0100, Sebastian Arcus wrote: > > Plus, like Gert said, if 192.168.113.0 is free, then modifying your VPN > > set up to do > > push "route 192.168.113.0 255.255.254.0" > > should definitely ensure that the LAN route takes precedence over the > > VPN route, regardless of the metric. > > 5. Regarding Gert's suggestion, 192.168.113.0 is not available - but > even if it were, I'm not sure I'm following the mechanics behind the > suggestion. Why would we be trying to push a route to 192.168.113.0/25 > through the tunnel, when the server I am trying to access is on > 192.168.112.0? I think I'm missing the point somehow
/23, not /25 - so a supernet, including .112 and .113
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
