RMerlin
Asuswrt-Merlin dev
Here's a quick rundown on what's going on recently development-wise:
OpenVPN:
The past two weeks have been spent implementing OpenVPN and writing a complete webui to manage it. While the OpenVPN code itself comes from Tomato (reused with its original author's permission), the webui had to be created from scratch, and that part alone took many days of development (and shorter sleep nights than usual
). I am sticking to all the same features (and actually same descriptions as well) so people can refer to any of the numerous Tomato tutorials out there explaining how to configure OpenVPN. Just like Tomato, Asuswrt-Merlin will accommodate up to two server instances and client instances.
Note that OpenVPN is nowhere as simple to use as PPTP is. However PPTP has been recently shown to be vulnerable to attacks, so I think it's time people start looking at this for a more secure alternative. And Asus's coming AiCloud will also allow add another secure alternative for people who need remote access to their LAN.
If all goes as planned, I'm hoping to have test builds available this weekend (N66U and AC66U - sorry N16 owners, but OpenVPN is very nvram-hungry. Look at optware for a possible disk-based alternative.)
VPN Status page:
While developing the OpenVPN webui I also added a VPN Status page, which will cover not only OpenVPN but also PPTPD, displaying a list of currently connected PPTP users.
AiCloud:
AiCloud is still in its late stages of betatesting at Asus. Once Asus releases it to the public (along with up-to-date code), I will tackle re-basing Asuswrt-Merlin on the newer code, and start releasing with AiCloud enabled. So fear not, there might be a few days of delay between Asus's release and the integration into Asuswrt-Merlin, but it will be there sooner than later.
Simmering
A few other things are at various stage of development, like an openssl upgrade and NFS support, or fleshing out documentation on the Wiki. It's too soon yet to tell if/when these would be actually implemented, but work has started on these.
And after that...
Once the next release (xxx.16) is out, the release following that (xxx.17) will focus on bug fixing, keeping with my established plan of alternating between new features and bugfixing releases.
Thank you every one for your continued interest and support in this project!
OpenVPN:
The past two weeks have been spent implementing OpenVPN and writing a complete webui to manage it. While the OpenVPN code itself comes from Tomato (reused with its original author's permission), the webui had to be created from scratch, and that part alone took many days of development (and shorter sleep nights than usual
). I am sticking to all the same features (and actually same descriptions as well) so people can refer to any of the numerous Tomato tutorials out there explaining how to configure OpenVPN. Just like Tomato, Asuswrt-Merlin will accommodate up to two server instances and client instances.Note that OpenVPN is nowhere as simple to use as PPTP is. However PPTP has been recently shown to be vulnerable to attacks, so I think it's time people start looking at this for a more secure alternative. And Asus's coming AiCloud will also allow add another secure alternative for people who need remote access to their LAN.
If all goes as planned, I'm hoping to have test builds available this weekend (N66U and AC66U - sorry N16 owners, but OpenVPN is very nvram-hungry. Look at optware for a possible disk-based alternative.)
VPN Status page:
While developing the OpenVPN webui I also added a VPN Status page, which will cover not only OpenVPN but also PPTPD, displaying a list of currently connected PPTP users.
AiCloud:
AiCloud is still in its late stages of betatesting at Asus. Once Asus releases it to the public (along with up-to-date code), I will tackle re-basing Asuswrt-Merlin on the newer code, and start releasing with AiCloud enabled. So fear not, there might be a few days of delay between Asus's release and the integration into Asuswrt-Merlin, but it will be there sooner than later.
Simmering
A few other things are at various stage of development, like an openssl upgrade and NFS support, or fleshing out documentation on the Wiki. It's too soon yet to tell if/when these would be actually implemented, but work has started on these.
And after that...
Once the next release (xxx.16) is out, the release following that (xxx.17) will focus on bug fixing, keeping with my established plan of alternating between new features and bugfixing releases.
Thank you every one for your continued interest and support in this project!
