Recent content by montr

I have a Synology DS-214+ NAS. It has a IPSEC server and client package. I also have built-in sync package for Google Drive and OneDrive.

I have version 3.0.0.4.376_1071. I am able to Wake on LAN reliably any capable device remotely with the RT-N66U. I do so by using the Asus mobile Apps (AiCloud on iTunes or Android market) or by remotely login to the ASUS RT-N66U after setting an OpenVPN tunnel. I also done the same with...

I did setup OpenVPN on my Asus RT-N66U and Synology DS-214+ (on a different port). It appears to me that the Synology VPN is more responsive than the Asus, better CPU? Sometime, I am not able to connect reliably or at all because the hotel or vacation home IP address range is the same as my...

I recently acquired a DS214+ with two Seagate NAS 4 TB disk. Everything is great, I am happy with my purchase. However, now I saturate the single 1 Gbps and I feel there is still some capability left untouched. I know about link aggregation but I have an 8 ports unmanaged switch. I have 2...

I have an Asus RT-N66U and a Synology NAS. I setup an OpenVPN with TCP port 443 on the Asus Router and an OpenVPN with UDP port 1194 on the Synology. On the Asus router, I just had to forward port 1194 to the NAS IP. With this simple setup, depending where I am and the firewall in between, I...

I have seen reports that some models do not have the Suspend S3 mode working properly. Anyone know which models have this implemented and working properly? Here are the units that I am interested: DSM 5.0 with DS214+, DS214 and DS414. Thanks in advance Leo

Good that you solved the problem. As for the ASUS firmware, the only setting is "Connect to DNS Server automatically" on http://192.168.1.1/Advanced_PPTPAdvanced_Content.asp . It is set to "Yes" but no DNS service unless I enter the DNS address manually.

I have a RT-N66U and I am using the Asus firmware. I have the same problem, no DNS on the client VPN after connection. This started after I upgraded to version 3.0.0.4.374_979 from 3.0.0.4.372_1393. To solve it, I had to enter manually the DNS server address (AT&T Uverse or OpenDNS...