Apinger has it been replaced

[johnpoz]

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!

[doktornotor]

@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.

[diablo266]

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.

[luckman212]

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

:D  ::) good news :D 8)

[cmb]

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

[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.

[maverick_slo]

@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 :)

[jwt]

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

[jwt]

After reboot:


[Harvy66]

da_pinger will be so much better.  ;D

[diablo266]

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