Zitat von Mark Larwill <[email protected]>:
With Windows 7, and Shrew Client 2.1.7 if a user has a DHCP address on the same network as the virtual address pool then the source address is not always the same, some traffic will get tunneled and other traffic won't. In the case where the traffic is tunneled the source IP is the Virtual IP, in the case where traffic is not tunneled the source IP is the interface's DHCP address. In the case where "tunnel all" is set then it seems like the source address should always be the virtual IP address.Is there a reason why some traffic is tunneled and other traffic is not? What is the logic of which source address is used? Is that an OS specific issue or is that specific to the shrew client? Is the configuration as described above supported? If not can support be added?
Do i understand corretly that you have overlapped address-space between your lokal net and the VPN? This will not work.
Regards Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
