Smokeping as a package - $100
-
I've looked into this a little.
SmokePing 2.x has monitoring and a web interface, and is written in perl. There are quite a few monitor types, which was a surprise (I thought it was just for pings, which feature would be fairly easy to directly replicate).
Version 3.0 is going towards monitoring only, which may be better for pfSense integration; SmokePing would then be used for data collection, and the interface could easily be merged with pfSense.
Writing a 3.0 package that runs as a slave would be the easiest first step (once SmokePing 3.0 is a bit more stable; development started about a month ago).
Good to know, hoping more ppl would find this useful too tho ;D
-
I'll chip in $100 as well. I use smokeping to monitor both of my Multi-WAN connections but would rather not need to run it on other hosts when my Soekris (running pfSense) can probably handle it.
-
I may be able to have a look at this but I really am not sure how to deal with the PBI packages.
-
I may be able to have a look at this but I really am not sure how to deal with the PBI packages.
;) Good time to learn maybe?
Also if you would take this bounty up please let me know if you need payment upfront, thank you.
-
@val:
I may be able to have a look at this but I really am not sure how to deal with the PBI packages.
;) Good time to learn maybe?
Also if you would take this bounty up please let me know if you need payment upfront, thank you.
Possibly! There really isn't a whole lot to go on as far as information.
-
I'll chip in $100
Just as a side note, I would be happy with just the ability to be able to have a tab to the RRD graphs where you can simply add ip's or domains and choose which interface to use and add them in and have pfsense handle it in an interface similar to smokeping that sat within RRD graphs. Smokeping, its self is not really a prerequisite for me.
Cheers,
James
-
;D $400 now.
-
Would it be sufficient to have a step-by-step guide / howto for installing it (either on a full, or on a NanoBSD version of) vanilla pfSense?
-
I've looked into this a little.
SmokePing 2.x has monitoring and a web interface, and is written in perl. There are quite a few monitor types, which was a surprise (I thought it was just for pings, which feature would be fairly easy to directly replicate).
Version 3.0 is going towards monitoring only, which may be better for pfSense integration; SmokePing would then be used for data collection, and the interface could easily be merged with pfSense.
Writing a 3.0 package that runs as a slave would be the easiest first step (once SmokePing 3.0 is a bit more stable; development started about a month ago).
Honestly I'm surprised this hasn't been integrated into pfsense yet, it's the de facto standard for monitoring line latency even for ISPs.
Smokeping3 is work that was sponsored and it doesn't seem to have taken off - https://github.com/oetiker/smokeping-3.x
The latest commit was on Nov 9, 2013.
Smokeping2 is stable and will likely see use far longer than Smokeping3.This is a decent bounty, and I will try to see if I can get Smokeping2 to work with lighthttpd and all the Perl dependencies.
I'm unfamiliar with pfsense packaging, and the hardest part for me will be to enable the package to add hosts for monitoring via the web gui. -
Freelance coder here, I'll have a look at this once I get back to my dev environment (holidays).
-
I've looked at it. Oh yeah, this can be done. No problem! I'm assuming it hasn't been completed by the previous psoter either, since he posted in October…
The hardest part for me will be the fact it's written in PERL. I'm more accustomed to lower-level languages like C and C++.
This should be a snap. lighthttpd and RRD, no problem. Might even be able to piggyback it onto CARP. No promises about CARP, though.
I return to my old beating grounds in a week, I'll give it a crack then. MISSION ACCEPTED.
-
Is there an update about the smokeping package?
-
@Ben.:
Is there an update about the smokeping package?
With pfSense having made some pretty major changes back at version 2.3 - nginx is now used instead of lighttpd, RRD graphing is no longer used due to the amount of prerequisite packages that would increase the distribution size significantly - so if it was being worked on, these two changes alone probably threw a monkey wrench into the works.
IF someone IS working on it, then you might want to contact jdillard about using the D3 graphing engine that is now used for the monitoring graphs, and will also be used for vnstat when it eventually returns as a package.
