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

    Unstable internet since 2.2.4

    Scheduled Pinned Locked Moved General pfSense Questions
    31 Posts 7 Posters 4.4k Views
    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.
    • N Offline
      NOYB
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • X Offline
        xman111
        last edited by

        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.

        1 Reply Last reply Reply Quote 0
        • N Offline
          NOYB
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • X Offline
            xman111
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • X Offline
              xman111
              last edited by

              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'

              1 Reply Last reply Reply Quote 0
              • X Offline
                xman111
                last edited by

                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

                1 Reply Last reply Reply Quote 0
                • P Offline
                  pf3000
                  last edited by

                  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.

                  1 Reply Last reply Reply Quote 0
                  • X Offline
                    xman111
                    last edited by

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

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      pf3000
                      last edited by

                      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.

                      1 Reply Last reply Reply Quote 0
                      • X Offline
                        xman111
                        last edited by

                        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.

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