starred/docker-ipsec-vpn-server
1
0
Fork 0
mirror of https://github.com/hwdsl2/docker-ipsec-vpn-server.git synced 2026-04-26 18:15:50 +03:00
Code Issues Projects Releases Packages Wiki Activity

[GH-ISSUE #161] IP address for SSH #148

New issue
Closed
opened 2026-03-02 07:28:05 +03:00 by kerem · 4 comments
kerem commented 2026-03-02 07:28:05 +03:00
Owner
Copy link

Originally created by @AKDub on GitHub (Sep 27, 2019).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/161

I have the docker running on a NAS in my home network - 192.168.1.100.

In the past, I am sure I used to be able to connect to your vpn from work, and ssh into the NAS. Am I mistaken? Currently I cant seem to do this, but nothing has changed recently other than some NAS reboots once in a while.

When I connect to the vpn, I seem to get an IP address of 192.168.42.x. Is this the issue?

Originally created by @AKDub on GitHub (Sep 27, 2019). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/161 I have the docker running on a NAS in my home network - 192.168.1.100. In the past, I am sure I used to be able to connect to your vpn from work, and ssh into the NAS. Am I mistaken? Currently I cant seem to do this, but nothing has changed recently other than some NAS reboots once in a while. When I connect to the vpn, I seem to get an IP address of 192.168.42.x. Is this the issue?
kerem closed this issue 2026-03-02 07:28:05 +03:00
kerem commented 2026-03-02 07:28:06 +03:00
Author
Owner
Copy link

@hwdsl2 commented on GitHub (Sep 28, 2019):

@AKDub Hello! The 192.168.42.x IP is the internal VPN IP that the client gets from the VPN server after connecting. Due to Docker's network isolation among containers, it is generally difficult to SSH from one container (which runs your VPN server) into another container after connecting.

<!-- gh-comment-id:536148828 --> @hwdsl2 commented on GitHub (Sep 28, 2019): @AKDub Hello! The `192.168.42.x` IP is the internal VPN IP that the client gets from the VPN server after connecting. Due to Docker's network isolation among containers, it is generally difficult to SSH from one container (which runs your VPN server) into another container after connecting.
kerem commented 2026-03-02 07:28:06 +03:00
Author
Owner
Copy link

@AKDub commented on GitHub (Sep 28, 2019):

So why did this work before? I’m trying to ssh into the NAS itself, not another container if that makes a difference

<!-- gh-comment-id:536163920 --> @AKDub commented on GitHub (Sep 28, 2019): So why did this work before? I’m trying to ssh into the NAS itself, not another container if that makes a difference
kerem commented 2026-03-02 07:28:06 +03:00
Author
Owner
Copy link

@hwdsl2 commented on GitHub (Sep 28, 2019):

@AKDub I am not familiar with your setup, but you can possibly use the VPN server’s internal address 192.168.42.1 after connecting.

<!-- gh-comment-id:536200118 --> @hwdsl2 commented on GitHub (Sep 28, 2019): @AKDub I am not familiar with your setup, but you can possibly use the VPN server’s internal address `192.168.42.1` after connecting.
kerem commented 2026-03-02 07:28:06 +03:00
Author
Owner
Copy link

@AKDub commented on GitHub (Oct 9, 2019):

Interestingly after trying with different devices to get this to work, on android and on Linux I can connect and have access to the local network of the VPN. On macOS and iOS it connects and I get web access through the VPN, but no access to the VPN’s local network.

So there must be some setting that stops it from working fully on Apple devices, or maybe it’s how they set up their VPN client software that is causing the problem

<!-- gh-comment-id:539884671 --> @AKDub commented on GitHub (Oct 9, 2019): Interestingly after trying with different devices to get this to work, on android and on Linux I can connect and have access to the local network of the VPN. On macOS and iOS it connects and I get web access through the VPN, but no access to the VPN’s local network. So there must be some setting that stops it from working fully on Apple devices, or maybe it’s how they set up their VPN client software that is causing the problem
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
bug

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question
No labels
bug
pull-request
question
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-ipsec-vpn-server#148
No description provided.