Lunarhotel.co.uk

Next, lets look for a Linux VPN server. Do a search for this in google, and you'll get results for a product called "Openswan". Openswan uses (by default) IPSEC to generate vpn tunnels, which are very secure, and are supported by most hardware vpn solutions, and are generally created on demand (rather than having to double click a "connect to my vpn" icon) .. and I expect your response will be the same as mine (at the time):

"I just need a bog standard PPTP VPN. Yes I’m aware that its not as secure as IPSEC and that Microsoft might not suit everyone’s tastes, but I just want a way of setting up a VPN server using Linux, that I can get up and running in ten minutes, like I do with Windows, and people are raving about Linux, so I must be able to do that right?"

Right! on all points but the ten minutes! Now obviously Im generalising, and I dont think that Im sooooo intelligent that if I couldn’t figure it out in ten minutes, then no-one else will... but for your average "Ive used microsoft products most of my life, I know my stuff, and now I want to try linux" IT person... ten minutes wont even scratch the surface.

The main reason for this is the assumed level of knowledge. Microsoft, generally assumes a very low, or non existent level of knowledge for most of its products. Sure you cant set up Exchange with various bells and whistles without knowing a bit about what you're doing, but generally, if its possible to do, Microsoft have written a Wizard for it. As I mentioned before, its quick and simple and protects you from the inner workings of whatever it is you're setting up. Linux on the other hand (somewhat incorrectly) assumes that (in the case of a vpn server) you know the impact of changing the MTU, or what a pre-shared key is, or how security certificates work.

I guess that’s what sums up the problems with *nix (linux / unix): The assumed level of knowledge is just too high. I mentioned earlier that there have various attempts at getting linux "user friendly" And of course there is one notable success. OS X (Yes the mac operating system) Is living proof that it can be done, without compromising the "nuts and bolts" functionality of linux. But if you want OS x... again, It'll cost you!

My other feeling on Linux is that its inherent strength is also simultaneously it greatest weakness. That of course being the "community" nature of its support. Now i dont want to detract at all from the benefits of it, and 99% of people who have the knowledge are normally all to happy to offer advice to a noobie like me who's sitting on their pc on the other side of the world. (Who says charity is dead?) But unfortunately, people who have a good solid understanding of linux, tend to assume (as I touched on earlier) that you know a lot more than you actually do. But who can blame them? they've been using linux for years, so its obvious to them that the # prompt is the equivalent of the c:\ prompt in DOS/Windows. They assume you know that must have the gcc++ development Libraries installed in order to compile "Kevins xyz firewall and proxy server" and of course... this isn’t always the case.

Development to most standard users is something "other IT people do" so understandably, encountering an option in a Linux Installation wizard of "Install the gcc++ development libraries?" Is usually met with a thought process similar to : "I wont need those, because Im just trying to install a (for example) Vpn server, and have no intention of developing any programs" , and the box is left unticked. However, once you get your linux box setup (a couple of hours of installation) and try installing almost any program of any worth, and of course you'll find you'll need to compile it, and that means you'll need (guess what?) the gc++ development libraries!