PPTPD on a Linode with a Windows 7 client: no gateway IP
I've got so far with PPTPD, but I just can't get it to work. My Windows 7 client connects okay, but my Linode doesn't seem to supply it with a gateway IP address, so it can't use the Internet:
~~![](<URL url=)http://dl.dropbox.com/u/1903330/wc/232321124214.png
I added the iptables gre traffic and allowed TCP port 1723, but ended up allowing everything through - to no avail.
I've tried connecting using my Android phone too, but the same thing happened - I couldn't browse the internet.
So below are the configuration files that I'm using:
/etc/ppp/pptpd-options: http://dpaste.com/hold/557152/
/etc/pptpd.conf: http://dpaste.com/hold/557157/
/var/log/syslog: http://dpaste.com/hold/557161/
I'm not sure if any others will be of use, but if there are any let me know.
Should add that I've edited
sysctl.conf
and set
net.ipv4.ip_forward = 1
.
Thanks
6 Replies
SSH tunnels, for example, enable you to do what you describe with almost no effort at all, without worrying about routing; just forward a port (say, 80) on your server to a port (say, 80) on your local machine; clients connecting to port 80 on your server will be served from your desktop, and you can use compression on the SSH tunnel to boot.
Could you point me in the direction of a guide on how to do that?
If anyone can suggest anything for PPTP that would be great, but if I can get SSH tunnelling working I can live with that!
That guide is just like the other guides I found though - I'm not particularly wanting to browse the Internet using my Linode's connection, rather allow people to connect to a port on my Linode and have that forwarded to my local computer.
Is that possible using SSH tunnelling?
That's why I was trying to setup a PPTP VPN, I recently moved and am using an Internet connection that shares the same IP with the entire block - which is fine for normal web browsing, but if I want to host a web server for testing locally and allow people to connect to it (for example) I can't.
That's for a forward tunnel rather than reverse, but the idea is similar.
PuTTY tends to be a bit more short-term (doesn't reconnect if connection is lost, shows up in the taskbar), but there are other clients intended for long-term tunnels or connections.
One kind of hacked-up solution to that might be putting plink in a batch script that infinitely loops, assuming plink will terminate when the connection is lost.
A more proper permanent solution might be autossh in cygwin, ptunnel, tunnelier, etc.