Skip to main content

dd-WRT PPTP VPN

After several attempts to get a OpenVPN tunnel working on my WRT54GL, using both OpenWRT and dd-WRT, I never could get the tunnel to work.  I tried everything I could think of, even using the built in certificates instead of my own, and I never could connect to the tunnel.

So, I decided to try PPTP, which I feel is a little less secure, as it's not client and server authenticated, but it is better than nothing.  Setting up the PPTP tunnel on the dd-WRT was surprisingly simple.  I think I did the whole thing in about 3 minutes!   

I followed the wiki at:  http://www.dd-wrt.com/wiki/index.php/VPN

But the main parts are:

On DD-WRT, go to the Administration->Services and set PPTP server to active, save the changes, then set the IP of router (192.168.1.1) for the server IP, and under Client IP(s) set a range for connections. (192.168.1.20-29 for example of a ten client set up)
Under Chap Secret put in username * password * for example: testmachine * password1234 * ( The "*" are NOT a Placeholder, they must be there ! ) Use no capital letters. Also avoid using the # character since this breaks pptp. (This also applies to the router administration password that is included by default in the password file for pptpd.)
Now on your PC select Create new Connection under Control Panel -> Network Connections. Select Connect to Network at my Workplace, then select Virtual Private Connection, give it a name (home link). Select what applies, dial up or LAN. Type the WAN IP address of your router, it must be static address or an address through DynDNS.org or the likes. (Thanks loxza)
Then at connect window, type the username and password you used earlier under Chap Secret (in our example:testmachine:password1234). Use no capital letters.
And presto---working PPTP VPN Tunnel!   

Comments

Popular posts from this blog

HP c6180 Printer and Vista

Hp c6180 driver issues with Vista Home Premium My wife has a Vista Home Premium laptop, and the HP C6180 Photosmart printer keeps disappearing from her available printers.  The only way I've found to fix the problem is to reinstall all the HP software. When I do this, I have to download the (large..507M software from HP, or reinstall the printer (ONLY the printer, not the scanner) with the installation disk, as the drivers are not discovered with a "Windows Update" setting.  My guess is that is because HP doesn't like people to install only the printer driver, which would be easy, but they want folks to install all their crapware as well, so they are withholding the drivers from the on-line Microsoft printer database.  So keep your installation CD!  I've also found that unless I install everything on the CD or in the Full Version download (HP Customer Participation Program, HP Imaging Device functions, HP OCR SW, HP All-In-one SW, HP Photosm...

atftpd vs tftpd-hpa

Recently I was trying to tftp files from a Windows computer to a Kali box.   One version of Windows worked, but another didn't.    After much troubleshooting, here were my symptoms: I could tftp a file from-to any Kali box from-to another Kali box I could NOT tftp files to a specific Windows 7 box from any Kali box I could NOT tftp files to a Chrooted-Ubuntu-Chromebook box from a Kali box After MUCH troubleshooting, going through every setting in atftpd, it seemed like it literally was a client OS problem.  Different clients simply would not download files---unacceptable. Thus, I switched to tftpd-hpa.   To install: apt-get install tftpd-hpa files go to/come from /srv/tftp, but it needs to be a tftp user. Thus, I needed to: chroot -R /srv/tftp Also, if you want to be able to put files ON the tftp server (from a client), you need to modify /etc/default/tftpd-hpa: change "TFTP_OPTIONS="--secure"  to "TFTP_OPTIONS="--secure --create" ...

Temper Temperature monitor on a Beaglebone Black

Beaglebone Black as a temperature monitor: Recently I wanted to monitor the temperature of my shed.  I thought I'd use a small computer such as a Raspberry Pi or a Beaglebone or Odroid. My Raspberry Pi boxes were all in use, so I grabbed my Beaglebone, which was doing nothing. I flashed it with the  Debian   9.3   2018-03-05   4GB SD   IoT   image, but that seemed like it was running lots of bloatware and the ethernet interface wouldn't take a static IP with /etc/network/interfaces. So I went with the  Debian   9.3   2018-01-28   4GB SD   LXQT   i  image instead.  I still had the same problem, that lots of junk was running, and I couldn't configure my interface by modifying /etc/network/interfaces So my first step was to get rid of all the bloatware.  If you're using a Raspberry Pi or something, you can skip this and just go to the second step below STEP 1--Remove Blotatware from Beaglebone Black...