mirror of
https://github.com/hwdsl2/docker-ipsec-vpn-server.git
synced 2026-04-26 01:55:53 +03:00
[GH-ISSUE #186] Use image tag versions #173
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Shagrat2 on GitHub (May 4, 2020).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/186
Yesterday updated image VPN stopped working
I wanted to roll back to the old version but you only have the latest
@hwdsl2 commented on GitHub (May 4, 2020):
@Shagrat2 Thanks for the report. Do you know why the new version stopped working? You can view xl2tpd logs using
docker logs ipsec-vpn-server, and Libreswan logs using this method [1].[1] https://github.com/hwdsl2/docker-ipsec-vpn-server#enable-libreswan-logs
@hwdsl2 commented on GitHub (May 4, 2020):
An image built based on Libreswan 3.29 (previous version in this repo) has been pushed with tag
3.29. Please try it, then let us know if it works for you.When using
docker run, replacehwdsl2/ipsec-vpn-serverwithhwdsl2/ipsec-vpn-server:3.29.@Shagrat2 commented on GitHub (May 4, 2020):
Perhaps the reason is different
The connection itself works and the server responds to the internal address. But the route does not work
2 days ago everything worked fine
hwdsl2/ipsec-vpn-server:3.29
Route for MacOS: route -p ADD 172.20.0.0 MASK 255.255.0.0 192.168.42.1
@hwdsl2 commented on GitHub (May 4, 2020):
This may be related: https://github.com/moby/libnetwork/issues/2331. Is your Docker host running Debian 10 (Buster)? Try the workaround mentioned in that issue, then reboot and re-connect the VPN.
Let us know if it works. If it does not, I can try to push a version with Debian 9 (stretch) for the Docker image (it was upgraded to Debian 10 yesterday).
@Shagrat2 commented on GitHub (May 4, 2020):
$ hostnamectl
Static hostname: vr
Icon name: computer-vm
Chassis: vm
Machine ID: 2b287b99126e4096b42b24c5d019bcb0
Boot ID: 3ffb1a59d0604f35993d58c7598d4e08
Virtualization: qemu
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.9.0-12-amd64
Architecture: x86-64
@hwdsl2 commented on GitHub (May 4, 2020):
@Shagrat2 Thanks for the details. I could not reproduce this issue on a fully updated Debian 9 system with same kernel and Docker version
19.03.8.More specifically, I don't see this line in the
docker logs ipsec-vpn-serveroutput:What was the command that you used to start the Docker container? Did you add
--network=host(not recommended)? And what is your Docker version? The error above indicates that something is wrong with the IPTables rules in the Docker container (i.e. bothnftablesand "legacy" iptables rules are present).@hwdsl2 commented on GitHub (May 5, 2020):
@Shagrat2 Try the Debian 9 based Docker image. You can build it like this:
When finished, re-create the Docker container. At the
docker runstep, use the image you just built, e.g.hwdsl2/ipsec-vpn-server:3.31-debian9.Let us know if this works. If so, it would be great if you can provide more information on your setup, to see why the Debian 10 based image does not work.
Since the new Libreswan version is not the root cause for your issue, I plan to remove the
3.29tag from Docker Hub.@Shagrat2 commented on GitHub (May 5, 2020):
3.29 Logs - Route not work
@Shagrat2 commented on GitHub (May 5, 2020):
hwdsl2/ipsec-vpn-server:3.31-debian9 - work OK!
vpn.env