On 15.03.06 09:27 +0100, Polus, Tomasz wrote:
> IMO this is a huge issue for all clients using simple VPN-IPSEC
> outgoing connections.... Is there anyone (m0n0wall developer maybe)
> who can make more thorough troubleshooting?
If you'd like to contribute to a solution, you should provide more
information - the output from http://m0n0wall/status.php after a
failed VPN connection attempt would be very helpful, as it would
allow us to determine which rule caused the packets to be blocked and
what the state of the NAT table was.
I've used the following VPN clients successfully behind m0n0wall with
various remote VPN gateways, some of which didn't support NAT-T (and
it worked anyway, as is to be expected with ESP in tunnel mode):
- SafeNet SoftRemote
- Cisco VPN client
- TheGreenBow VPN client
- Equinux VPN Tracker
- SonicWall Global VPN client
One thing that should be noted is that m0n0wall doesn't attempt to
preserve the LAN host's source port when doing outbound NAT. If you
have a remote VPN device that insists on the VPN client's port being
500, then it won't work. Some other firewalls attempt to preserve the
port for the first connection, and some don't.