Smokeping configuration

G

giggity

Expert Member
Joined
Feb 19, 2011
Messages
1,209
Reaction score
135
Location
Pretoria
I've made my SmokePing publicly available: http://smoke.sengi.co.za/
Don't judge too hard.


@PBCool Can you provide any feedback/suggestions/improvements on this Smokeping configuration for CISP's network?

Or if anyone from the community has an up-to-date configuration that would be great.

I have other hosts like Google, AWS, etc. but these are for CISP specifically. I found these IPs in someone's public Smokeping, where some of the IPs weren't working any more, so I'm expecting these are pretty out of date.

INI: 
+ CISP
title = CISP
menu = CISP

++ cdns1cispcoza
title = cdns1.cisp.co.za (154.0.1.1) [JHB]
host = 154.0.1.1

++ cdns1cptcispcoza
title = cdns1.cpt.cisp.co.za (155.93.255.1) [CPT]
host = 155.93.255.1

++ cdns1dbncispcoza
title = cdns1.dbn.cisp.co.za (154.0.1.150) [DBN]
host = 154.0.1.150

++ n35t-custcoolideascoza
title = n35t-cust.coolideas.co.za (102.132.144.1) [BRY]
host = 102.132.144.1

++ cool-154-0-0-100-lon-core-router
title = London Core Router (154.0.0.100) [LON]
host = 154.0.0.100

++ u101custcoolideascoza
title = u101.cust.coolideas.co.za (154.0.5.17) [LON]
host = 154.0.5.17

++ cispdemarccogentcocom
title = cisp.demarc.cogentco.com (149.14.250.250) [LON]
host = 149.14.250.250

++ queen
title = queen.cisp.co.za [LON]
host = queen.cisp.co.za

Edit: Added 154.0.0.100 to the config above - thanks @TheRoDent :D
 
Last edited:
Managed to set this up and getting some data back

1687204677808.png

1687204719346.png
1687204743794.png
 
giggity said:
@PBCool Can you provide any feedback/suggestions/improvements on this Smokeping configuration for CISP's network?

Or if anyone from the community has an up-to-date configuration that would be great.

I have other hosts like Google, AWS, etc. but these are for CISP specifically. I found these IPs in someone's public Smokeping, where some of the IPs weren't working any more, so I'm expecting these are pretty out of date.

INI: 
+ CISP
title = CISP
menu = CISP

++ cdns1cispcoza
title = cdns1.cisp.co.za (154.0.1.1) [JHB]
host = 154.0.1.1

++ cdns1cptcispcoza
title = cdns1.cpt.cisp.co.za (155.93.255.1) [CPT]
host = 155.93.255.1

++ cdns1dbncispcoza
title = cdns1.dbn.cisp.co.za (154.0.1.150) [DBN]
host = 154.0.1.150

++ n35t-custcoolideascoza
title = n35t-cust.coolideas.co.za (102.132.144.1) [BRY]
host = 102.132.144.1

++ u101custcoolideascoza
title = u101.cust.coolideas.co.za (154.0.5.17) [LON]
host = 154.0.5.17

++ cispdemarccogentcocom
title = cisp.demarc.cogentco.com (149.14.250.250) [LON]
host = 149.14.250.250

++ queen
title = queen.cisp.co.za [LON]
host = queen.cisp.co.za
Click to expand...
I would recommend adding 154.0.0.100 which is one of our Core Routers in the UK.

Keep in mind however, that the router has rate-limits (like any carrier router) in place when it comes to ICMP packets. Don't overcook it. And no, I'm not going to say what the limits are, suffcient to say it's not unreasonable.
 
TheRoDent said:
I would recommend adding 154.0.0.100 which is one of our Core Routers in the UK.

Keep in mind however, that the router has rate-limits (like any carrier router) in place when it comes to ICMP packets. Don't overcook it. And no, I'm not going to say what the limits are, suffcient to say it's not unreasonable.
Click to expand...
Added the router to the config, thanks. It's 20 pings over 300s, so hopefully shouldn't be an issue... unless it gets flooded by multiple people.
 
giggity said:
Added the router to the config, thanks. It's 20 pings over 300s, so hopefully shouldn't be an issue... unless it gets flooded by multiple people.
Click to expand...

Same config on my end.

Where are you located and what FNO are you using? I’m PTA East and Openserve
 
Here are my 48h logs.

Info about my setup:
SmokePing Container (Portainer) running on a Raspberry Pi 400. Connected using an Ethernet cable. I'm monitoring connection to the router itself as a baseline for any abnormalities (cable issues/CPU limitations) and it seems fine so far.

1687270053751.png

Seems like it might be working fine, since you can see the spike yesterday at around 12:00 when things went wonky. Not sure what happened around 14:00 though, I don't think I noticed any degradation.
1687270624361.png

1687270272566.png

1687270312865.png

I'm also monitoring a trace to a League of Legends server until the point I start getting no ICMP responses. I don't know if there's a better way to do this other than manually entering each IP. I'm also not sure this will yield any useful info since the game uses UDP, and sends way more than 20 packets per 300s.

If anyone has a traceroute for Apex, I can also monitor that. Seen a lot of complaints about it on the main feedback thread.

1687270372877.png
 
Are you going to expose this somehow or just post here periodically ?
 
Mzezman said:
Nice… one day I’ll figure out (and find the time) how to do this on mine
Click to expand...
If your ISP and FNO don't mess with NAT too much, it's not too difficult. Set up DDNS on your router, port forward to your server using dst-nat. If your DDNS server has a fugly domain, buy a domain and set up a CNAME record.
 
giggity said:
If your ISP and FNO don't mess with NAT too much, it's not too difficult. Set up DDNS on your router, port forward to your server using dst-nat. If your DDNS server has a fugly domain, buy a domain and set up a CNAME record.
Click to expand...

Conceptually I understand what you’re saying, it’s just sitting down, tooling, configuring and getting it done.
 
Odd, I was just looking into this. Can it do traceroutes too? If ping only, did you consider UptimeKuma?
 
calypso said:
Odd, I was just looking into this. Can it do traceroutes too? If ping only, did you consider UptimeKuma?
Click to expand...
UptimeKuma doesn't have packet loss logs as far as I know - could be wrong. Otherwise it's certainly more user friendly.

SmokePing can do traceroutes, but I haven't had time to play around with them. I think it's not a proper traceroute either, more like you configure the hop just before the destination IP.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X