IF I connect to the firewall via VPN as 192.168.1.1 (on my internal LAN e.g. wireless) then I can now ping 192.168.1.1 where I couldn't before... Hmmm. If I connect to an external WIFI e.g. the VPN address is my external IP then I cannot ping 192.168.1.1
I tried Static route of 192.168.1.32/28 in case I'd read the instructions OK - Still no dice. As the article says - routing issues in the tunnel.
Appreciate you looking at this - I can ssh into my server at 192.168.1.10 and bring up a firefox session from there to 192.168.1.1, so all is not lost. The external wireless is on another subnet entirely. If they were on 192.168.1 then that could have been an issue.
There's absolutely no urgency (as far as I'm concerned) It's a curiosity for me, as there is a workaround and actually having a working native VPN (L2TP) connection is a big bonus for me as I don't need to install any additional software from who knows where :-)
I seem to have the same problem as the original poster. I am trying to get connected with Mac OS build in L2TP/IPSec client to a smallwall router. No luck. Please tell me what information I should post and what I can do to help debug this issue.
I use MacOS 10.10 (Yosemite). I have also tried to connect my old iPhone 3GS (iOS 6) with no luck either.
I also wanted to test connecting my Ubuntu workstation and my Debian netbook, but did not find any way to do that in Network Manager. I do not have any Windows machines to try conneting with.
Ok, I have now installed Andy's latest t1n1wall beta (1.10.2b69) based on FreeBSD 10.2 on a test system to see if racoon behaves better. Maybe it does. I don't know, because I'm not able to even get the L2TP/Ipsec client to connect. I have configured the t1n1wall with the same parameters as I configured smallwall.