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

    Apinger has it been replaced

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    18 Posts 10 Posters 5.8k 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.
    • G
      grandrivers
      last edited by

      well dual wan is what brought me to pfsense and for awhile apnginer was half usable for me but since its last recompile emeral did 2.2 ish its has broke the dual wan functionality of pfsense.
      I think the worse your internet connections are the more important Apinger replacement is, maybe I truley am in the minority with apinger not working more than working
      maybe its only residential connections that fight with apinger but somehow i have feeling thats not the case

      I can help test as soon as ready bare metal install so no vm issuses

      pfsense plus 25.03 super micro A1SRM-2558F
      C2558 32gig ECC  60gig SSD

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        Thats great news jimp, I was just recently reading a blog post about the new webgui - yeah that is prob keeping everyone busy..  But sounds like the apinger issues will be addressed sooner vs later which is good news.. Thanks!

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          @johnpoz: The graphs/widgets you've posted are on the good side, just mostly harmless BS info. I keep getting BS like 109% packet loss, and the damned superbroken thing totally confused and eating all CPU until killed and respawned.

          1 Reply Last reply Reply Quote 0
          • D
            diablo266
            last edited by

            Glad to know apinger has had some work done on it, I've been hoping to use the dual-wan and failover functionality for years with pfsense but have been unable to due to it's brokenness. Hopefully we're months instead of years away now.

            1 Reply Last reply Reply Quote 0
            • luckman212L
              luckman212 LAYER 8
              last edited by

              Was browsing thru gonzopancho's twitter feed and saw this
              https://twitter.com/gonzopancho/status/672176161850441729

              :D  ::) good news :D 8)

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

                Switching to dpinger will be the last thing before we go to beta, it'll hopefully be committed this week.

                1 Reply Last reply Reply Quote 0
                • J
                  jwt Netgate
                  last edited by

                  @cmb:

                  Switching to dpinger will be the last thing before we go to beta, it'll hopefully be committed this week.

                  Well, either last, or second to last.

                  1 Reply Last reply Reply Quote 0
                  • M
                    maverick_slo
                    last edited by

                    @jwt:

                    @cmb:

                    Switching to dpinger will be the last thing before we go to beta, it'll hopefully be committed this week.

                    Well, either last, or second to last.

                    Ou yeah :)

                    1 Reply Last reply Reply Quote 0
                    • J
                      jwt Netgate
                      last edited by

                      Second to last:

                      https://twitter.com/rbgarga/status/675078699998437381

                      Unlocking package pfSense-kernel-pfSense… done.
                      Downloading upgrade packages...
                      Checking for upgrades (6 candidates): ...... done
                      Processing candidates (6 candidates): ...... done
                      The following 6 package(s) will be affected (of 0 checked):

                      New packages to be INSTALLED:
                      dpinger: 0.0.1.20151209_2 [pfSense]

                      Installed packages to be UPGRADED:
                      pfSense-rc: 2.3.a.20151209.0831 -> 2.3.a.20151210.1516 [pfSense-core]
                      pfSense-kernel-pfSense: 2.3.a.20151209.0831 -> 2.3.a.20151210.1516 [pfSense-core]
                      pfSense-default-config-serial: 2.3.a.20151209.0831 -> 2.3.a.20151210.1516 [pfSense-core]
                      pfSense-base: 2.3.a.20151209.0831 -> 2.3.a.20151210.1516 [pfSense-core]
                      pfSense: 2.3.a.20151209.0716 -> 2.3.a.20151210.1512 [pfSense]

                      The operation will free 6 KiB.
                      41 MiB to be downloaded.
                      Fetching pfSense-rc-2.3.a.20151210.1516.txz: . done
                      Fetching pfSense-kernel-pfSense-2.3.a.20151210.1516.txz: …....... done
                      Fetching pfSense-default-config-serial-2.3.a.20151210.1516.txz: . done
                      Fetching pfSense-base-2.3.a.20151210.1516.txz: .......... done
                      Fetching pfSense-2.3.a.20151210.1512.txz: . done
                      Fetching dpinger-0.0.1.20151209_2.txz: . done
                      Checking integrity... done (0 conflicting)

                      Upgrading pfSense kernel...
                      Checking integrity... done (0 conflicting)
                      The following 2 package(s) will be affected (of 0 checked):

                      Installed packages to be UPGRADED:
                      pfSense-kernel-pfSense: 2.3.a.20151209.0831 -> 2.3.a.20151210.1516 [pfSense-core]
                      pfSense-rc: 2.3.a.20151209.0831 -> 2.3.a.20151210.1516 [pfSense-core]

                      The process will require 227 B more space.
                      [1/2] Upgrading pfSense-rc from 2.3.a.20151209.0831 to 2.3.a.20151210.1516…
                      [1/2] Extracting pfSense-rc-2.3.a.20151210.1516: . done
                      [2/2] Upgrading pfSense-kernel-pfSense from 2.3.a.20151209.0831 to 2.3.a.20151210.1516…
                      ===> Keeping a copy of current kernel in /boot/kernel.old
                      [2/2] Extracting pfSense-kernel-pfSense-2.3.a.20151210.1516: …....... done
                      Upgrade is complete.  Rebooting in 10 seconds.

                      Locking package pfSense-kernel-pfSense... done.
                      Success

                      1 Reply Last reply Reply Quote 0
                      • J
                        jwt Netgate
                        last edited by

                        After reboot:

                        ![Screen Shot 2015-12-10 at 6.49.54 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2015-12-10 at 6.49.54 PM.png_thumb)
                        ![Screen Shot 2015-12-10 at 6.49.54 PM.png](/public/imported_attachments/1/Screen Shot 2015-12-10 at 6.49.54 PM.png)

                        1 Reply Last reply Reply Quote 0
                        • H
                          Harvy66
                          last edited by

                          da_pinger will be so much better.  ;D

                          1 Reply Last reply Reply Quote 0
                          • D
                            diablo266
                            last edited by

                            This is incredibly exciting, apinger has been a thorn in my side for years. Thank you guys!

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