Recent content by mystical

Dual WAN hasn't worked for me since I upgraded to 66_alpha4 from the 56_ release. The DSL modem attached to the backup port LAN1 continues to function for a laptop connected to the modem, and Merlin reports when I disconnect the LAN1 ethernet cable from the DSL modem. So it appears that Merlin...

I have ugraded three ASUS to your Alpha 4 build and will report back if I still see the vpn lockup problems.

For the last year I have had an ASUS AC68U OpenVPN client running Merlin 380.58 connected to an AC68U server running 380.58. Last week I upgraded my client to 380.65_4 and since then I have been experiencing timeouts of the connection after less than 24 hours of operation. The server logs say...

Thanks for your response. I have one OpenVPN client session always open and that is a key feature requirement for this installation. In an effort minimize the load on the ASUS, I have just turned off the Traffic Analyzer -> Statistics feature, but that is almost a second critical feature...

Running 380.58, I am experiencing GUI and OpenVPN freezes anywhere from 1 day to 3 days after reboot. I have turned off all wifi and there is no USB device connected. My web power strip doesn't power cycle the ASUS because it still responds to pings, so when this lockup occurs I ssh to the...

It has been down all day today As a work-around so my ASUS VPN Client can connect to my DDNS ASUS VPN Server during this outage, I added my server address to the client /etc/hosts file.

Hi, I had not thought of that solution, but in my case one of the routers is behind another router. So opening a VPN connection to that 'hidden' router is more complex than just getting the tunnel opened by the 'hidden' router to be bi-directional.

I am experiencing a lockup problem at 3 different sites, all running 380.58 on AC-68Us. During lockup, wired ethernet traffic continues to flow through the 68U but there is no ping response from the 68U cpu. All ASUS are set to reboot one per week, but lockup has occurred to two different...

FIXED: After a careful reading of the previous posts, I learned the per-client route instructions must be saved in /jffs/configs/openvpn/ccd1/...,*not* in /jffs/openvpn/ccd1/... After saving the files to /jffs/configs/... my fully bi-directional routes now are restored perfectly after a client...

I can see that you are correct about the the July dates at the head of the syslog So the syslog does not persist through a reboot? If it would help someone's debugging I could setup my ASUS to log to my NAS.

So if I want to sure I can remotely access my router, it seems I should set 'Enable Reboot Scheduler' to 'yes' and reboot once a week. Do you do that? thanks

Ok, I can see why it would be useful to have two server instances, But my reboot earlier today also caused my vpn client routing file to be lost, which was my original problem in this thread. I have tried to put that 'kaukini' file in /jffs/openvpn/ccd* but after a vpn server restart it is...

No, I didn't change any logging settings, although I have enabled all of the traffic monitoring and QOS features. After reboot the log is small and there seems plenty of free space in the file systems: rob@RT-AC68U-7658:/tmp/home/root# ls -l /tmp/syslog.log -rw-rw-rw- 1 rob root...

Unfortunately there is nothing useful in the syslog, and a very large time gap, which suggests to me that the out of ram condition stopped the process which flushes the RAM log file to NVRAM. If I encounter this condition again, I now know the path to the syslog file and will look there first...

I am running 380.58 on 4 AC68Us and all experience the same problem: After a power cycle or reboot the VPNclients are off even though they we running at the time of reboot. In addition, I have at least one router where the client is always 'on' after a reboot. Thankfully the openvpn server is...