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 Photosmart Essential, HP

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" I al

Security Onion on the Antsle

My Setup of Security Onion on the Antsle: Recently my IDS box, an Intel Atom D2500 Fanless Mini-ITX PC, D2500CCE, died.  Truth be told, I think it came from the factory in a bad state, as I originally thought I had a bad graphics driver, but I then noticed that, after much troubleshooting, it wasn't a driver issue at all.  The box just sometimes wouldn't boot up correctly with video.  It seems heat related, something like not enough thermal paste on the CPU, as after it is powered off for a while it is more likely to boot than when it is warm.  Along with that issue, this box maxed out at 4GB of RAM (only has 2 memory slots, each of which will only take a 2GB card max) and had a single processor, so it was under powered for Security Onion. So, I decided to quit limping along on P.O.S. boxes, and buy a little more heavyweight box for my networked IDS.   Security Onion requires a minimum of 8GB of RAM, and 4 cores per their specs page https://github.com/secur