XPost: alt.os.linux.ubuntu, alt.os.linux.mageia   
   From: tauno.voipio@notused.fi.invalid   
      
   On 2.4.2024 19.23, Scott Alfter wrote:   
   > In article ,   
   > Marco Moock   wrote:   
   >> On 01.04.2024 um 18:35 Uhr Markus Robert Kessler wrote:   
   >>> So, I'd like to skip getting such a huge amount of useless routes. I   
   >>> want to set the routing by my own script, instead.   
   >>   
   >> NetworkManager has an option to ignore routes from the peer.   
   >> Connection settings --> IPv4/IPv6 settings --> Routes --> Ignore   
   >> automatically obtained routes   
   >   
   > The Cisco ASA at work pushes some routes to my computer when I connect to   
   > it.  One of them (for a remote office) uses the same 192.168.1.0/24 subnet   
   > as my home network, so I lose access to my file server, printers, etc. at   
   > home when I'm connected to the VPN.  I'd been considering moving my home   
   > network to a different subnet, but this would be easier...will have to look   
   > into it.   
   >   
   > I'd still need a route to 172.16.0.0/22.  Would this have to be added   
   > manually after connecting?   
   >   
      
   The network 172.16.x.x to 172.31.x.x is one of the RFC1918 ranges   
   reserved for private networks, and as such it is non-routable in the   
   outside Net. It is probably fine to have inside of the VPN tunnel.   
   The same applies to the 192.168.x.x network (and 10.x.x.x).   
      
   The commercial VPNs like Cisco want to disable direct Internet access   
   of the client for the duration of the tunnel, to prevent sneak paths   
   to/from the public net and the internal tunneled network.   
      
   --   
      
   -Tauno Voipio   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)