We have an ASA5510 that we can connect to through the Windows VPN client (L2TP). Our network has several subnets in the 192.168.0.0 range (the ASA knows where to redirect the traffic for the other subnets to).
In the ASA, we have the following VPN Pool:
ip local pool clientVPNpool 192.168.232.1-192.168.239.254 mask 255.255.0.0
Now, when the client connects to the ASA, he gets an IP address, but the route that refers traffic to that IP is 192.168.232.0 255.255.255.0 and not 192.168.0.0 255.255.0.0 (as I would expect since that's the netmask we gave the IP pool).
Now I could change the VPN client to add the route each time the client connects to our vpn, but I was hoping there would be a simpler solution.
If I add this route:
route add 192.168.0.0 MASK 255.255.0.0 192.168.232.1
all works as expected...