| www.rodneybeede.com | "I would love to change the world, but they won't give me the source code" - unknown |
I used OpenWrt Firmware Attitude Adjustment (r29484) / LuCI Trunk (trunk+svn8073) and kernel version 2.6.39.4.
option /etc/ppp/options.pptpd # Set IPs to something not in your DHCP allocated LAN but on the same subnet localip 10.1.1.2 remoteip 10.1.1.3-10 #debug
# Tested against Windows 7 client auth name "pptp-server" #debug #dump # pppd logfile option #logfile "/tmp/log/pptpd.log" refuse-pap refuse-chap refuse-mschap require-mschap-v2 # PLEASE NOTE THAT ON OpenWRT (or DD-WRT, etc) distribution builds the pppd is special patched # The MPPC flag builds a non-standard PPP that uses different options. # So don't rely on most pptpd or pppd examples since you need the special version one mppe required,no40,no56,stateless # Makes clients look like they are on the lan proxyarp # Client alive check lcp-echo-failure 3 lcp-echo-interval 60
#USERNAME PROVIDER PASSWORD IPADDRESS # * for IPADDRESS means dynamically assign from the remoteip range in options.pptpd rbeede pptp-server ProvideAReallyLongPasswordHere * gamer pptp-server ProvideAReallyLongPasswordHere *
# This file is interpreted as shell script. # Put your custom iptables rules here, they will # be executed with each firewall (re-)start. WAN=eth1 # Allow VPN server iptables -t nat -A prerouting_rule -i $WAN -p tcp --dport 1723 -j ACCEPT iptables -A input_rule -i $WAN -p tcp --dport 1723 -j ACCEPT iptables -A output_rule -p 47 -j ACCEPT iptables -A input_rule -p 47 -j ACCEPT # Allow VPN pptpd connections access to the lan iptables -A forwarding_rule -s 10.1.1.0/24 -d 10.1.1.0/24 -j ACCEPT iptables -A output_rule -o ppp+ -s 10.1.1.0/24 -d 10.1.1.0/24 -j ACCEPT iptables -A input_rule -i ppp+ -s 10.1.1.0/24 -d 10.1.1.0/24 -j ACCEPT # Allow VPN pptpd connections Internet access iptables -A forwarding_rule -i ppp+ -o $WAN -j ACCEPT