To set up a Windows PPTP VPN server behind your OpenWRT enabled router, you need to forward the necessary ports and protocols, and install the proper modules.
Finding information about how to do this was a lengthy process. I never actually found the necessary info (although I noticed there are quite a few people which are rather clueless about networking; makes me wonder why they're bothering with OpenWRT in the first place, it's not the easiest firmware out there).
But I've managed to compile the bits and pieces of various sources into a coherent mass. It's not a guide in the literal sense, ...
In Windows, it is possible to obtain the MAC address of the wireless access point you're connected to. This is handy when you have multiple access points with the same ESSID (i.e. "roaming") and want to know which one you're connected to. This is done with the netsh CLI tool, available since Windows XP.
To do this, start a command prompt, and type in:
netsh wlan show interfaces
This shows all wireless interfaces on your system. When your wireless is active and connected to an AP, you get output similar to this:
For all those who recently acquired a WET54G (rev 3.1), or are planning on acquiring one, should read the problem I had with it.
The problem only affects EU versions of the product, as the US version has a more recent firmware available which fixes the problem.
Update: there's still no new firmware. I've updated the links so they are correct again.
And here's a direct link is here.
Anyway, the main symptom is the lock up of the device as soon as a connection with a wireless network has been made, and that network uses WPA-PSK or WPA2-PSK. I've tested this out extensively ...
We had a bit of trouble with an Apache2 server, configured as a front-end proxy for a IIS running various different sites. The idea for this has grown because of the fact that our client had only one public IP address at the time, but had to run multiple sites. Rather than running the sites in IIS on different ports, we setup the Apache2 to proxy requests to the IIS back-end, so the sites were accessible by means of sub-urls.
E.g.:
Running OpenVPN on Vista, works, but requires some workarounds.
Current list of issues:
connection gets established, but route addition fails with route addition failed usingCreateIpForwardEntryRead further for the solutions...
This problem always occurs on a Vista. What happens is that while the connection does get established, the routes are not being added properly, because of an API change in Vista.
To circumvent the issue, add this line to your OpenVPN config file:
route-method exe
This way, the route addition is called directly using the commandline utility.
Did an upgrade of my Linksys WRT54GL to the latest OpenWRT firmware. These are roughly the steps I followed.
My old firmware was a OpenWRT rc5, default release. For my new firmware, I used the ImageBuilder to create a more customized firmware with a lot of packages (such as ntpclient, openvpn, nas, gpio, ...) preinstalled in the squashfs image. I left the new Webif^2 out on purpose, as it's updated at a fair regular base. The image (which has it's build list attached) is called cad, which is because I originally selected it for use with routers at work.
read more
