Dear RMerlin,
after a dirty update from 384.19 to beta 2 I was not able to access via ssh to the router anymore. After the factory default reset, it was possible, but I had problems with my x3mrouting script. So I wanted to downgrade to 384.19 . Downgrade successful, but the restoring of my saved configuration didn´t work.
So back to beta 2 and made a new configuration. I had the following problems:
1. SSH access is working, access via winscp isn´t working anymore after default reset. Neither on beta 2 nor after downgrading
2. I had three different VPN providers. Only one is working. If you establish a vpn connection with cyberghost and/or windscribe, the complete internet traffic is blocked and no traffic is possible (VPN Client 3 and 5 tested). If you turn off VPN, the connection is still not possibe, you have to reboot the router. Ping command stops during activation of the vpnclient. Syslog in the attachment (VPN 1 and 4 are working without problems, but if you manually turn on Cyberghost and connection is established, all internet traffic is blocked)
3. I got a failure with the DNSMASQ - because of a lock file.
ls -al | grep lock
-rws--x--- 1 su root 0 May 5 2018 ebtables.lock
What is that ?
Do you have any ideas, to solve my problems ? I would appreciate your support.
Thanks a lot.
Hugo