Live data from Hacker News

Be your own VPN provider with OpenBSD

networkfilter.blogspot.com

51–60 of 63 posts

Re: Be your own VPN provider with OpenBSD

#51
Another approach: https://github.com/jlund/streisand

"Streisand sets up a new server running L2TP/IPsec, OpenSSH, OpenVPN, Shadowsocks, sslh, Stunnel, and a Tor bridge. It also generates custom configuration instructions for all of these services. At the end of the run you are given an HTML file with instructions that can be shared with friends, family members, and fellow activists."

Re: Be your own VPN provider with OpenBSD

#52
post #10

The disadvantage of this over a shared VPN that doesn't keep logs is that there's now a unique IP address that can be tied back to you. A cool feature for a VPS would be to have a shared IP address between a bunch of customers.

I suppose you could always come up with some script that recreates the whole VPS and thus get a new IP address... but that makes it overly complicated for most people.

Re: Be your own VPN provider with OpenBSD

#53
post #44

Earlier quoted context omitted.

Yes, except for the TCP-over-TCP issue.

SSH does it's own flow control, and with HPN-SSH it is much better. Also, if your connection to the VPN host is quite good, then the TCP-over-TCP issue does not apply as much. The bad cases happen when that connection has packet loss.

All connections have packet loss.

Re: Be your own VPN provider with OpenBSD

#54
post #10

The disadvantage of this over a shared VPN that doesn't keep logs is that there's now a unique IP address that can be tied back to you. A cool feature for a VPS would be to have a shared IP address between a bunch of customers.

Yeah. And in my case, an rDNS lookup will even resolve to a domain name owned by me, as I run some other utilities on that box.

Not stopping me, though. I use the VPN when using public WiFis, knowing that my data is protected but that I'm not anonymous.

Re: Be your own VPN provider with OpenBSD

#55
post #49

We made this really easy, on Ubuntu: https://www.tinfoilsecurity.com/vpn will generate you a private VPN on your own box with a single click. If you don't trust us and prefer to do it on your own, that's fine too, it's open source: https://github.com/tinfoil/openvpn_autoconfig/blob/master/bi...

How about a 'start this with Bitcoin' button? :)

Re: Be your own VPN provider with OpenBSD

#57

Another solution I'd recommend is SoftEtherVPN[1]. It's a bit easier to configure and supports multiple protocols, including OpenVPN. [1] https://github.com/SoftEtherVPN/SoftEtherVPN/

Back when I tried SoftEther several months back, by way of VPN Gate, the connections seemed pretty unreliable compared to OpenVPN. I think the VPN Gate software locked down the options in SoftEther, though. Packet loss affected gaming and video streaming in particular. Casual web browsing was OK.

Re: Be your own VPN provider with OpenBSD

#58
Please everyone keep in mind that if you're using a tutorial to set this up you're probably not an expert, so in the future you could suffer security issues (inherent to any service) without even knowing.

That's why I pay for services, not because I can't follow a tutorial to set them up :)

Re: Be your own VPN provider with OpenBSD

#59
post #52
post #10

The disadvantage of this over a shared VPN that doesn't keep logs is that there's now a unique IP address that can be tied back to you. A cool feature for a VPS would be to have a shared IP address between a bunch of customers.

I suppose you could always come up with some script that recreates the whole VPS and thus get a new IP address... but that makes it overly complicated for most people.

AWS does not charge for first 100 IP addresses.

They also have OpenVPN AMI.

Re: Be your own VPN provider with OpenBSD

#60
post #10

The disadvantage of this over a shared VPN that doesn't keep logs is that there's now a unique IP address that can be tied back to you. A cool feature for a VPS would be to have a shared IP address between a bunch of customers.

On the other hand shared IPs are probably quickly flagged by anomaly detection software.

I.e. Tor IPs typically have very poor 'credit' score.

Post reply on HN