Who owns 169.254.169.254? Just looking at the wget in the setup script...
Also I'd suggest people get an OpenVPN VPN if they can. PPTP is insecure/broken, nobody should be using it ever. And while L2TP/IPSec is secure, it is a massive PITA to use and is often blocked on public WiFi (where a VPN is most useful) because they don't allow the ports/protocols (plus IPSec traversal is a nightmare in some cases).
OpenVPN acts like an SSL connection (not dissimilar to that used by HTTPS) so it works more places. It also traverses most network equipment without issue since, again, it looks similar to HTTPS traffic.
PS - I have no horses in this race, but I have setup an L2TP/IPSec VPN on EC2 before, it was an unpleasant experience all around.
PPS - If you REALLY want OpenVPN to work great put it on port 443. If you browse there nothing will happen, but OpenVPN clients will happily use the port and few if any network equipment is designed to block it.
Also I'd suggest people get an OpenVPN VPN if they can. PPTP is insecure/broken, nobody should be using it ever. And while L2TP/IPSec is secure, it is a massive PITA to use and is often blocked on public WiFi (where a VPN is most useful) because they don't allow the ports/protocols (plus IPSec traversal is a nightmare in some cases).
OpenVPN acts like an SSL connection (not dissimilar to that used by HTTPS) so it works more places. It also traverses most network equipment without issue since, again, it looks similar to HTTPS traffic.
PS - I have no horses in this race, but I have setup an L2TP/IPSec VPN on EC2 before, it was an unpleasant experience all around.
PPS - If you REALLY want OpenVPN to work great put it on port 443. If you browse there nothing will happen, but OpenVPN clients will happily use the port and few if any network equipment is designed to block it.