Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Extremely Low Download Speed (0.5mbps?!) ExpressVPN (LOGS!)

    OpenVPN
    6
    24
    3.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Chillstice
      last edited by

      Intro
      I'm relatively new to pfSense - it's been an awesome experience so far - however I would consider myself an intermediate to advanced user. I have successfully built my pfSense box (specs below) and connected it to the wan connection from my ISP, Comcast. My goal is to run a router-level VPN across the whole network and route traffic using firewall rules. I tried using StrongVPN, but their pfsense support is really weak and I couldn't get it to work. I was able to switch over to ExpressVPN and get the VPN connected using OpenVPN. Connecting to the VPN server and having a usable connection are two different things. I've been troubleshooting for the past few days trying to get at least 50% of my normal, non-VPN download speed consistently. I've been failing to do so and now I'm reaching out to more communication channels. I spent about an hour on a Live Chat with an engineer from ExpressVPN, but that didn't help much. I've been changing settings all over pfSense to no avail. I have no idea what's happening to the bandwidth.

      pfSense Box
      https://pcpartpicker.com/user/Chiller252/saved/yrcm8d
      Asus B75M-PLUS
      Intel Core 13-2120 3.3GHz 2 cores, 4 logical
      4GB Kingston Value Ram 1600MHz
      pfSense installed on a Seagate Barracuda 7200 250GB sata 6GB-s HDD
      Intel EXPI9404PTL Pro 1000 PT Quad Port Network adapter

      Location: Littleton, CO 80120
      VPN Server: usa-denver-ca-version-2.expressnetw.com (physically closest)

      pfSense OpenVPN Client Settings
      https://i.imgur.com/IKAww5F.png
      Disabled: no
      Server mode: Peer to Peer (SSL/TLS)
      Protocol: UDP on IPv4
      Device mode: tun - Layer 3 Tunnel Mode
      Interface: WAN
      Local Port:
      Server host or address: usa-denver-ca-version-2.expressnetw.com
      Server port: 1195
      No Proxy

      Username and Password are correct

      Use a TLS Key enabled
      TLS Key correct
      TLS Key Usage Mode: TLS Authentication
      Peer Certificate Authority: ExpressVPNCA
      Client Certificate: ExpressVPN Client Cert
      Encryption Algorithm: AES-256-CBC
      NCP disabled
      Auth digest algorithm: SHA512
      Hardware Crypto disabled

      Compression: Adaptive LZO Compression (tried LZO as well)
      Topology: Subnet
      TOS disabled
      Don't pull routed: unchecked
      Don't add/remove routes: unchecked

      Custom options:

      persist-key;persist-tun;remote-random;pull;tls-client;verify-x509-name Server name-prefix;remote-cert-tls server;key-direction 1;route-method exe;route-delay 2;tun-mtu 1500;fragment 1300;mssfix 1450;keysize 256;sndbuf 524288;rcvbuf 524288;auth-nocache;

      UDP Fast I/O: Use
      Send/Recieve Buffer: Default
      Verbosity level: 3

      Testing

      Normal non-VPN Comcast Xfinity speeds: 10-12 Ping, 230-240mbps Down, 10-12mbps Up
      http://beta.speedtest.net/result/6912853403
      https://i.imgur.com/uMhv4rh.png

      Good ExpressVPN speed (only occurred for a short period of time): 28 Ping, 143mbps Down, 10mbps Up (60% normal download speed)
      https://i.imgur.com/Sv9ngJ3.png

      And one time the ExpressVPN speed was: 56 Ping, 0.48mbps Down, 9mbps Up (0.002% normal download speed)
      https://i.imgur.com/YFFXJHi.png

      Assesment
      I think what might be happening is that since the traffic from/to the VPN server is UDP, as it's coming back from the VPN server (download) Comcast is throttling the UDP traffic back to the house. This UDP traffic patter can appear similarly to a DDos attack and they might have traffic shaping rules that mitigate that kind of attack, while also destroying my VPN download speed. I tried switching to TCP, but I don't think ExpressVPN supports that. I would be happy with at least 100mbps, still less than half what I can get bypassing the VPN, but way better than less than 10mbps.

      Don't hesitate to ask for more information. I'll add it to the OP. I'm determined to get this figured out/fixed.

      Edit: Logs
      Okay, so this is weird. The last two days using ExpressVPN has been a flawless experience. I've been consistently getting the last speed I reported (10-12 Ping, 140-150mbps Download, 9-10mbps Upload) however something in the last 10 hours has changed and now the speed is less than half that. It's not as slow at the title of the thread advertises, but it's nowhere near what it was the last two days. I was able to capture the pfSense logs of the last 10 hours and I will gladly share it here for people to pick through.
      At the start of these logs the speed is excellent, by the end of the logs it's way worse:

      System Logs:

      Jan 1 04:30:04 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Emerging Threats Open rules are up to date...
Jan 1 04:30:05 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Snort VRT rules are up to date...
Jan 1 04:30:05 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] There is a new set of Snort GPLv2 Community Rules posted. Downloading community-rules.tar.gz...
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Snort GPLv2 Community Rules file update downloaded successfully.
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Hide Deprecated Rules is enabled. Removing obsoleted rules categories.
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Removed 0 obsoleted rules category files.
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Updating rules configuration for: WAN ...
Jan 1 04:30:11 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Building new sid-msg.map file for WAN...
Jan 1 04:30:11 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Updating rules configuration for: LAN ...
Jan 1 04:30:14 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Building new sid-msg.map file for LAN...
Jan 1 04:30:14 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Updating rules configuration for: EXPRESSVPNINTERFACE ...
Jan 1 04:30:17 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Building new sid-msg.map file for EXPRESSVPNINTERFACE...
Jan 1 04:30:17 	SuricataStartup 	60631 	Suricata STOP for WAN(5050_em1)...
Jan 1 04:30:17 	kernel 		em1: promiscuous mode disabled
Jan 1 04:30:19 	SuricataStartup 	62442 	Suricata STOP for LAN(10768_em0)...
Jan 1 04:30:19 	kernel 		em0: promiscuous mode disabled
Jan 1 04:30:21 	SuricataStartup 	64089 	Suricata STOP for ExpressVPN(5448_ovpnc1)...
Jan 1 04:30:21 	kernel 		ovpnc1: promiscuous mode disabled
Jan 1 04:30:23 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Suricata has restarted with your new set of rules...
Jan 1 04:30:23 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] The Rules update has finished.
Jan 1 04:30:23 	SuricataStartup 	65750 	Suricata START for WAN(5050_em1)...
Jan 1 04:30:23 	check_reload_status 		Syncing firewall
Jan 1 04:30:23 	kernel 		em1: link state changed to DOWN
Jan 1 04:30:23 	kernel 		em1: promiscuous mode enabled
Jan 1 04:30:23 	check_reload_status 		Linkup starting em1
Jan 1 04:30:24 	SuricataStartup 	66916 	Suricata START for LAN(10768_em0)...
Jan 1 04:30:24 	php-fpm 	17844 	/rc.linkup: DEVD Ethernet detached event for wan
Jan 1 04:30:24 	check_reload_status 		Linkup starting em0
Jan 1 04:30:24 	kernel 		em0: link state changed to DOWN
Jan 1 04:30:24 	kernel 		em0: promiscuous mode enabled
Jan 1 04:30:25 	SuricataStartup 	68226 	Suricata START for ExpressVPN(5448_ovpnc1)...
Jan 1 04:30:25 	kernel 		ovpnc1: promiscuous mode enabled
Jan 1 04:30:25 	php-fpm 	67758 	/rc.linkup: DEVD Ethernet detached event for lan
Jan 1 04:30:26 	check_reload_status 		Reloading filter
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	check_reload_status 		Linkup starting em1
Jan 1 04:30:26 	kernel 		em1: link state changed to UP
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	check_reload_status 		Linkup starting em0
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		em0: link state changed to UP
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	php-fpm 	72868 	/rc.linkup: DEVD Ethernet attached event for lan
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	php-fpm 	72868 	/rc.linkup: HOTPLUG: Configuring interface lan
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		em0: link state changed to DOWN
Jan 1 04:30:29 	check_reload_status 		Linkup starting em0
Jan 1 04:30:29 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	php-fpm 	17844 	/rc.linkup: Shutting down Router Advertisment daemon cleanly
Jan 1 04:30:30 	check_reload_status 		Reloading filter
Jan 1 04:30:30 	php-fpm 	67758 	/rc.linkup: DEVD Ethernet attached event for wan
Jan 1 04:30:30 	php-fpm 	67758 	/rc.linkup: HOTPLUG: Configuring interface wan
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	check_reload_status 		Linkup starting em1
Jan 1 04:30:30 	kernel 		em1: link state changed to DOWN
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	check_reload_status 		Linkup starting em0
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		em0: link state changed to UP
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		cannot forward src fe80:1::4e66:41ff:fe51:9502, dst 2601:283:4300:98cc:a236:9fff:fe06:11bf, nxt 58, rcvif em0, outif em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	check_reload_status 		Linkup starting em1
Jan 1 04:30:36 	kernel 		em1: link state changed to UP
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	check_reload_status 		rc.newwanip starting em1
Jan 1 04:30:37 	php-fpm 	67758 	/rc.linkup: calling interface_dhcpv6_configure.
Jan 1 04:30:37 	php-fpm 	67758 	/rc.linkup: Accept router advertisements on interface em1
Jan 1 04:30:37 	php-fpm 	67758 	/rc.linkup: Starting rtsold process
Jan 1 04:30:39 	rc.gateway_alarm 	94266 	>>> Gateway alarm: WAN_DHCP (Addr:73.153.120.1 Alarm:1 RTT:7842ms RTTsd:1257ms Loss:21%)
Jan 1 04:30:39 	check_reload_status 		updating dyndns WAN_DHCP
Jan 1 04:30:39 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:39 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:30:39 	check_reload_status 		Reloading filter
Jan 1 04:30:39 	php-fpm 	67758 	/rc.linkup: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:39 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:41 	check_reload_status 		updating dyndns lan
Jan 1 04:30:41 	check_reload_status 		Reloading filter
Jan 1 04:30:41 	php-fpm 	78708 	/rc.linkup: DEVD Ethernet detached event for lan
Jan 1 04:30:41 	php-fpm 	72868 	/rc.linkup: DEVD Ethernet attached event for lan
Jan 1 04:30:41 	php-fpm 	72868 	/rc.linkup: HOTPLUG: Configuring interface lan
Jan 1 04:30:41 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:42 	rtsold 		Received RA specifying route fe80::201:5cff:fe63:b846 for interface wan(em1)
Jan 1 04:30:42 	rtsold 		Starting dhcp6 client for interface wan(em1)
Jan 1 04:30:44 	php-fpm 	72868 	/rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1514806244] unbound[20294:0] error: bind: address already in use [1514806244] unbound[20294:0] fatal error: could not open ports'
Jan 1 04:30:46 	check_reload_status 		updating dyndns wan
Jan 1 04:30:46 	check_reload_status 		Reloading filter
Jan 1 04:30:46 	php-fpm 	17844 	/rc.linkup: DEVD Ethernet detached event for wan
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: rc.newwanip: Info: starting on em1.
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: rc.newwanip: on (IP address: 73.153.120.157) (interface: WAN[wan]) (real interface: em1).
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: ROUTING: setting IPv6 default route to fe80::201:5cff:fe63:b846%em1
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: Removing static route for monitor fe80::201:5cff:fe63:b846 and adding a new route through fe80::201:5cff:fe63:b846%em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	rc.gateway_alarm 	42670 	>>> Gateway alarm: EXPRESSVPNINTERFACE_VPNV4 (Addr:10.123.2.145 Alarm:1 RTT:0ms RTTsd:0ms Loss:100%)
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:48 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	php-fpm 	72868 	/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
Jan 1 04:30:48 	php-fpm 	72868 	/rc.newwanipv6: rc.newwanipv6: Info: starting on em1.
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	php-fpm 	72868 	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2001:558:6040:82:306a:ef3f:54b:ea8f) (interface: wan) (real interface: em1).
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	rc.gateway_alarm 	55130 	>>> Gateway alarm: WAN_DHCP (Addr:73.153.120.1 Alarm:1 RTT:8471ms RTTsd:173ms Loss:33%)
Jan 1 04:30:49 	check_reload_status 		updating dyndns WAN_DHCP
Jan 1 04:30:49 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:49 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:30:49 	check_reload_status 		Reloading filter
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	php-fpm 	67758 	/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jan 1 04:30:50 	php-fpm 	67758 	OpenVPN terminate old pid: 34821
Jan 1 04:30:50 	kernel 		ovpnc1: link state changed to DOWN
Jan 1 04:30:50 	check_reload_status 		Reloading filter
Jan 1 04:30:50 	php-fpm 	67758 	OpenVPN PID written: 64524
Jan 1 04:30:50 	php-fpm 	67758 	/rc.newwanip: Creating rrd update script
Jan 1 04:30:51 	php-fpm 	17844 	/rc.linkup: Shutting down Router Advertisment daemon cleanly
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: DEVD Ethernet attached event for wan
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: HOTPLUG: Configuring interface wan
Jan 1 04:30:51 	php-fpm 	17844 	/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use EXPRESSVPNINTERFACE_VPNV4.
Jan 1 04:30:51 	check_reload_status 		rc.newwanip starting em1
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: calling interface_dhcpv6_configure.
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: Accept router advertisements on interface em1
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: Starting rtsold process
Jan 1 04:30:52 	php-fpm 	17844 	/rc.newwanip: rc.newwanip: Info: starting on em1.
Jan 1 04:30:52 	php-fpm 	17844 	/rc.newwanip: rc.newwanip: on (IP address: 73.153.120.157) (interface: WAN[wan]) (real interface: em1).
Jan 1 04:30:52 	php-fpm 	17844 	/rc.newwanip: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:52 	php-fpm 	67758 	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 73.153.120.157 -> 73.153.120.157 - Restarting packages.
Jan 1 04:30:52 	check_reload_status 		Starting packages
Jan 1 04:30:53 	php-fpm 	78708 	/rc.linkup: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:53 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:53 	php-fpm 	67758 	/rc.start_packages: Restarting/Starting all packages.
Jan 1 04:30:54 	php-fpm 	78708 	/rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1514806254] unbound[37737:0] error: bind: address already in use [1514806254] unbound[37737:0] fatal error: could not open ports'
Jan 1 04:30:54 	php-fpm 	17844 	/rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1514806254] unbound[38462:0] error: bind: address already in use [1514806254] unbound[38462:0] fatal error: could not open ports'
Jan 1 04:30:55 	php-fpm 	72868 	/rc.newwanipv6: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:55 	check_reload_status 		Reloading filter
Jan 1 04:30:56 	rtsold 		Received RA specifying route fe80::201:5cff:fe63:b846 for interface wan(em1)
Jan 1 04:30:56 	rtsold 		Starting dhcp6 client for interface wan(em1)
Jan 1 04:30:57 	check_reload_status 		updating dyndns wan
Jan 1 04:30:57 	check_reload_status 		Reloading filter
Jan 1 04:30:58 	php-fpm 	78708 	/rc.newwanipv6: rc.newwanipv6: Info: starting on em1.
Jan 1 04:30:58 	php-fpm 	78708 	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2001:558:6040:82:306a:ef3f:54b:ea8f) (interface: wan) (real interface: em1).
Jan 1 04:30:59 	php-fpm 	17844 	/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jan 1 04:30:59 	php-fpm 	17844 	OpenVPN terminate old pid: 64524
Jan 1 04:30:59 	php-fpm 	17844 	OpenVPN PID written: 70463
Jan 1 04:30:59 	check_reload_status 		Reloading filter
Jan 1 04:30:59 	php-fpm 	17844 	/rc.newwanip: Creating rrd update script
Jan 1 04:31:01 	php-fpm 	17844 	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 73.153.120.157 -> 73.153.120.157 - Restarting packages.
Jan 1 04:31:01 	check_reload_status 		Starting packages
Jan 1 04:31:01 	php-fpm 	78708 	/rc.newwanipv6: ROUTING: setting default route to 73.153.120.1
Jan 1 04:31:01 	php-fpm 	78708 	/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::201:5cff:fe63:b846%em1
Jan 1 04:31:01 	php-fpm 	78708 	/rc.newwanipv6: Removing static route for monitor fe80::201:5cff:fe63:b846 and adding a new route through fe80::201:5cff:fe63:b846%em1
Jan 1 04:31:01 	check_reload_status 		Reloading filter
Jan 1 04:31:02 	php-fpm 	87789 	/rc.start_packages: Restarting/Starting all packages.
Jan 1 04:31:05 	kernel 		ovpnc1: link state changed to UP
Jan 1 04:31:05 	check_reload_status 		rc.newwanip starting ovpnc1
Jan 1 04:31:06 	php-fpm 	87789 	/rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
Jan 1 04:31:06 	php-fpm 	87789 	/rc.newwanip: rc.newwanip: on (IP address: 10.67.2.142) (interface: EXPRESSVPNINTERFACE[opt2]) (real interface: ovpnc1).
Jan 1 04:31:06 	php-fpm 	87789 	/rc.newwanip: IP Address has changed, killing states on former IP Address 10.123.2.146.
Jan 1 04:31:07 	php-fpm 	87789 	/rc.newwanip: Removing static route for monitor fe80::201:5cff:fe63:b846 and adding a new route through fe80::201:5cff:fe63:b846%em1
Jan 1 04:31:09 	rc.gateway_alarm 	25063 	>>> Gateway alarm: EXPRESSVPNINTERFACE_VPNV4 (Addr:10.67.2.141 Alarm:1 RTT:0ms RTTsd:0ms Loss:100%)
Jan 1 04:31:09 	check_reload_status 		updating dyndns EXPRESSVPNINTERFACE_VPNV4
Jan 1 04:31:09 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:31:09 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:31:09 	check_reload_status 		Reloading filter
Jan 1 04:31:10 	php-fpm 	20000 	/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use EXPRESSVPNINTERFACE_VPNV4.
Jan 1 04:31:11 	php-fpm 	87789 	/rc.newwanip: Creating rrd update script
Jan 1 04:31:13 	php-fpm 	87789 	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.123.2.146 -> 10.67.2.142 - Restarting packages.
Jan 1 04:31:13 	check_reload_status 		Starting packages
Jan 1 04:31:14 	php-fpm 	20000 	/rc.start_packages: Restarting/Starting all packages.
Jan 1 10:20:23 	pfsense.localdomain 		nginx: 2018/01/01 10:20:23 [error] 41431#100103: *9285 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827220874 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:20:23 	pfsense.localdomain 		nginx: 2018/01/01 10:20:23 [error] 41431#100103: *9285 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827220875 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:20:24 	php-fpm 	20000 	/index.php: Successful login for user 'admin' from: 192.168.1.252
Jan 1 10:20:25 	pfsense.localdomain 		nginx: 2018/01/01 10:20:25 [error] 41431#100103: *9287 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827222805 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:20:39 	pfsense.localdomain 		nginx: 2018/01/01 10:20:39 [error] 41431#100103: *9285 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827237544 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:23:25 	pfsense.localdomain 		nginx: 2018/01/01 10:23:25 [error] 41431#100103: *9317 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827403277 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:23:31 	check_reload_status 		Syncing firewall
Jan 1 10:23:31 	syslogd 		Logging subprocess 34558 (exec /usr/local/sbin/sshlockout_pf 15) exited due to signal 15.
Jan 1 10:23:31 	syslogd 		exiting on signal 15
Jan 1 10:23:31 	syslogd 		kernel boot file is /boot/kernel/kernel
Jan 1 10:23:31 	pfsense.localdomain 		nginx: 2018/01/01 10:23:31 [error] 41431#100103: *9317 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827409474 HTTP/1.1", host: "192.168.1.1"

      OpenVPN Logs:

      Jan 1 00:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=655948382/-1 pkts=1297327/0
Jan 1 00:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 00:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 00:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 00:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 00:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 00:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 00:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 00:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 00:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 01:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=58757088/-1 pkts=206056/0
Jan 1 01:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 01:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 01:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 01:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 01:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 01:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 01:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 01:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 01:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 02:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=62952625/-1 pkts=220012/0
Jan 1 02:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 02:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 02:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 02:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 02:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 02:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 02:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 02:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 02:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 03:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=63504090/-1 pkts=213666/0
Jan 1 03:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 03:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 03:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 03:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 03:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 03:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 03:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 03:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 03:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 04:30:50 	openvpn 	34821 	event_wait : Interrupted system call (code=4)
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 10.123.0.1 10.123.2.145 255.255.255.255
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 157.97.121.51 73.153.120.1 255.255.255.255
Jan 1 04:30:50 	openvpn 	34821 	ERROR: FreeBSD route delete command failed: external program exited with error status: 1
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 0.0.0.0 10.123.2.145 128.0.0.0
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 128.0.0.0 10.123.2.145 128.0.0.0
Jan 1 04:30:50 	openvpn 	34821 	Closing TUN/TAP interface
Jan 1 04:30:50 	openvpn 	34821 	/usr/local/sbin/ovpn-linkdown ovpnc1 1500 1606 10.123.2.146 10.123.2.145 init
Jan 1 04:30:50 	openvpn 	34821 	SIGTERM[hard,] received, process exiting
Jan 1 04:30:50 	openvpn 	64493 	WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jan 1 04:30:50 	openvpn 	64493 	WARNING: file '/var/etc/openvpn/client1.up' is group or others accessible
Jan 1 04:30:50 	openvpn 	64493 	OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Nov 16 2017
Jan 1 04:30:50 	openvpn 	64493 	library versions: OpenSSL 1.0.2m-freebsd 2 Nov 2017, LZO 2.10
Jan 1 04:30:50 	openvpn 	64524 	MANAGEMENT: unix domain socket listening on /var/etc/openvpn/client1.sock
Jan 1 04:30:50 	openvpn 	64524 	WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Jan 1 04:30:50 	openvpn 	64524 	NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 1 04:30:50 	openvpn 	64524 	Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:30:50 	openvpn 	64524 	Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:30:50 	openvpn 	64524 	TCP/UDP: Preserving recently used remote address: [AF_INET]157.97.121.123:1195
Jan 1 04:30:50 	openvpn 	64524 	Socket Buffers: R=[42080->524288] S=[57344->524288]
Jan 1 04:30:50 	openvpn 	64524 	TCP/UDP: Socket bind failed on local address [AF_INET]73.153.120.157:0: Can't assign requested address (errno=49)
Jan 1 04:30:50 	openvpn 	64524 	Exiting due to fatal error
Jan 1 04:30:59 	openvpn 	70160 	WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jan 1 04:30:59 	openvpn 	70160 	WARNING: file '/var/etc/openvpn/client1.up' is group or others accessible
Jan 1 04:30:59 	openvpn 	70160 	OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Nov 16 2017
Jan 1 04:30:59 	openvpn 	70160 	library versions: OpenSSL 1.0.2m-freebsd 2 Nov 2017, LZO 2.10
Jan 1 04:30:59 	openvpn 	70463 	MANAGEMENT: unix domain socket listening on /var/etc/openvpn/client1.sock
Jan 1 04:30:59 	openvpn 	70463 	WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Jan 1 04:30:59 	openvpn 	70463 	NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 1 04:30:59 	openvpn 	70463 	Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:30:59 	openvpn 	70463 	Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:31:04 	openvpn 	70463 	TCP/UDP: Preserving recently used remote address: [AF_INET]157.97.121.45:1195
Jan 1 04:31:04 	openvpn 	70463 	Socket Buffers: R=[42080->524288] S=[57344->524288]
Jan 1 04:31:04 	openvpn 	70463 	UDPv4 link local (bound): [AF_INET]73.153.120.157:0
Jan 1 04:31:04 	openvpn 	70463 	UDPv4 link remote: [AF_INET]157.97.121.45:1195
Jan 1 04:31:04 	openvpn 	70463 	TLS: Initial packet from [AF_INET]157.97.121.45:1195, sid=a4ff038b 09919bfa
Jan 1 04:31:04 	openvpn 	70463 	WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jan 1 04:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 04:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 04:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 04:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 04:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 04:31:04 	openvpn 	70463 	[Server-1596-1a] Peer Connection Initiated with [AF_INET]157.97.121.45:1195
Jan 1 04:31:05 	openvpn 	70463 	SENT CONTROL [Server-1596-1a]: 'PUSH_REQUEST' (status=1)
Jan 1 04:31:05 	openvpn 	70463 	PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.67.0.1,route 10.67.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.67.2.142 10.67.2.141'
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: timers and/or timeouts modified
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: --ifconfig/up options modified
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: route options modified
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Jan 1 04:31:05 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 04:31:05 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:31:05 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 04:31:05 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:31:05 	openvpn 	70463 	ROUTE_GATEWAY 73.153.120.1/255.255.254.0 IFACE=em1 HWADDR=a0:36:9f:06:11:be
Jan 1 04:31:05 	openvpn 	70463 	TUN/TAP device ovpnc1 exists previously, keep at program end
Jan 1 04:31:05 	openvpn 	70463 	TUN/TAP device /dev/tun1 opened
Jan 1 04:31:05 	openvpn 	70463 	do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Jan 1 04:31:05 	openvpn 	70463 	/sbin/ifconfig ovpnc1 10.67.2.142 10.67.2.141 mtu 1500 netmask 255.255.255.255 up
Jan 1 04:31:05 	openvpn 	70463 	/usr/local/sbin/ovpn-linkup ovpnc1 1500 1606 10.67.2.142 10.67.2.141 init
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 157.97.121.45 73.153.120.1 255.255.255.255
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 0.0.0.0 10.67.2.141 128.0.0.0
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 128.0.0.0 10.67.2.141 128.0.0.0
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 10.67.0.1 10.67.2.141 255.255.255.255
Jan 1 04:31:07 	openvpn 	70463 	Initialization Sequence Completed
Jan 1 05:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=57309826/-1 pkts=186221/0
Jan 1 05:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 05:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 05:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 05:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 05:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 05:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 05:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 05:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 05:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 06:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=157402000/-1 pkts=375606/0
Jan 1 06:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 06:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 06:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 06:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 06:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 06:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 06:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 06:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 06:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 07:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=67191644/-1 pkts=228980/0
Jan 1 07:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 07:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 07:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 07:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 07:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 07:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 07:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 07:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 07:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 08:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=65796799/-1 pkts=222308/0
Jan 1 08:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 08:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 08:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 08:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 08:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 08:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 08:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 08:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 08:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 09:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=412828892/-1 pkts=682337/0
Jan 1 09:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 09:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 09:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 09:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 09:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 09:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 09:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 09:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 09:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 10:12:44 	openvpn 	70463 	FRAG TTL expired i=1
Jan 1 10:13:49 	openvpn 	70463 	FRAG TTL expired i=14
Jan 1 10:14:29 	openvpn 	70463 	FRAG TTL expired i=4
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'state 1'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'status 2'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client disconnected
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'state 1'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'status 2'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client disconnected
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: CMD 'state 1'
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: CMD 'status 2'
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: Client disconnected
Jan 1 10:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=470109623/-1 pkts=883512/0
Jan 1 10:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 10:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 10:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 10:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 10:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 10:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 10:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 10:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 10:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA

      I couldn't find a particular issue in the logs, but perhaps someone else can. This might be the key to figuring out what's going on.

      Edit: For reference, this is what the last few days looked like:

      1 Reply Last reply Reply Quote 0
      • C
        Chillstice
        last edited by

        Is there anything wrong with my configuration?

        1 Reply Last reply Reply Quote 0
        • L
          lovan6
          last edited by

          I am also using Expessvpn and I am 14K miles away from the nearest west coast server. It helps if your CPU supports Intel AES New Instructions.

          On my Cryptographic settings, I use  Hardware Crytpo=BSD Cryptodev engine.

          My VPN speed and latency depends on the time of the day. I do not expect to be consistent due to my distance. On my 50/50 symmetrical fiber connection, I get 40 Mbps downlink / 20 Mbps uplink and latency of 151.

          I use ExpressVPN for geolocation blocking on my streaming devices such as  Roku and Apple tv, Banking and shopping online on certain devices. I leave the rest connected to my local ISP.

          Expressvpn customer support does know anything about Pfsense and they would just provide you a link on how to install Pfsense on Expressvpn.

          1 Reply Last reply Reply Quote 0
          • C
            Chillstice
            last edited by

            I will continue testing and recording data. I'm goijg to try the ExpressVPN support again and see if they can find anything. I still have about 25 days out of my 30 day risk-free trial period. If this doesn't improve I can try another VPN service.

            1 Reply Last reply Reply Quote 0
            • B
              bcruze
              last edited by

              I’m having the same issue with BOTH PIA and nordvpn currently..

              All my setups are correct but after 11am each day or slightly later the connection goes to crap… devices connected to the wan gateway are fine.

              I’m at a total loss on how to fix this

              1 Reply Last reply Reply Quote 0
              • C
                Chillstice
                last edited by

                @bcruze:

                I’m having the same issue with BOTH PIA and nordvpn currently..

                All my setups are correct but after 11am each day or slightly later the connection goes to crap… devices connected to the wan gateway are fine.

                I’m at a total loss on how to fix this

                Glad to hear that there are others encountering similar problems. This is no longer an isolated case.

                1 Reply Last reply Reply Quote 0
                • C
                  Chillstice
                  last edited by

                  Could this be part of the problem?

                  1 Reply Last reply Reply Quote 0
                  • B
                    bcruze
                    last edited by

                    @Chillstice:

                    Could this be part of the problem?

                    You need a aes ni compatible processor

                    Mine is and on or off it doesn’t help or hurt speeds

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      If you are seeing anything so extreme it has nothing whatsoever to do with AES-NI being present or not.

                      If it works and is fast, then works and is slow with no changes, There is probably not an OpenVPN setting that will help.

                      Hard to say what is happening.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • C
                        Chillstice
                        last edited by

                        Alright, so I had temporarily disabled the VPN routing for the last couple days and decided to test it again. Without changing any settings other than enabling the VPN routing, I'm suddenly getting the best speeds I've ever gotten over a VPN.

                        http://beta.speedtest.net/result/6924202031

                        IDK what's up. Maybe it's something out of my crontrol i.e. ExpressVPN traffic shaping. Or even something Comcast is doing. Either way, if it stays this way I'm happy.

                        1 Reply Last reply Reply Quote 0
                        • B
                          bcruze
                          last edited by

                          i have been trying to get PIA and nordvpn on 256bitCBC encryption to stay at at least 30% below my full internet connection and it has been impossible for the past few weeks.    i even bought a new zoom 5370 modem.  to replace the arris provided by my ISP.  still the same issue!

                          PIA connects at SHA256.    Nord is SHA512.    both AES 256CBC though

                          what will happen is it will stay connected all night.  work from 6am until about 10am.  then my speeds will drop to the 2-5Mb area ALL during the day.

                          i know what your thinking its my ISP.    well if i disconnect my speeds are still FULL download and uploads provided by my ISP.

                          Nordvpn replied last night saying its a limitation of my router.  SG2220  1.7Ghz.  i don't believe that is the case.  cisco lower end equipment is that same specs and it does not have this issue.
                          i am going to guess this is a Openvpn issue/  BSD issue on 2.42 p1 that is out of my control until someone who knows what they are doing trys this and see's the issue

                          until then i am having better luck and better support from PIA.  so i will keep that config file running on this router

                          1 Reply Last reply Reply Quote 0
                          • B
                            bcruze
                            last edited by

                            its like clock work.  10am EST.  i have been remoted in to my mac from work.        been getting 100Mb down for about an hour connected to PIA.  10am hits and i am now limited to less than 5Mb down 5Mb up.

                            doesn't matter what server i connect to.    disconnect and its back to normal speeds

                            1 Reply Last reply Reply Quote 0
                            • C
                              Chillstice
                              last edited by

                              Who is your ISP? With the current state of Net Neutrality large ISPs promise not to throttle or block certain traffic, but they totally have the ability to do just that, including traffit to and from VPN servers. I thought Comcast was the worst offender, but there are lesser-known ISPs like Frontier that are far more atrocious. Even going as far as to charge their customers extra fees for roadwork. I wouldn't be surprised if ISPs begin throttling or even blocking connections to VPNs if Net Neutrality dies.

                              1 Reply Last reply Reply Quote 0
                              • B
                                bcruze
                                last edited by

                                TWC / spectrum.  i hear you on that.

                                i guess time will tell when more people start to experience this

                                1 Reply Last reply Reply Quote 0
                                • C
                                  Chillstice
                                  last edited by

                                  Okay, so this is weird. The last two days using ExpressVPN has been a flawless experience. I've been consistently getting the last speed I reported (10-12 Ping, 140-150mbps Download, 9-10mbps Upload) however something in the last 10 hours has changed and now the speed is less than half that. It's not as slow at the title of the thread advertises, but it's nowhere near what it was the last two days. I was able to capture the pfSense logs of the last 10 hours and I will gladly share it here for people to pick through.

                                  Logs from last successful speed-test until now:
                                  System Logs:

                                  Jan 1 04:30:04 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Emerging Threats Open rules are up to date...
Jan 1 04:30:05 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Snort VRT rules are up to date...
Jan 1 04:30:05 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] There is a new set of Snort GPLv2 Community Rules posted. Downloading community-rules.tar.gz...
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Snort GPLv2 Community Rules file update downloaded successfully.
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Hide Deprecated Rules is enabled. Removing obsoleted rules categories.
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Removed 0 obsoleted rules category files.
Jan 1 04:30:08 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Updating rules configuration for: WAN ...
Jan 1 04:30:11 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Building new sid-msg.map file for WAN...
Jan 1 04:30:11 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Updating rules configuration for: LAN ...
Jan 1 04:30:14 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Building new sid-msg.map file for LAN...
Jan 1 04:30:14 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Updating rules configuration for: EXPRESSVPNINTERFACE ...
Jan 1 04:30:17 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Building new sid-msg.map file for EXPRESSVPNINTERFACE...
Jan 1 04:30:17 	SuricataStartup 	60631 	Suricata STOP for WAN(5050_em1)...
Jan 1 04:30:17 	kernel 		em1: promiscuous mode disabled
Jan 1 04:30:19 	SuricataStartup 	62442 	Suricata STOP for LAN(10768_em0)...
Jan 1 04:30:19 	kernel 		em0: promiscuous mode disabled
Jan 1 04:30:21 	SuricataStartup 	64089 	Suricata STOP for ExpressVPN(5448_ovpnc1)...
Jan 1 04:30:21 	kernel 		ovpnc1: promiscuous mode disabled
Jan 1 04:30:23 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] Suricata has restarted with your new set of rules...
Jan 1 04:30:23 	php-cgi 		suricata_check_for_rule_updates.php: [Suricata] The Rules update has finished.
Jan 1 04:30:23 	SuricataStartup 	65750 	Suricata START for WAN(5050_em1)...
Jan 1 04:30:23 	check_reload_status 		Syncing firewall
Jan 1 04:30:23 	kernel 		em1: link state changed to DOWN
Jan 1 04:30:23 	kernel 		em1: promiscuous mode enabled
Jan 1 04:30:23 	check_reload_status 		Linkup starting em1
Jan 1 04:30:24 	SuricataStartup 	66916 	Suricata START for LAN(10768_em0)...
Jan 1 04:30:24 	php-fpm 	17844 	/rc.linkup: DEVD Ethernet detached event for wan
Jan 1 04:30:24 	check_reload_status 		Linkup starting em0
Jan 1 04:30:24 	kernel 		em0: link state changed to DOWN
Jan 1 04:30:24 	kernel 		em0: promiscuous mode enabled
Jan 1 04:30:25 	SuricataStartup 	68226 	Suricata START for ExpressVPN(5448_ovpnc1)...
Jan 1 04:30:25 	kernel 		ovpnc1: promiscuous mode enabled
Jan 1 04:30:25 	php-fpm 	67758 	/rc.linkup: DEVD Ethernet detached event for lan
Jan 1 04:30:26 	check_reload_status 		Reloading filter
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	check_reload_status 		Linkup starting em1
Jan 1 04:30:26 	kernel 		em1: link state changed to UP
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:26 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:27 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	check_reload_status 		Linkup starting em0
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		em0: link state changed to UP
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:28 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	php-fpm 	72868 	/rc.linkup: DEVD Ethernet attached event for lan
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	php-fpm 	72868 	/rc.linkup: HOTPLUG: Configuring interface lan
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		em0: link state changed to DOWN
Jan 1 04:30:29 	check_reload_status 		Linkup starting em0
Jan 1 04:30:29 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:29 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	php-fpm 	17844 	/rc.linkup: Shutting down Router Advertisment daemon cleanly
Jan 1 04:30:30 	check_reload_status 		Reloading filter
Jan 1 04:30:30 	php-fpm 	67758 	/rc.linkup: DEVD Ethernet attached event for wan
Jan 1 04:30:30 	php-fpm 	67758 	/rc.linkup: HOTPLUG: Configuring interface wan
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	check_reload_status 		Linkup starting em1
Jan 1 04:30:30 	kernel 		em1: link state changed to DOWN
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:30 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:31 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	check_reload_status 		Linkup starting em0
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		em0: link state changed to UP
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:32 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:33 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:34 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		cannot forward src fe80:1::4e66:41ff:fe51:9502, dst 2601:283:4300:98cc:a236:9fff:fe06:11bf, nxt 58, rcvif em0, outif em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:35 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	check_reload_status 		Linkup starting em1
Jan 1 04:30:36 	kernel 		em1: link state changed to UP
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:36 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:37 	check_reload_status 		rc.newwanip starting em1
Jan 1 04:30:37 	php-fpm 	67758 	/rc.linkup: calling interface_dhcpv6_configure.
Jan 1 04:30:37 	php-fpm 	67758 	/rc.linkup: Accept router advertisements on interface em1
Jan 1 04:30:37 	php-fpm 	67758 	/rc.linkup: Starting rtsold process
Jan 1 04:30:39 	rc.gateway_alarm 	94266 	>>> Gateway alarm: WAN_DHCP (Addr:73.153.120.1 Alarm:1 RTT:7842ms RTTsd:1257ms Loss:21%)
Jan 1 04:30:39 	check_reload_status 		updating dyndns WAN_DHCP
Jan 1 04:30:39 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:39 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:30:39 	check_reload_status 		Reloading filter
Jan 1 04:30:39 	php-fpm 	67758 	/rc.linkup: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:39 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:41 	check_reload_status 		updating dyndns lan
Jan 1 04:30:41 	check_reload_status 		Reloading filter
Jan 1 04:30:41 	php-fpm 	78708 	/rc.linkup: DEVD Ethernet detached event for lan
Jan 1 04:30:41 	php-fpm 	72868 	/rc.linkup: DEVD Ethernet attached event for lan
Jan 1 04:30:41 	php-fpm 	72868 	/rc.linkup: HOTPLUG: Configuring interface lan
Jan 1 04:30:41 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:42 	rtsold 		Received RA specifying route fe80::201:5cff:fe63:b846 for interface wan(em1)
Jan 1 04:30:42 	rtsold 		Starting dhcp6 client for interface wan(em1)
Jan 1 04:30:44 	php-fpm 	72868 	/rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1514806244] unbound[20294:0] error: bind: address already in use [1514806244] unbound[20294:0] fatal error: could not open ports'
Jan 1 04:30:46 	check_reload_status 		updating dyndns wan
Jan 1 04:30:46 	check_reload_status 		Reloading filter
Jan 1 04:30:46 	php-fpm 	17844 	/rc.linkup: DEVD Ethernet detached event for wan
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: rc.newwanip: Info: starting on em1.
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: rc.newwanip: on (IP address: 73.153.120.157) (interface: WAN[wan]) (real interface: em1).
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: ROUTING: setting IPv6 default route to fe80::201:5cff:fe63:b846%em1
Jan 1 04:30:46 	php-fpm 	67758 	/rc.newwanip: Removing static route for monitor fe80::201:5cff:fe63:b846 and adding a new route through fe80::201:5cff:fe63:b846%em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:47 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	rc.gateway_alarm 	42670 	>>> Gateway alarm: EXPRESSVPNINTERFACE_VPNV4 (Addr:10.123.2.145 Alarm:1 RTT:0ms RTTsd:0ms Loss:100%)
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:48 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	php-fpm 	72868 	/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
Jan 1 04:30:48 	php-fpm 	72868 	/rc.newwanipv6: rc.newwanipv6: Info: starting on em1.
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	php-fpm 	72868 	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2001:558:6040:82:306a:ef3f:54b:ea8f) (interface: wan) (real interface: em1).
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:48 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	rc.gateway_alarm 	55130 	>>> Gateway alarm: WAN_DHCP (Addr:73.153.120.1 Alarm:1 RTT:8471ms RTTsd:173ms Loss:33%)
Jan 1 04:30:49 	check_reload_status 		updating dyndns WAN_DHCP
Jan 1 04:30:49 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:49 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:30:49 	check_reload_status 		Reloading filter
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:49 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	kernel 		arpresolve: can't allocate llinfo for 73.153.120.1 on em1
Jan 1 04:30:50 	php-fpm 	67758 	/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jan 1 04:30:50 	php-fpm 	67758 	OpenVPN terminate old pid: 34821
Jan 1 04:30:50 	kernel 		ovpnc1: link state changed to DOWN
Jan 1 04:30:50 	check_reload_status 		Reloading filter
Jan 1 04:30:50 	php-fpm 	67758 	OpenVPN PID written: 64524
Jan 1 04:30:50 	php-fpm 	67758 	/rc.newwanip: Creating rrd update script
Jan 1 04:30:51 	php-fpm 	17844 	/rc.linkup: Shutting down Router Advertisment daemon cleanly
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: DEVD Ethernet attached event for wan
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: HOTPLUG: Configuring interface wan
Jan 1 04:30:51 	php-fpm 	17844 	/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use EXPRESSVPNINTERFACE_VPNV4.
Jan 1 04:30:51 	check_reload_status 		rc.newwanip starting em1
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: calling interface_dhcpv6_configure.
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: Accept router advertisements on interface em1
Jan 1 04:30:51 	php-fpm 	78708 	/rc.linkup: Starting rtsold process
Jan 1 04:30:52 	php-fpm 	17844 	/rc.newwanip: rc.newwanip: Info: starting on em1.
Jan 1 04:30:52 	php-fpm 	17844 	/rc.newwanip: rc.newwanip: on (IP address: 73.153.120.157) (interface: WAN[wan]) (real interface: em1).
Jan 1 04:30:52 	php-fpm 	17844 	/rc.newwanip: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:52 	php-fpm 	67758 	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 73.153.120.157 -> 73.153.120.157 - Restarting packages.
Jan 1 04:30:52 	check_reload_status 		Starting packages
Jan 1 04:30:53 	php-fpm 	78708 	/rc.linkup: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:53 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:30:53 	php-fpm 	67758 	/rc.start_packages: Restarting/Starting all packages.
Jan 1 04:30:54 	php-fpm 	78708 	/rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1514806254] unbound[37737:0] error: bind: address already in use [1514806254] unbound[37737:0] fatal error: could not open ports'
Jan 1 04:30:54 	php-fpm 	17844 	/rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1514806254] unbound[38462:0] error: bind: address already in use [1514806254] unbound[38462:0] fatal error: could not open ports'
Jan 1 04:30:55 	php-fpm 	72868 	/rc.newwanipv6: ROUTING: setting default route to 73.153.120.1
Jan 1 04:30:55 	check_reload_status 		Reloading filter
Jan 1 04:30:56 	rtsold 		Received RA specifying route fe80::201:5cff:fe63:b846 for interface wan(em1)
Jan 1 04:30:56 	rtsold 		Starting dhcp6 client for interface wan(em1)
Jan 1 04:30:57 	check_reload_status 		updating dyndns wan
Jan 1 04:30:57 	check_reload_status 		Reloading filter
Jan 1 04:30:58 	php-fpm 	78708 	/rc.newwanipv6: rc.newwanipv6: Info: starting on em1.
Jan 1 04:30:58 	php-fpm 	78708 	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2001:558:6040:82:306a:ef3f:54b:ea8f) (interface: wan) (real interface: em1).
Jan 1 04:30:59 	php-fpm 	17844 	/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jan 1 04:30:59 	php-fpm 	17844 	OpenVPN terminate old pid: 64524
Jan 1 04:30:59 	php-fpm 	17844 	OpenVPN PID written: 70463
Jan 1 04:30:59 	check_reload_status 		Reloading filter
Jan 1 04:30:59 	php-fpm 	17844 	/rc.newwanip: Creating rrd update script
Jan 1 04:31:01 	php-fpm 	17844 	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 73.153.120.157 -> 73.153.120.157 - Restarting packages.
Jan 1 04:31:01 	check_reload_status 		Starting packages
Jan 1 04:31:01 	php-fpm 	78708 	/rc.newwanipv6: ROUTING: setting default route to 73.153.120.1
Jan 1 04:31:01 	php-fpm 	78708 	/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::201:5cff:fe63:b846%em1
Jan 1 04:31:01 	php-fpm 	78708 	/rc.newwanipv6: Removing static route for monitor fe80::201:5cff:fe63:b846 and adding a new route through fe80::201:5cff:fe63:b846%em1
Jan 1 04:31:01 	check_reload_status 		Reloading filter
Jan 1 04:31:02 	php-fpm 	87789 	/rc.start_packages: Restarting/Starting all packages.
Jan 1 04:31:05 	kernel 		ovpnc1: link state changed to UP
Jan 1 04:31:05 	check_reload_status 		rc.newwanip starting ovpnc1
Jan 1 04:31:06 	php-fpm 	87789 	/rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
Jan 1 04:31:06 	php-fpm 	87789 	/rc.newwanip: rc.newwanip: on (IP address: 10.67.2.142) (interface: EXPRESSVPNINTERFACE[opt2]) (real interface: ovpnc1).
Jan 1 04:31:06 	php-fpm 	87789 	/rc.newwanip: IP Address has changed, killing states on former IP Address 10.123.2.146.
Jan 1 04:31:07 	php-fpm 	87789 	/rc.newwanip: Removing static route for monitor fe80::201:5cff:fe63:b846 and adding a new route through fe80::201:5cff:fe63:b846%em1
Jan 1 04:31:09 	rc.gateway_alarm 	25063 	>>> Gateway alarm: EXPRESSVPNINTERFACE_VPNV4 (Addr:10.67.2.141 Alarm:1 RTT:0ms RTTsd:0ms Loss:100%)
Jan 1 04:31:09 	check_reload_status 		updating dyndns EXPRESSVPNINTERFACE_VPNV4
Jan 1 04:31:09 	check_reload_status 		Restarting ipsec tunnels
Jan 1 04:31:09 	check_reload_status 		Restarting OpenVPN tunnels/interfaces
Jan 1 04:31:09 	check_reload_status 		Reloading filter
Jan 1 04:31:10 	php-fpm 	20000 	/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use EXPRESSVPNINTERFACE_VPNV4.
Jan 1 04:31:11 	php-fpm 	87789 	/rc.newwanip: Creating rrd update script
Jan 1 04:31:13 	php-fpm 	87789 	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.123.2.146 -> 10.67.2.142 - Restarting packages.
Jan 1 04:31:13 	check_reload_status 		Starting packages
Jan 1 04:31:14 	php-fpm 	20000 	/rc.start_packages: Restarting/Starting all packages.
Jan 1 10:20:23 	pfsense.localdomain 		nginx: 2018/01/01 10:20:23 [error] 41431#100103: *9285 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827220874 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:20:23 	pfsense.localdomain 		nginx: 2018/01/01 10:20:23 [error] 41431#100103: *9285 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827220875 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:20:24 	php-fpm 	20000 	/index.php: Successful login for user 'admin' from: 192.168.1.252
Jan 1 10:20:25 	pfsense.localdomain 		nginx: 2018/01/01 10:20:25 [error] 41431#100103: *9287 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827222805 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:20:39 	pfsense.localdomain 		nginx: 2018/01/01 10:20:39 [error] 41431#100103: *9285 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827237544 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:23:25 	pfsense.localdomain 		nginx: 2018/01/01 10:23:25 [error] 41431#100103: *9317 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827403277 HTTP/1.1", host: "192.168.1.1"
Jan 1 10:23:31 	check_reload_status 		Syncing firewall
Jan 1 10:23:31 	syslogd 		Logging subprocess 34558 (exec /usr/local/sbin/sshlockout_pf 15) exited due to signal 15.
Jan 1 10:23:31 	syslogd 		exiting on signal 15
Jan 1 10:23:31 	syslogd 		kernel boot file is /boot/kernel/kernel
Jan 1 10:23:31 	pfsense.localdomain 		nginx: 2018/01/01 10:23:31 [error] 41431#100103: *9317 open() "/usr/local/www/robots.txt" failed (2: No such file or directory), client: 192.168.1.252, server: , request: "GET /robots.txt?1514827409474 HTTP/1.1", host: "192.168.1.1"

                                  OpenVPN Logs:

                                  Jan 1 00:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=655948382/-1 pkts=1297327/0
Jan 1 00:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 00:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 00:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 00:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 00:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 00:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 00:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 00:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 00:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 01:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=58757088/-1 pkts=206056/0
Jan 1 01:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 01:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 01:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 01:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 01:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 01:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 01:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 01:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 01:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 02:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=62952625/-1 pkts=220012/0
Jan 1 02:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 02:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 02:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 02:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 02:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 02:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 02:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 02:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 02:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 03:30:52 	openvpn 	34821 	TLS: soft reset sec=0 bytes=63504090/-1 pkts=213666/0
Jan 1 03:30:52 	openvpn 	34821 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 03:30:52 	openvpn 	34821 	VERIFY OK: nsCertType=SERVER
Jan 1 03:30:52 	openvpn 	34821 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 03:30:52 	openvpn 	34821 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1597-1a, emailAddress=support@expressvpn.com
Jan 1 03:30:52 	openvpn 	34821 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 03:30:52 	openvpn 	34821 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 03:30:52 	openvpn 	34821 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 03:30:52 	openvpn 	34821 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 03:30:52 	openvpn 	34821 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 04:30:50 	openvpn 	34821 	event_wait : Interrupted system call (code=4)
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 10.123.0.1 10.123.2.145 255.255.255.255
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 157.97.121.51 73.153.120.1 255.255.255.255
Jan 1 04:30:50 	openvpn 	34821 	ERROR: FreeBSD route delete command failed: external program exited with error status: 1
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 0.0.0.0 10.123.2.145 128.0.0.0
Jan 1 04:30:50 	openvpn 	34821 	/sbin/route delete -net 128.0.0.0 10.123.2.145 128.0.0.0
Jan 1 04:30:50 	openvpn 	34821 	Closing TUN/TAP interface
Jan 1 04:30:50 	openvpn 	34821 	/usr/local/sbin/ovpn-linkdown ovpnc1 1500 1606 10.123.2.146 10.123.2.145 init
Jan 1 04:30:50 	openvpn 	34821 	SIGTERM[hard,] received, process exiting
Jan 1 04:30:50 	openvpn 	64493 	WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jan 1 04:30:50 	openvpn 	64493 	WARNING: file '/var/etc/openvpn/client1.up' is group or others accessible
Jan 1 04:30:50 	openvpn 	64493 	OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Nov 16 2017
Jan 1 04:30:50 	openvpn 	64493 	library versions: OpenSSL 1.0.2m-freebsd 2 Nov 2017, LZO 2.10
Jan 1 04:30:50 	openvpn 	64524 	MANAGEMENT: unix domain socket listening on /var/etc/openvpn/client1.sock
Jan 1 04:30:50 	openvpn 	64524 	WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Jan 1 04:30:50 	openvpn 	64524 	NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 1 04:30:50 	openvpn 	64524 	Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:30:50 	openvpn 	64524 	Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:30:50 	openvpn 	64524 	TCP/UDP: Preserving recently used remote address: [AF_INET]157.97.121.123:1195
Jan 1 04:30:50 	openvpn 	64524 	Socket Buffers: R=[42080->524288] S=[57344->524288]
Jan 1 04:30:50 	openvpn 	64524 	TCP/UDP: Socket bind failed on local address [AF_INET]73.153.120.157:0: Can't assign requested address (errno=49)
Jan 1 04:30:50 	openvpn 	64524 	Exiting due to fatal error
Jan 1 04:30:59 	openvpn 	70160 	WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jan 1 04:30:59 	openvpn 	70160 	WARNING: file '/var/etc/openvpn/client1.up' is group or others accessible
Jan 1 04:30:59 	openvpn 	70160 	OpenVPN 2.4.4 amd64-portbld-freebsd11.1 [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] built on Nov 16 2017
Jan 1 04:30:59 	openvpn 	70160 	library versions: OpenSSL 1.0.2m-freebsd 2 Nov 2017, LZO 2.10
Jan 1 04:30:59 	openvpn 	70463 	MANAGEMENT: unix domain socket listening on /var/etc/openvpn/client1.sock
Jan 1 04:30:59 	openvpn 	70463 	WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Jan 1 04:30:59 	openvpn 	70463 	NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 1 04:30:59 	openvpn 	70463 	Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:30:59 	openvpn 	70463 	Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:31:04 	openvpn 	70463 	TCP/UDP: Preserving recently used remote address: [AF_INET]157.97.121.45:1195
Jan 1 04:31:04 	openvpn 	70463 	Socket Buffers: R=[42080->524288] S=[57344->524288]
Jan 1 04:31:04 	openvpn 	70463 	UDPv4 link local (bound): [AF_INET]73.153.120.157:0
Jan 1 04:31:04 	openvpn 	70463 	UDPv4 link remote: [AF_INET]157.97.121.45:1195
Jan 1 04:31:04 	openvpn 	70463 	TLS: Initial packet from [AF_INET]157.97.121.45:1195, sid=a4ff038b 09919bfa
Jan 1 04:31:04 	openvpn 	70463 	WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jan 1 04:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 04:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 04:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 04:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 04:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 04:31:04 	openvpn 	70463 	[Server-1596-1a] Peer Connection Initiated with [AF_INET]157.97.121.45:1195
Jan 1 04:31:05 	openvpn 	70463 	SENT CONTROL [Server-1596-1a]: 'PUSH_REQUEST' (status=1)
Jan 1 04:31:05 	openvpn 	70463 	PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.67.0.1,route 10.67.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.67.2.142 10.67.2.141'
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: timers and/or timeouts modified
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: --ifconfig/up options modified
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: route options modified
Jan 1 04:31:05 	openvpn 	70463 	OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Jan 1 04:31:05 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 04:31:05 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:31:05 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 04:31:05 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 04:31:05 	openvpn 	70463 	ROUTE_GATEWAY 73.153.120.1/255.255.254.0 IFACE=em1 HWADDR=a0:36:9f:06:11:be
Jan 1 04:31:05 	openvpn 	70463 	TUN/TAP device ovpnc1 exists previously, keep at program end
Jan 1 04:31:05 	openvpn 	70463 	TUN/TAP device /dev/tun1 opened
Jan 1 04:31:05 	openvpn 	70463 	do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Jan 1 04:31:05 	openvpn 	70463 	/sbin/ifconfig ovpnc1 10.67.2.142 10.67.2.141 mtu 1500 netmask 255.255.255.255 up
Jan 1 04:31:05 	openvpn 	70463 	/usr/local/sbin/ovpn-linkup ovpnc1 1500 1606 10.67.2.142 10.67.2.141 init
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 157.97.121.45 73.153.120.1 255.255.255.255
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 0.0.0.0 10.67.2.141 128.0.0.0
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 128.0.0.0 10.67.2.141 128.0.0.0
Jan 1 04:31:07 	openvpn 	70463 	/sbin/route add -net 10.67.0.1 10.67.2.141 255.255.255.255
Jan 1 04:31:07 	openvpn 	70463 	Initialization Sequence Completed
Jan 1 05:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=57309826/-1 pkts=186221/0
Jan 1 05:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 05:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 05:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 05:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 05:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 05:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 05:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 05:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 05:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 06:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=157402000/-1 pkts=375606/0
Jan 1 06:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 06:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 06:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 06:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 06:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 06:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 06:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 06:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 06:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 07:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=67191644/-1 pkts=228980/0
Jan 1 07:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 07:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 07:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 07:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 07:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 07:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 07:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 07:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 07:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 08:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=65796799/-1 pkts=222308/0
Jan 1 08:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 08:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 08:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 08:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 08:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 08:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 08:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 08:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 08:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 09:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=412828892/-1 pkts=682337/0
Jan 1 09:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 09:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 09:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 09:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 09:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 09:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 09:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 09:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 09:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jan 1 10:12:44 	openvpn 	70463 	FRAG TTL expired i=1
Jan 1 10:13:49 	openvpn 	70463 	FRAG TTL expired i=14
Jan 1 10:14:29 	openvpn 	70463 	FRAG TTL expired i=4
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'state 1'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'status 2'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client disconnected
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'state 1'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: CMD 'status 2'
Jan 1 10:20:24 	openvpn 	70463 	MANAGEMENT: Client disconnected
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: CMD 'state 1'
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: CMD 'status 2'
Jan 1 10:20:30 	openvpn 	70463 	MANAGEMENT: Client disconnected
Jan 1 10:31:04 	openvpn 	70463 	TLS: soft reset sec=0 bytes=470109623/-1 pkts=883512/0
Jan 1 10:31:04 	openvpn 	70463 	VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jan 1 10:31:04 	openvpn 	70463 	VERIFY OK: nsCertType=SERVER
Jan 1 10:31:04 	openvpn 	70463 	VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 10:31:04 	openvpn 	70463 	VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1596-1a, emailAddress=support@expressvpn.com
Jan 1 10:31:04 	openvpn 	70463 	Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 10:31:04 	openvpn 	70463 	Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 10:31:04 	openvpn 	70463 	Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jan 1 10:31:04 	openvpn 	70463 	Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jan 1 10:31:04 	openvpn 	70463 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA

                                  I couldn't find a particular issue in the logs, but perhaps someone else can. This might be the key to figuring out what's going on.

                                  Edit: For reference, this is what the last few days looked like:

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    Chillstice
                                    last edited by

                                    I think I finally figured it out. Although ExpressVPN was convincing me that there's no exceptional load on the Denver VPN server, I think there's something severely wrong with it. I'm starting to get sub-mbps download speeds again no matter what I do. I tried using their desktop client for testing and found that the Denver VPN server severely under-performed. Switching to the next closest server - Dallas - has yielded the following speed:
                                    http://beta.speedtest.net/result/6927565764

                                    It's only an extra 10-15ms latency (which is still incredible) but I get my speed back.

                                    Although a large selling point for ExpressVPN for me was the fact that they had a VPN server in my state, I found that the Dalas 2 server is far superior. Too bad they won't admit that there are problems with the Denver server.

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bcruze
                                      last edited by

                                      you Sir are on to something.

                                      for PIA i have been using east coast primarily but using nslookup to find the different address and then connecting statically when one of them is slow.

                                      i tried another coast and i have faster speed tests than ever.  WTH .

                                      i think i'll leave this for a while.  its ALOT harder to find where the nordvpn servers are as they want you to use their tool to "automagically" find a server for you.    either way i have not been happy with their service i may end up dropping Nord.

                                      i never even thought to try another location… i appreciate the post

                                      1 Reply Last reply Reply Quote 0
                                      • DerelictD
                                        Derelict LAYER 8 Netgate
                                        last edited by

                                        Not sure how anyone actually thought that these commodity VPN providers had a sustainable business model as traffic/subscribership increased.

                                        Chattanooga, Tennessee, USA
                                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          Chillstice
                                          last edited by

                                          k

                                          1 Reply Last reply Reply Quote 0
                                          • W
                                            wayne622
                                            last edited by

                                            What are you using for your monitor up for the ExpressVPN gateway? I’m trying them out and every IP I put in to monitor I am getting a high packet loss and the gateway showing offline.

                                            Also, for the other op in order to get the locations of the NordVPN servers you have to chat with support and they will give a listing of where the servers are located.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.