I have an Asus RT-N16 on which I was running Shibby 102 with an OpenVPN client configured to send all traffic through to a VPN service provider. All has worked fine, with rock-solid stability, but I wanted to create a VPN tunnel to my nearby office, so, after some research, concluded that it should be possible to set up the router to act as a VPN server, with the office initiating the connection as an OpenVPN client. The only problem is that it's not possible in Shibby builds. The problem is lack of NVRAM space (32KB in the case of the RT-N16) and the large size of the OpenVPN keys and certificates. For the server side, the file sizes are: ca.crt is 1359 bytes server.crt is 4069 bytes server.key is 916 byte db1024.pem is 245 bytes The client side files are also very large. Long story short, could not squeeze client and server onto the RT-N16 under shibby 102. The original Shibby 102 USB/VPN build left 11.34KB free after a fresh install, so I tried Shibby MiniVPN (without USB) and that gave 12.66KB free after a new install, which was still too little. Toastman 7500.2 RT-VPN gives 15.10KB free NVRAM after a fresh install and that was JUST big enough to get all the client and server configuration details into the router. However, after setting up a few other very basic things, like WiF, DHCPi and changing the router's IP address, I'm down to 228 bytes. That doesn't give me much scope for further configuration changes. The bottom line is that the large OpenVPN key and certificate sizes are a crying out for some kind of compression before being stored in NVRAM. Right now, it's simply not possible for me to run even a "miniVPN" Shibby build if I want to have both a client and server configured, simply because of insufficient NVRAM space. Toastman's build is just about hanging in there but I'm reluctant to do any more changes in case I use up my remaining 228 bytes of free space. Can anyone comment on whether compression of selected NVRAM parameters is feasible?