Unstable internet since 2.2.4



  • Hey guys, ever since updating to 2.2.4 it seems my internet has been unstable.  The gateway monitor always says there is packet loss (right now 6%) and the WAN and OPENVPN go offline then back online regularly.  Is there still the Apinger problem or has that been fixed?  Here is a system log, not sure how to interpret it, any help would be much appreciated.

    Here is the General Log

    Oct 28 05:45:38 php-fpm[67542]: /rc.start_packages: Restarting/Starting all packages.
    Oct 28 05:45:38 check_reload_status: updating dyndns AirVPN_WAN
    Oct 28 05:45:38 check_reload_status: Restarting ipsec tunnels
    Oct 28 05:45:38 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Oct 28 05:45:38 check_reload_status: Reloading filter
    Oct 28 05:45:39 php-fpm[1399]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use AirVPN_WAN.
    Oct 28 05:45:41 kernel: ovpnc1: link state changed to UP
    Oct 28 05:45:41 check_reload_status: rc.newwanip starting ovpnc1
    Oct 28 05:45:42 php-fpm[19321]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
    Oct 28 05:45:42 php-fpm[19321]: /rc.newwanip: rc.newwanip: on (IP address: 10.4.0.195) (interface: AIRVPN_WAN[opt1]) (real interface: ovpnc1).
    Oct 28 05:45:43 php-fpm[19321]: /rc.newwanip: ROUTING: setting default route to 10.4.0.1
    Oct 28 05:45:44 php-fpm[19321]: /rc.newwanip: Ignoring IPsec reload since there are no tunnels on interface opt1
    Oct 28 05:45:44 php-fpm[19321]: /rc.newwanip: Creating rrd update script
    Oct 28 05:45:46 php-fpm[19321]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.4.0.195 -> 10.4.0.195 - Restarting packages.
    Oct 28 05:45:46 check_reload_status: Starting packages
    Oct 28 05:45:47 php-fpm[62624]: /rc.start_packages: Restarting/Starting all packages.
    Oct 28 05:45:50 check_reload_status: updating dyndns AirVPN_WAN
    Oct 28 05:45:50 check_reload_status: Restarting ipsec tunnels
    Oct 28 05:45:50 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Oct 28 05:45:50 check_reload_status: Reloading filter
    Oct 28 05:45:52 php-fpm[62624]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use AirVPN_WAN.
    Oct 28 05:45:52 check_reload_status: updating dyndns AirVPN_WAN
    Oct 28 05:45:52 check_reload_status: Restarting ipsec tunnels
    Oct 28 05:45:52 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Oct 28 05:45:52 check_reload_status: Reloading filter
    Oct 28 05:45:53 php-fpm[62624]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use AirVPN_WAN.
    Oct 28 05:50:01 check_reload_status: Syncing firewall
    Oct 28 05:52:43 check_reload_status: Syncing firewall
    Oct 28 05:52:43 check_reload_status: Reloading filter
    Oct 28 05:52:46 php-fpm[57262]: /system_advanced_admin.php: webConfigurator configuration has changed. Restarting webConfigurator.
    Oct 28 05:52:46 check_reload_status: webConfigurator restart in progress
    Oct 28 05:52:48 lighttpd[67894]: (log.c.164) server started
    Oct 28 05:52:48 php-fpm[62919]: /rc.restart_webgui: Creating rrd update script
    Oct 28 05:54:01 check_reload_status: Syncing firewall
    Oct 28 05:54:01 check_reload_status: Reloading filter
    Oct 28 06:57:02 check_reload_status: updating dyndns AirVPN_WAN
    Oct 28 06:57:02 check_reload_status: Restarting ipsec tunnels
    Oct 28 06:57:02 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Oct 28 06:57:02 check_reload_status: Reloading filter
    Oct 28 06:57:03 php-fpm[82663]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use AirVPN_WAN.
    Oct 28 06:57:43 check_reload_status: updating dyndns AirVPN_WAN
    Oct 28 06:57:43 check_reload_status: Restarting ipsec tunnels
    Oct 28 06:57:43 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Oct 28 06:57:43 check_reload_status: Reloading filter
    Oct 28 06:57:44 php-fpm[51062]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use AirVPN_WAN.
    Oct 28 13:31:59 php-fpm[54882]: /index.php: Session timed out for user 'admin' from: 192.168.1.113
    Oct 28 13:32:27 php-fpm[54882]: /index.php: Successful login for user 'admin' from: 192.168.1.113
    Oct 28 13:32:27 php-fpm[54882]: /index.php: Successful login for user 'admin' from: 192.168.1.113
    Oct 29 02:15:14 php-fpm[49309]: /index.php: Successful login for user 'admin' from: 192.168.1.226
    Oct 29 02:15:14 php-fpm[49309]: /index.php: Successful login for user 'admin' from: 192.168.1.226

    Here is the Gateway Log
    Oct 29 02:32:07 apinger: SIGHUP received, reloading configuration.
    Oct 29 02:31:56 apinger: alarm canceled (config reload): AirVPN_WAN(10.4.0.1) *** down ***
    Oct 29 02:31:56 apinger: SIGHUP received, reloading configuration.
    Oct 29 02:31:56 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:55 apinger: alarm canceled: WAN_DHCP(174.1.32.1) *** down ***
    Oct 29 02:31:55 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:54 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:54 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:53 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:53 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:52 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:52 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:51 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:51 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:50 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:50 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:48 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:48 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:47 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:47 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:46 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:46 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:45 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:45 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:44 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:44 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:43 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:43 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:42 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:42 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:41 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:41 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:40 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:40 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:39 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:39 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:38 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:38 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:37 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:37 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:36 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:36 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:35 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:35 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:34 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:34 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:33 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:33 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:32 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:32 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:31 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:31 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:30 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:30 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:29 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:29 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:28 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:28 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:27 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:27 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:26 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:26 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:25 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:25 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:24 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:24 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:23 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:23 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:22 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:22 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:21 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:21 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:20 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:20 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:19 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:19 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:18 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:18 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:17 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:17 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:16 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:16 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 29 02:31:15 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:14 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:12 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:10 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:09 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:05 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:03 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:02 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:01 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:31:00 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:56 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:54 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:53 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:52 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:50 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:48 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:45 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:44 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:42 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:41 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:39 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:38 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:37 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:36 apinger: Could not bind socket on address(174.1.32.200) for monitoring address 174.1.32.1(WAN_DHCP) with error Can't assign requested address
    Oct 29 02:30:23 apinger: ALARM: WAN_DHCP(174.1.32.1) *** down ***
    Oct 29 02:30:23 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 29 02:21:48 apinger: Starting Alarm Pinger, apinger(63466)
    Oct 29 02:21:44 apinger: Exiting on signal 15.
    Oct 28 06:57:33 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** loss ***
    Oct 28 06:56:52 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** loss ***
    Oct 28 05:50:32 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:50:28 apinger: Starting Alarm Pinger, apinger(10289)
    Oct 28 05:50:11 apinger: Exiting on signal 15.
    Oct 28 05:45:43 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:45:42 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 05:45:40 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:40 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 05:45:39 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:38 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:38 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:36 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:35 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:34 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:45:30 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:45:28 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 05:45:27 apinger: alarm canceled (config reload): WAN_DHCP(174.1.32.1) *** down ***
    Oct 28 05:45:27 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:45:26 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 05:45:25 apinger: ALARM: WAN_DHCP(174.1.32.1) *** down ***
    Oct 28 05:43:50 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:43:49 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 05:43:49 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 05:43:48 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:43:47 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:43:46 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:43:45 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:43:44 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:43:41 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:43:39 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:40:38 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:40:35 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:40:34 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:40:33 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:40:32 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:40:31 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 05:40:29 apinger: SIGHUP received, reloading configuration.
    Oct 28 05:37:57 apinger: Starting Alarm Pinger, apinger(20056)
    Oct 28 05:01:53 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** delay ***
    Oct 28 05:01:44 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** delay ***
    Oct 28 04:51:32 apinger: Starting Alarm Pinger, apinger(20743)
    Oct 28 04:47:02 apinger: SIGHUP received, reloading configuration.
    Oct 28 04:47:02 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 04:47:01 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 04:47:00 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 04:46:59 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 04:46:58 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 04:46:57 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 04:46:56 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 04:46:55 apinger: Could not bind socket on address(10.4.0.195) for monitoring address 10.4.0.1(AirVPN_WAN) with error Can't assign requested address
    Oct 28 04:43:20 apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 04:43:11 apinger: alarm canceled: WAN_DHCP(174.1.32.1) *** down ***
    Oct 28 04:42:18 apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 28 04:42:17 apinger: ALARM: WAN_DHCP(174.1.32.1) *** down ***
    Oct 28 04:37:08 apinger: Starting Alarm Pinger, apinger(19338)
    Oct 28 04:34:44 apinger: SIGHUP received, reloading configuration.
    Oct 28 04:34:37 apinger: alarm canceled: WAN_DHCP(174.1.32.1) *** down ***
    Oct 28 04:29:09 apinger: Starting Alarm Pinger, apinger(20480)
    Oct 27 21:24:42 pfSense apinger: alarm canceled: WAN_DHCP(174.1.32.1) *** down ***
    Oct 27 21:23:50 pfSense apinger: ALARM: WAN_DHCP(174.1.32.1) *** down ***
    Oct 27 21:17:14 pfSense apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 21:14:36 pfSense apinger: alarm canceled (config reload): AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 21:14:36 pfSense apinger: SIGHUP received, reloading configuration.
    Oct 27 21:14:11 pfSense apinger: alarm canceled: WAN_DHCP(174.1.32.1) *** down ***
    Oct 27 21:13:20 pfSense apinger: ALARM: WAN_DHCP(174.1.32.1) *** down ***
    Oct 27 21:13:20 pfSense apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 20:47:34 pfSense apinger: alarm canceled (config reload): AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 20:47:34 pfSense apinger: SIGHUP received, reloading configuration.
    Oct 27 20:47:26 pfSense apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 20:41:57 pfSense apinger: alarm canceled (config reload): AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 20:41:57 pfSense apinger: SIGHUP received, reloading configuration.
    Oct 27 20:41:57 pfSense apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 09:15:16 pfSense apinger: alarm canceled: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 27 09:15:00 pfSense apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***
    Oct 26 22:27:09 pfSense apinger: alarm canceled (config reload): AirVPN_WAN(10.4.0.1) *** down ***
    Oct 26 22:27:09 pfSense apinger: SIGHUP received, reloading configuration.
    Oct 26 22:27:01 pfSense apinger: alarm canceled: WAN_DHCP(174.1.32.1) *** down ***
    Oct 26 22:26:09 pfSense apinger: ALARM: AirVPN_WAN(10.4.0.1) *** down ***



  • anything guys?



  • Have you searched for some of the stuff in your logs?

    What did you find?



  • Apinger is still borked and you might want to disable gateway monitoring (System - Routing - (Edit your gateway) - Disable Gateway Monitoring) if apinger is causing you pain.



  • thanks guys, very grateful.

    I thought that apinger was supposed to be fixed in 2.2, I guess not, thanks KOM.  I did a bunch of pinging and from the command prompt and there seems to be almost no packet loss, I think 3 out of 3000.

    i tried reinstalling and it is still up and down and flakey.  I have changed network cables as well.  I am about to try to install it all on another machine but it will be quite a bit of work and mess with my home computer, do you guys think it is a hardware thing?

    I have also resorted to no VPN, just the basic Wan and Lan to try to simplify a little more to figure things out.

    I have a wireless access point connected to the PFsense and when i wirelesly connect to the network, it doesn't seem to have as many errors.


  • Banned

    As noted above - with apinger, you have no idea whether what it shows and detects are real issues or yet another inexplicable bug causing apinger to invent completely BS figures (such as the 109% packet loss I regularly see here) and result in up/down/up/down cycle for absolutely no valid reason. Disable the monitoring and see for yourself.



  • I think apinger was taking down my VPN as well when it thought something was going wrong.

    So I should disable apinger, clear all logs and see what errors gets logged?  or just disable and do some pinging and other types of testing?


  • Banned

    Well, clearing the above noise from logs certainly won't harm anything.





  • thanks for the links!

    really looking forward to testing tonight, I am off tomorrow so I have tonight to play.

    Do you guys think i should completely change hardware or work with the system/software i have right now?


  • Banned

    I don't think changing HW will get you anywhere, frankly.



  • thanks,  you saved me a bunch of time and potentially money.  I will try to iron out issues with what I have.  will post back,  thanks for taking your time to help me.



  • after I disable the gateway monitoring, what would be the best way to determine if i have a problem at all?



  • you could run a batch file on one of your clients and let it run for a while.

    something like this:

    
    @echo off
    
    :START
    
    ping -n 4 4.2.2.2 >nul
    
    if %errorlevel% == 1 (
      echo Internet offline >> C:\Internet.txt
      Time /t >> C:\Internet.txt
    )
    
    Timeout /t 30
    @set errorlevel = 0
    
    GOTO START
    
    


  • awesome thanks Heper.. at least that gives me a start..  I was starting to think it might be an Intel network card that I have, probably isn't..



  • hey guys, stopping apinger seems to have helped with the errors and internet dropping, thanks for that.

    I am now having problems with very high pings and slow internet.  sometimes the ping to 8.8.8.8 is 20ms, sometimes it is 800ms.  whenever I ping AirVPN, it is a 2-400ms.    I have been using DNS from UNblock, where is the setting to get the DNS from my ISP automatically?  i couldn't find them under WAN settings.

    Any other hints to figure out what is going on with ping swings and generally high pings?  I cannot even use VPN it is so slow now, never had a problem before.



  • Is DNS Forwarder or DNS Resolver enabled (which one)?

    DNS Forwarder uses the DNS Servers specified in the System: General Setup.
    DNS Resolver uses the DNS root servers.

    Client DNS server assignment can be overridden in Services: DHCP server.



  • i have DNS forwarder enabled and just LAN and Localhost selected as this is how my VPN is supposed to be setup when i get it working.

    I plugged my cable modem directly into my laptop and everything is fast.  I then rebooted and connected PFsense again and it seems better.  I think i am starting to get how DNS is assigned, thanks NOYB.  Does DNS determine my Pings?

    I can switch between my ISP dns and Unblock's dns and they both seem fairly fast pinging most websites.  When i ping some of the AIRVPN servers though, I am still getting the high hundreds though, not sure what that is about.  If I can't get good pings to them, i won't be able to get the VPN up and working.

    Any way to figure out where it is going off the rail?

    I was able to go to pingtest.net and get an A grade on my connection.  The only problem now i guess are the very high pings to the servers at AirVPN.



  • DNS should have nothing to do with ping times (assuming name resolves to same IP address).  Once name is resolved to an IP address DNS is out of the picture.

    To see where the slowness may be try a trace route (tracert on a Windows client).



  • does this mean anything?  the request timed out on step 2.  it seemed fast until step 7.

    1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [192.168.1.1]
      2    *        *        *    Request timed out.
      3    9 ms    9 ms    9 ms  rd3st-tge0-13-0-10-1.vc.shawcable.net [64.59.150.85]
      4    16 ms    10 ms    14 ms  66.163.72.254
      5    14 ms    15 ms    16 ms  rc5wt-be5.wa.shawcable.net [66.163.74.158]
      6    15 ms    15 ms    13 ms  xe-9-1-0.sea22.ip4.gtt.net [77.67.71.73]
      7  160 ms  161 ms  161 ms  xe-1-3-0.fra29.ip4.gtt.net [141.136.108.17]
      8  167 ms  170 ms  168 ms  a100-gw.ip4.gtt.net [77.67.66.206]
      9  168 ms  171 ms  168 ms  54.239.5.110
    10  167 ms  169 ms  167 ms  54.239.5.134
    11  168 ms  173 ms  172 ms  ec2-54-93-175-114.eu-central-1.compute.amazonaws.com [54.93.175.114]

    and one to google

    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:

    1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [192.168.1.1]
      2    *        *        *    Request timed out.
      3    12 ms    9 ms    10 ms  rd3st-tge0-13-0-10-1.vc.shawcable.net [64.59.150.85]
      4    18 ms    17 ms    16 ms  66.163.70.106
      5    18 ms    15 ms    16 ms  rx0wt-google.wa.shawcable.net [66.163.68.50]
      6    14 ms    15 ms    17 ms  74.125.37.95
      7    15 ms    15 ms    15 ms  209.85.250.121
      8    16 ms    16 ms    16 ms  google-public-dns-a.google.com [8.8.8.8]



  • No the hop #2 time out is not significant.  Just means that router does not respond to pings.
    Don't see any of the 400 to 800 ms pings you mentioned in the opening post.

    That doesn't look too bad really.  Here's what it looks like from here for comparison.

    
    Tracing route to ec2-54-93-175-114.eu-central-1.compute.amazonaws.com [54.93.175.114]
    over a maximum of 30 hops:
    
      1     1 ms    <1 ms     1 ms  pfSense.localdomain [192.168.2.1]
      2     6 ms     5 ms     6 ms  static-50-53-160-1.bvtn.or.frontiernet.net [50.53.160.1]
      3     6 ms     5 ms     5 ms  50.38.7.201
      4    19 ms    37 ms    30 ms  ae2---0.cor02.bvtn.or.frontiernet.net [74.40.1.181]
      5    20 ms    22 ms    20 ms  ae3---0.cor01.plal.ca.frontiernet.net [74.40.1.225]
      6    21 ms    48 ms    22 ms  ae0---0.cbr01.plal.ca.frontiernet.net [74.40.3.150]
      7    21 ms    22 ms    19 ms  xe-0.paix.plalca01.us.bb.gin.ntt.net [198.32.176.14]
      8   231 ms   232 ms   232 ms  ae-15.r01.snjsca04.us.bb.gin.ntt.net [129.250.5.33]
      9    22 ms    23 ms    22 ms  ae-1.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
     10    88 ms    88 ms   112 ms  ae-8.r21.chcgil09.us.bb.gin.ntt.net [129.250.5.16]
     11   132 ms   142 ms   140 ms  ae-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.3.97]
     12    89 ms    95 ms    88 ms  ae-5.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
     13   231 ms   232 ms   235 ms  ae-6.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.181]
     14     *      229 ms   222 ms  ae-1.r02.frnkge03.de.bb.gin.ntt.net [129.250.4.163]
     15   169 ms   174 ms   177 ms  212.119.27.174
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18   170 ms   170 ms   175 ms  54.239.5.134
     19   169 ms   169 ms   169 ms  ec2-54-93-175-114.eu-central-1.compute.amazonaws.com [54.93.175.114]
    
    Trace complete.
    
    
    
    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms    <1 ms  pfSense.localdomain [192.168.2.1]
      2     6 ms     5 ms     5 ms  static-50-53-160-1.bvtn.or.frontiernet.net [50.53.160.1]
      3     7 ms     7 ms     8 ms  50.38.7.201
      4    12 ms    10 ms    12 ms  ae2---0.cor02.bvtn.or.frontiernet.net [74.40.1.181]
      5     9 ms    10 ms    10 ms  ae0---0.cor01.bvtn.or.frontiernet.net [74.40.1.185]
      6    10 ms    12 ms    10 ms  ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.221]
      7    20 ms    18 ms    15 ms  ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.122]
      8    10 ms    12 ms    11 ms  74.40.26.131
      9    10 ms    10 ms    10 ms  72.14.238.181
     10    10 ms    10 ms    10 ms  209.85.245.67
     11    10 ms    10 ms    10 ms  google-public-dns-a.google.com [8.8.8.8]
    
    Trace complete.
    
    


  • Oh and by the way that hop #2 is probably the default gateway.  So no wonder apinger was having trouble.

    So it was probably detecting and marking the WAN interface as down.  That's probably why the VPN was going down.



  • hate to sound like any more of a dumbass but is there a way to fix that?

    i did another clean install and now am only using WAN and LAN.  I also tried plugging my WAN into the other Intel NIC which gets me a different IP address from my ISP to just test, didn't seem to make a difference.



  • Configure apinger to monitor the next available hop.  Or leave apinger disabled.



  • thanks NOYB, i configured it to the 2nd hop and am not getting any errors, thanks for the tip.  If it gives me any problems, i will disable it but i kind of like having it on. Going to try to setup OpenVPN client tomorrow to see how it works.  Have a good night.



  • got the VPN up and working, seems to be better.  Having a few VPN errors though.  Not sure if it is totally taking the tunnel down or just reporting.  Going to google this a little.

    Oct 31 13:20:19 openvpn[53731]: MANAGEMENT: Client disconnected
    Oct 31 13:20:19 openvpn[53731]: MANAGEMENT: CMD 'status 2'
    Oct 31 13:20:19 openvpn[53731]: MANAGEMENT: CMD 'state 1'
    Oct 31 13:20:19 openvpn[53731]: MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
    Oct 31 13:17:24 openvpn[53731]: MANAGEMENT: Client disconnected
    Oct 31 13:17:24 openvpn[53731]: MANAGEMENT: CMD 'status 2'
    Oct 31 13:17:24 openvpn[53731]: MANAGEMENT: CMD 'state 1'
    Oct 31 13:17:24 openvpn[53731]: MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
    Oct 31 13:17:23 openvpn[53731]: MANAGEMENT: Client disconnected
    Oct 31 13:17:23 openvpn[53731]: MANAGEMENT: CMD 'status 2'
    Oct 31 13:17:23 openvpn[53731]: MANAGEMENT: CMD 'state 1'
    Oct 31 13:17:23 openvpn[53731]: MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
    Oct 31 13:17:22 openvpn[53731]: MANAGEMENT: Client disconnected
    Oct 31 13:17:22 openvpn[53731]: MANAGEMENT: CMD 'status 2'
    Oct 31 13:17:22 openvpn[53731]: MANAGEMENT: CMD 'state 1'
    Oct 31 13:17:22 openvpn[53731]: MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
    Oct 31 13:17:14 openvpn[53731]: MANAGEMENT: Client disconnected
    Oct 31 13:17:14 openvpn[53731]: MANAGEMENT: CMD 'status 2'
    Oct 31 13:17:14 openvpn[53731]: MANAGEMENT: CMD 'state 1'
    Oct 31 13:17:14 openvpn[53731]: MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
    Oct 31 13:16:43 openvpn[53731]: MANAGEMENT: Client disconnected
    Oct 31 13:16:43 openvpn[53731]: MANAGEMENT: CMD 'status 2'
    Oct 31 13:16:43 openvpn[53731]: MANAGEMENT: CMD 'state 1'



  • hey guys, VPN is up and down like crazy..  here are the logs..  frustrating..  the rest of the network stuff seems good now, this seems like it is the only outstanding problem. Switching next weekend from 30mb cable to 100mb ADSL, can't wait.  any ideas?

    Nov 1 10:31:14 php-fpm[3124]: /rc.start_packages: Restarting/Starting all packages.
    Nov 1 10:31:13 check_reload_status: Starting packages
    Nov 1 10:31:13 php-fpm[3124]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.4.5.207 -> 10.4.14.212 - Restarting packages.
    Nov 1 10:31:11 php-fpm[3124]: /rc.newwanip: Creating rrd update script
    Nov 1 10:31:07 php-fpm[3124]: /rc.newwanip: IP has changed, killing states on former IP 10.4.5.207.
    Nov 1 10:31:07 php-fpm[3124]: /rc.newwanip: rc.newwanip: on (IP address: 10.4.14.212) (interface: AIRVPN_WAN[opt1]) (real interface: ovpnc1).
    Nov 1 10:31:07 php-fpm[3124]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
    Nov 1 10:31:06 check_reload_status: rc.newwanip starting ovpnc1
    Nov 1 10:31:06 kernel: ovpnc1: link state changed to UP
    Nov 1 10:31:05 check_reload_status: Reloading filter
    Nov 1 10:31:05 kernel: ovpnc1: link state changed to DOWN
    Nov 1 09:33:44 php-fpm[58963]: /rc.start_packages: Restarting/Starting all packages.
    Nov 1 09:33:43 check_reload_status: Starting packages
    Nov 1 09:33:43 php-fpm[58963]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.4.1.211 -> 10.4.5.207 - Restarting packages.
    Nov 1 09:33:41 php-fpm[58963]: /rc.newwanip: Creating rrd update script
    Nov 1 09:33:37 php-fpm[58963]: /rc.newwanip: IP has changed, killing states on former IP 10.4.1.211.
    Nov 1 09:33:37 php-fpm[58963]: /rc.newwanip: rc.newwanip: on (IP address: 10.4.5.207) (interface: AIRVPN_WAN[opt1]) (real interface: ovpnc1).
    Nov 1 09:33:37 php-fpm[58963]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
    Nov 1 09:33:36 check_reload_status: rc.newwanip starting ovpnc1
    Nov 1 09:33:36 kernel: ovpnc1: link state changed to UP
    Nov 1 09:33:35 check_reload_status: Reloading filter
    Nov 1 09:33:35 kernel: ovpnc1: link state changed to DOWN
    Nov 1 09:14:58 php-fpm[24903]: /rc.start_packages: Restarting/Starting all packages.
    Nov 1 09:14:57 check_reload_status: Starting packages
    Nov 1 09:14:57 php-fpm[24903]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.4.7.147 -> 10.4.1.211 - Restarting packages.
    Nov 1 09:14:55 php-fpm[24903]: /rc.newwanip: Creating rrd update script
    Nov 1 09:14:51 php-fpm[24903]: /rc.newwanip: IP has changed, killing states on former IP 10.4.7.147.
    Nov 1 09:14:51 php-fpm[24903]: /rc.newwanip: rc.newwanip: on (IP address: 10.4.1.211) (interface: AIRVPN_WAN[opt1]) (real interface: ovpnc1).
    Nov 1 09:14:51 php-fpm[24903]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
    Nov 1 09:14:50 check_reload_status: rc.newwanip starting ovpnc1
    Nov 1 09:14:50 kernel: ovpnc1: link state changed to UP
    Nov 1 09:14:49 check_reload_status: Reloading filter
    Nov 1 09:14:49 kernel: ovpnc1: link state changed to DOWN
    Nov 1 08:49:53 php-fpm[88638]: /rc.start_packages: Restarting/Starting all packages.
    Nov 1 08:49:52 check_reload_status: Starting packages
    Nov 1 08:49:52 php-fpm[88638]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.4.21.60 -> 10.4.7.147 - Restarting packages.
    Nov 1 08:49:50 php-fpm[88638]: /rc.newwanip: Creating rrd update script
    Nov 1 08:49:46 php-fpm[88638]: /rc.newwanip: IP has changed, killing states on former IP 10.4.21.60.
    Nov 1 08:49:46 php-fpm[88638]: /rc.newwanip: rc.newwanip: on (IP address: 10.4.7.147) (interface: AIRVPN_WAN[opt1]) (real interface: ovpnc1).
    Nov 1 08:49:46 php-fpm[88638]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
    Nov 1 08:49:45 check_reload_status: rc.newwanip starting ovpnc1
    Nov 1 08:49:45 kernel: ovpnc1: link state changed to UP
    Nov 1 08:49:44 kernel: ovpnc1: link state changed to DOWN
    Nov 1 08:20:24 syslogd: kernel boot file is /boot/kernel/kernel



  • Try disabling gateway monitoring for both VPN and WAN in System>routing. Openvpn by itself is capable of detecting and reconnecting if the vpn connection is broken.



  • i have all monitoring turned off on the gateways.. just having tons of OpenVPN errors and disconnecting.



  • It happens at 09:14:49, 09:33:35, 10:31:05. Check other logs like gateway, openvpn etc to see what's happening at these times…or probably before these times.
    It could easily be that you haven't added custom options from airvpn config into the ovpn client setting's advanced box, like i think once I added mssfix from the vpn's config files, and BAM it was stable.



  • This is what is in my advance box, I'm pretty sure you are right though, it is probably something in here:

    remote-cert-tls server;comp-lzo no;verb 4;explicit-exit-notify 5;key-direction 1;auth SHA1;keysize 256;key-method 2;tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA;

    I just updated to 60 internet today, clearing all my logs and see what I get, pretty sure it will be the exact same.  Nice though, going through the tunnel I get 60, outside the tunnel 70.


Log in to reply