PLEASE NOTE THE ONE OF THE FOLLOWING IS REQUIRED TO PARTICIPATE IN THE ALPHA!
- Cisco E4200 v1
- Cisco E3200
- Asus RT-N66U
- Asus RT-AC66U
Please visit this URL to download setup instructions and VyprVPN Router Alpha firmware:
You will find a folder for each of the supported routers. Each folder contains:
- A PDF file with instructions.
- The firmware file (.bin or .trx).
- A checksum.txt file with an MD5 checksum of the firmware. It’s optional, but a good idea to validate the MD5 checksum: https://help.ubuntu.com/community/HowToMD5SUM. Thank you Ubuntu for an OS Agnostic page covering MD5 checksum validation!
It’s Alpha, Right?
Remember that this is alpha software, and there may be some bugs in your usage of it. We want to hear all of your experiences, good or bad. In the coming weeks we’re going to be working to improve debugging in general and fix a couple of outstanding, known issues, including:
- Debugging: Incorporating our standard “Contact Support” functionality into the VyprVPN application on the Router so you can easily send us logfiles for debug purposes.
- Debugging: Switching our application logging to be compatible with syslog so you can log things onto a local PC for ease of access/troubleshooting the hard things.
- Debugging: Investigate enabling crash dumps so when a process dies unexpectedly, we can get debug information out of the crash.
- Known Bug: Router goes non-responsive. One of our internal alpha testers reported this problem, a reboot fixes the issue. (Troubleshooting in progress.)
- Known Bug: After waking my device from sleep, it cannot access the Internet until I reconnect the VyprVPN connection. Rebooting the router also fixes the issue, but it’s more than you need to do. (Troubleshooting in progress.)
Let us know how it goes. This is the tip of the iceberg of what we’re going to do in the router space, and we’re interested in any feedback you have. In the coming days I’ll be putting together a public FAQ for the VyprVPN Router Alpha – I already have some Questions I know we’ll be seeing, and we’ve got some answers. We didn’t want to stall getting the firmware in your hands for that.
If something goes wrong please make a post here in the forum. You can contact support – but know that they’re going to be a bit slower on helping with these issues as they will be working hand-in-hand with the router development team. If you need to send logfiles, other information of a sensitive nature, or are just uncomfortable using a public forum for support, please use firstname.lastname@example.org instead.
Good luck, and enjoy!
Michael (MikeDoug) Douglass