You are not logged in.

#1 2016-07-13 01:04:22

AlmostSurelyRob
Member
From: UK
Registered: 2012-03-17
Posts: 77

Cannot access a server inside VPN

I am trying to connect to a server within a PPTP VPN. The VPN seems to connect okay, but I cannot seem to access gitlab server which is within. Windows instructions speak of an automatic proxy which I am specifying in Firefox but that doesn't help. I also tried a number of `ip route add` but that doesn't work.

Here's my /etc/ppp/[tunnel]

# written by pptpsetup
pty "pptp [vpn server] --nolaunchpppd"
lock
noauth
nobsdcomp
nodeflate
name [domain]\\[username]
remotename [tunnel]
ipparam stfc
require-mppe-128
refuse-eap
# usepeerdns

I've tried with and without usepeerdns! After connecting with pon I also alter the routes as I want to access 193.62.122.5.

And the output of ip route

ip route
default via 192.168.0.1 dev wlp4s0  src 192.168.0.12  metric 303 
148.79.38.1 dev ppp0  proto kernel  scope link  src 192.168.0.12 
148.79.160.27 via 192.168.0.1 dev wlp4s0  src 192.168.0.12 
192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.12  metric 303 
193.62.122.0/24 dev ppp0  scope link

I can confirm that the DNS name resolves to an IP address and I've tracked with tracepath that it reaches the vpn server, but then the signal vanishes. What am I missing? Please let me know if you have any ideas.

Offline

#2 2016-07-17 10:45:13

aiBo
Member
Registered: 2010-11-10
Posts: 50

Re: Cannot access a server inside VPN

Have you any access to the gitlab server, so you can analyze from there? I'd guess, that your packets reach the gitlab server fine, but the response packets don't find their way back, as they have no route to the machine you try to access the server from. An alternative to setting a static route on the gitlab server would be to use NAT on the VPN server.

Offline

#3 2016-07-17 22:37:44

AlmostSurelyRob
Member
From: UK
Registered: 2012-03-17
Posts: 77

Re: Cannot access a server inside VPN

Thanks for coming back to me on this. I have Ubuntu-based laptop from work and the Network Manager generated configuration seems to work fine there. Ubuntu redirects everything to the tunnel, which seems like an overkill, but to me it indicated that the problem is on my side after all.

Offline

Board footer

Powered by FluxBB