Recent content by 9528

Thanks for pointing it out. I've gone back to Surfshark support and asked them to fix this by providing an updated configuration file.

Aug 21 16:12:12 roamast: determine candidate node [A8:5E:45:89:C9:80](rssi: -47dbm) for client [2C:78:0E:C3:D9:8A](rssi: -71dbm) to roam Aug 21 16:12:12 roamast: Roam a client [2C:78:0E:C3:D9:8A], status [0] Aug 21 16:12:12 wlceventd: WLCEVENTD wlceventd_proc_event(481): eth6: Disassoc...

Aug 21 15:31:12 roamast: determine candidate node [A8:5E:45:89:C9:80](rssi: -55dbm) for client [CC:F9:57:FF:D4:25](rssi: -71dbm) to roam Aug 21 15:31:12 roamast: eth5: disconnect weak signal strength station [cc:f9:57:ff:d4:25] Aug 21 15:31:12 roamast: eth5: remove client [cc:f9:57:ff:d4:25]...

Aug 21 15:23:36 rc_service: httpd 1278:notify_rc start_vpnclient1 Aug 21 15:23:36 ovpn-client1[10067]: Options error: You must define CA file (--ca) or CA path (--capath) Aug 21 15:23:36 ovpn-client1[10067]: Use --help for more information. Aug 21 15:23:36 openvpn: Starting OpenVPN client 1...

This is what's under General log. Aug 21 14:31:01 ntpd: Initial clock set Aug 21 14:31:02 rc_service: ntpd_synced 2911:notify_rc restart_diskmon Aug 21 14:31:02 disk_monitor: Finish Aug 21 14:31:02 start_ddns: update WWW.ASUS.COM [email protected], wan_unit 0 Aug 21 14:31:02 disk_monitor: be idle...

Hi all, Been using the same UDP file from surfshark for a while(on 384.18) until I flashed it to 384.19. Since yesterday, it started showing connection error. Been through all troubleshooting with Surfshark support and unable to solve the issue. Any help will be much appreciated.