I wasn't able to reproduce the bug in my setup, so I'm guessing a bit here. I committed a possible fix that should be in the next update.
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
cd /usr/pluto/binWhere you replace xxxxx with the newest file.
gdb Advanced_IP_Camera /home/coredump/1/core_Advanced_IP_Camera_xxxxx
virtual_private=%4:192.168.80.0/24and it is working, so I don't think that is your problem.
I found I couldn't get a connection to work however until I replaced the !VPNpass1 against my user with a plain text password. Hope this helps someone make sense of the issues.What do you mean, "!VPNPass1" seems pretty plain text to me..?
Note: Currently you need to re-enable the user and change his username after any change to the Network settings page as the files are rewritten
Do NOT forward port 1701 (L2TP), this would have allowed direct access to the L2TP server, bypassing IPSEC entirely and sending all your data unencrypted. The whole idea is that the IPSEC connection encrypts your data from end to end, and on the server end, this data will be passed on to port 1701 internally.It *is* easier to get a connection when not going through IPSEC, but some devices will happily connect to the L2TP server if the IPSEC fails for some reason.