docker-l2tpipsec-vpn
docker-l2tpipsec-vpn copied to clipboard
Unable to connect - where to find server log files?
Currently attempting running it in a boot2docker with minimal changes to see if I can get it to work. When I first tried to build the image I had problems with python package so I changed it to use debian:wheezy instead, but after that was able to build and run the image. I left the username password as student howdyhowdy and shared secret as howdyhowdy to test it, but I'm unable to connect with following error:
"The L2TP-VPN server did not respond. Try reconnecting. If the problem continues, verify your settings and contact your Administrator."
Enabling verbose logging on OS X I get the following in /var/log/ppp.log on the client.
Sat Feb 7 22:16:16 2015 : publish_entry SCDSet() failed: Success!
Sat Feb 7 22:16:16 2015 : publish_entry SCDSet() failed: Success!
Sat Feb 7 22:16:16 2015 : l2tp_get_router_address
Sat Feb 7 22:16:16 2015 : l2tp_get_router_address 192.168.0.1 from dict 1
Sat Feb 7 22:16:16 2015 : L2TP connecting to server '192.168.59.103' (192.168.59.103)...
Sat Feb 7 22:16:16 2015 : IPSec connection started
Sat Feb 7 22:16:16 2015 : IPSec phase 1 client started
Sat Feb 7 22:16:26 2015 : IPSec connection failed
I tried to override the docker start to just be /bin/bash so I could run the run script in background and look around for any logs on the server, but I couldn't find the logs on the server. Where should I look?
Also here is the error I got building the image on ubuntu:12.04, I would send a pull request for my changes, but I wanted to get it working first. My fork is here: https://github.com/kurtharriger/docker-l2tpipsec-vpn
Sending build context to Docker daemon 87.55 kB Sending build context to Docker daemon Step 0 : FROM ubuntu:12.04 ---> 69c02692b0c1 Step 1 : RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list ---> Using cache ---> fbf575428354 Step 2 : RUN apt-get update ---> Using cache ---> 20fc27861ad4 Step 3 : RUN apt-get upgrade -y ---> Using cache ---> 73ddb81f10e3 Step 4 : RUN apt-get install -y curl wget ---> Using cache ---> 7a5020885b3e Step 5 : RUN apt-get install -y openswan : ---> Using cache ---> b9c59d63ea8d Step 6 : RUN apt-get install -y lsof iptables ufw ---> Running in 02a21d80fb3e Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: ufw : Depends: python2.7 but it is not going to be installed Depends: python (>= 2.7.1-0ubuntu2) but it is not going to be installed Depends: python (< 2.8) but it is not going to be installed E: Unable to correct problems, you have held broken packages. INFO[0002] The command [/bin/sh -c apt-get install -y lsof iptables ufw] returned a non-zero code: 100
Hey Kurt
I haven't messed with the repo in a while and I commend your efforts. The repo in its current state represents my best effort on this. I spent a ton of time trying to get it working, but ultimately wo success.
I'm really sorry I can't be more help. I wish you the best of luck and let me know if you get it working.
Robert
Sent from my iPhone
On Feb 7, 2015, at 9:24 PM, Kurt Harriger [email protected] wrote:
Currently attempting running it in a boot2docker with minimal changes to see if I can get it to work. When I first tried to build the image I had problems with python package so I changed it to use debian:wheezy instead, but after that was able to build and run the image. I left the username password as student howdyhowdy and shared secret as howdyhowdy to test it, but I'm unable to connect with following error:
"The L2TP-VPN server did not respond. Try reconnecting. If the problem continues, verify your settings and contact your Administrator."
Enabling verbose logging on OS X I get the following in /var/log/ppp.log on the client.
Sat Feb 7 22:16:16 2015 : publish_entry SCDSet() failed: Success! Sat Feb 7 22:16:16 2015 : publish_entry SCDSet() failed: Success! Sat Feb 7 22:16:16 2015 : l2tp_get_router_address Sat Feb 7 22:16:16 2015 : l2tp_get_router_address 192.168.0.1 from dict 1 Sat Feb 7 22:16:16 2015 : L2TP connecting to server '192.168.59.103' (192.168.59.103)... Sat Feb 7 22:16:16 2015 : IPSec connection started Sat Feb 7 22:16:16 2015 : IPSec phase 1 client started Sat Feb 7 22:16:26 2015 : IPSec connection failed
I tried to override the docker start to just be /bin/bash so I could run the run script in background and look around for any logs on the server, but I couldn't find the logs on the server. Where should I look?
Also here is the error I got building the image on ubuntu:12.04, I would send a pull request for my changes, but I wanted to get it working first. My fork is here: https://github.com/kurtharriger/docker-l2tpipsec-vpn
Sending build context to Docker daemon 87.55 kB Sending build context to Docker daemon Step 0 : FROM ubuntu:12.04 ---> 69c02692b0c1 Step 1 : RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list ---> Using cache ---> fbf575428354 Step 2 : RUN apt-get update ---> Using cache ---> 20fc27861ad4 Step 3 : RUN apt-get upgrade -y ---> Using cache ---> 73ddb81f10e3 Step 4 : RUN apt-get install -y curl wget ---> Using cache ---> 7a5020885b3e Step 5 : RUN apt-get install -y openswan : ---> Using cache ---> b9c59d63ea8d Step 6 : RUN apt-get install -y lsof iptables ufw ---> Running in 02a21d80fb3e Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: ufw : Depends: python2.7 but it is not going to be installed Depends: python (>= 2.7.1-0ubuntu2) but it is not going to be installed Depends: python (< 2.8) but it is not going to be installed E: Unable to correct problems, you have held broken packages. INFO[0002] The command [/bin/sh -c apt-get install -y lsof iptables ufw] returned a non-zero code: 100
— Reply to this email directly or view it on GitHub.
Thanks for the quick reply. I did make a bit more progress I suppose but still unsuccessful.
While I can echo "hello" > /dev/udp/192.168.59.103/1701 and get xl2tpd to spit an error when running in foreground, when attempting to connect from os x vpn client it seems to receive nothing. I'm thinking perhaps there some initial communication that supposedly needs to happen first, but I'm not sure.
I might try the docker openvpn again, but was looking for something that was easy to setup from the client side and didn't require installing additional vpn clients. Thanks!
I was looking to setup native vpn, instead of open vpn, for the same reasons.
I believe that I solved all the dependency issues and now the issue lies at the networking level. Forwarding the right ports and connections from the external interface, to docker, the container, and then back out that stack to the Internet was very hard to debug.
Like I said, never got it working. Good luck!
Robert
Sent from my iPhone
On Feb 7, 2015, at 10:42 PM, Kurt Harriger [email protected] wrote:
Thanks for the quick reply. I did make a bit more progress I suppose but still unsuccessful.
While I can echo "hello" > /dev/udp/192.168.59.103/1701 and get xl2tpd to spit an error when running in foreground, when attempting to connect from os x vpn client it seems to receive nothing. I'm thinking perhaps there some initial communication that supposedly needs to happen first, but I'm not sure.
I might try the docker openvpn again, but was looking for something that was easy to setup from the client side and didn't require installing additional vpn clients. Thanks!
— Reply to this email directly or view it on GitHub.