[vpn-help] Ambiguous Source IP Address with overlapping address pools

[lst_hoe02 at kwsoft.de]

Zitat von Mark Larwill <larwill at gmail.com>:

> 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


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6046 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20110601/ba124892/attachment-0001.bin>