It's confirmed here. installing the latest 2.70 beta xp ipsec client is unable to do any kind of work via vpn behind astaro. The connection is able to be established but she can't access her files, e-mail, servers...anything.
this is a bug...this being marked not a bug is baffling.
Jus to be clear, I'm assuming that you're uing L2TP/IPSec from your windows machine, through an Astaro, to some other endpoint. Astaro is not the L2TP server that you are connecting to. That was implied, but never fully stated.
Also, you mentioned that this same problem existed in 7.201, so this doesn't really belong in this forum, and insisting this should be tagged as a 7.300 bug doesn't make much sense.
Even calling this a bug is pretty hard to do, since the essential part of what you are trying to do works fine. I have customers who do the same as you are describing. For them it works fine. This means that there must be something else involved that make Astaro's behavior different from ipcop. For example, Is there high packet latency on the isp? Is Nat Traversal enabled on the L2TP server? Does ipcop have an IPSec passthru option enabled?
Looking through this thread there seems to be only one NAT masq specified. Does your L2TP vpn use the same network pool as your internal network as assigned by DHCP or is it using the default L2TP VPN pool network?
If using L2TP Vpn pool network you will need a second NAT Masq for the VPN network to the external interface in order to pass traffic to the external world.
Also if you are using this ASG box as your non-default gateway for your internal PCs try setting a SNAT rule such as:
Source: L2TP network
Destination: Internal(network)
Service: Any
Change Source: Internal(address)
This will effectively masq the L2TP pool as the ASG address for return traffic.
William,
Off topic, can I ask why you are always pushing that ipcop crap on here so much? For the free OSS firewalls there are much better than ipcrap.
