• Pop!_Planet is still very much under development. Data for the wiki is being sourced from the Arch Linux and Ubuntu wikis, along with a bunch of completely unique content specific to Pop!_OS, and sourcing, converting and updating that content takes time; please be patient. If you can't find what you're looking for here, check the Arch Linux and Ubuntu wikis.
  • Welcome!

    I'll get straight to the point.

    When I started Pop!_Planet, I launched it because I saw a need for a centralized community for Pop!_OS. To be frank, I never expected the level of popularity it has achieved. Over the last year, we have gone from under 50 users, to almost 400 users. That's awesome! However... it also comes with a downside. We are rapidly running out of disk space on our server, and the bandwidth costs go up every month.

    Pop!_Planet is not affiliated with System76 in any way, and is funded completely out of pocket. From day one, I said that I'd never use on-site ads (I hate them as much as you do), so the only monetization we get is through donations. Right now, the donations we receive don't even cover our overhead.

    I know that most users will ignore this message, and that's ok. However, if even a few of our users are willing and able to donate a few dollars to help offset our expenses, it would be greatly appreciated.

    Support Pop!_Planet

    Thank you for your time,

    Dan Griffiths
    Pop!_Planet Founder

Logging dropping network.

FlipChip

Member
Mar 7, 2019
87
5
11
As it happens I did this for quick'n'verydirty thigie:

Code:
#!/bin/bash

while :
do
    sleep 60 & pid=$!

    echo "
    ###################################################"

    echo "
    $(date)"

    ping -c4 -W1 www.google.com &&

    echo "
    -> connection is up"||

    echo "
    -> connection is down"

    echo "
    ###################################################"


    wait $pid
done
This is then run

Code:
njetwrkz.sh >> file
From there one can extract instances that have lost packages with:

Code:
awk '$4<4' file | grep %
To determine how many times packages weren't received:

Code:
awk '$4<4' file | grep % | wc -l
Another grep tells you how many times there has been 100% loss:

Code:
awk '$4<4' file | grep 100% | wc -l
Yes it's very dirty and just fine for the accuracy I need at the moment. Should one nee more detailed info there are real tools for this.
 

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
969
143
20
www.patreon.com
You're right, there are real tools for that already. I'm really not the one to judge but I think dirty is fine if it works. What's important here is you gave it a go and learned from it.
 

FlipChip

Member
Mar 7, 2019
87
5
11
You're right, there are real tools for that already. I'm really not the one to judge but I think dirty is fine if it works. What's important here is you gave it a go and learned from it.
Yeah. And those tools take longer time to find and install and all than write this little thingie.

Of course one gives it a go, otherwise it wouldn't be done, right?

And yes, I learned from it, but what?
 

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
969
143
20
www.patreon.com
I'm on your side. I'm really trying to keep my install slim and I'd prefer to have a functional script for one intended purpose than install a suit of tools that require a large learning curve. I find attempting to manipulate the system from CLI to be satisfying and provides insight to how everything fits together.
 

Members online

No members online now.

Latest projects

Forum statistics

Threads
777
Messages
3,544
Members
717
Latest member
Loki