dpinger 3.6

@luckman212 I haven't done a Redmine for dpinger 3.6 yet, but there's no reason you can't update. 3.5/3.6 are just a minor bug fix releases.

FYI, Redmine 16882 has been created for the update.

@dennypage is there a reason to update to this if not really seeing any bugs? I take it at some point it will show up in normal pkg update or in pfsense 26.x for example.

@johnpoz personal choice.

I wish it had a cool down timer on this man I watched my ssd get destroyed once when the internet was down.

@JonathanLee said in dpinger 3.6:

I watched my ssd get destroyed once when the internet was down.

How was your SSD was destroyed, and what was the relationship to dpinger?

@dennypage I recently had a gateway dropping on and off, which caused dpinger to constantly write to the logs for days. Unfortunately, this heavy disk thrashing burned through about 5% of my SSD lifetime. It would be great if dpinger could implement a cooldown period during rapid state changes to prevent this.

@JonathanLee You might be conflating actions of dpinger with actions of upper layers. What are the actual log entries in question?

@dennypage they were all gateway logs that day all of them it was nothing but pages of them.

@JonathanLee I don't see how even if 10s of thousands of entries could be the cause of 5% loss of your ssd life.. Unless is was like a 1MB ssd or something.

SSDs are rated for like their total size written per day for years and years.. I don't see how some text entry logs could be any significant amount of data - unless your like writing something like the complete works of shakespeare in every log entry.

@JonathanLee said in dpinger 3.6:

they were all gateway logs that day all of them it was nothing but pages of them.

Does the log entry say "sendto" or does it say "gateway"?

@dennypage To be honest, it was a while ago when we moved, so the details are a bit fuzzy. The first ISP tech didn't know how to set up bridge mode and messed up a configuration—possibly the gateway—so they had to send a senior technician to fix it. The original installer actually called me right during a final exam. I was incredibly stressed and frustrated because he kept insisting modem-only mode wasn't possible, even though support had already told me I could use my own equipment. I feel bad because I ended up being a bit rude, telling him to just hook it up so I could deal with it later.

@johnpoz its a 256MB drive I have no idea what happened it was so weird. It was a combination of moving and ISP issues with the ISP equipment. But yes it ate my drive whatever occurred it was a misconfiguration and it kept going online and off over and over so sendto and gateway errors all at once. So maybe a cool down timer is needed a staged escalation cool down timer. Example if it down for 5 mins wait 10min test again if its down still 15mins still go to 30 if still go to 1 hour if still down go to 2hr... 4... 8 and at some point just say max reached restart dpinger. of course based on so many log writes in a min or something, I just felt like wow there is no guard rails on this one and it did it burned it up.

@JonathanLee said in dpinger 3.6:

256MB

Did you mean 256GB, don't think you could ever buy a ssd that small ;)

@johnpoz haha GB yes