Not pfSense related.. but i hopefully someone can help



  • Hey, so from the shell, does anyone know if its possible and hoe i can create a script that i can run which will ping all my client antenna IP's for a set amount of time, and output the results for each IP to a text file that i can check out later?

    so for example i want it to run: ping -c 1000 192.168.10.100  and do this for each IP address that is in the script, and output its findings to a txt file.

    I am having issues with clients (who are all connected via antenna) having slowness problems with web browsing, but i cant see this problem when i check out their connection.  SO i was hoping maybe this to be a good way to say run this for a long amount of time, various times throughout the day to see whats happening.

    Looking forward to your responses.



  • I think the best way to monitor your link is using nagios or zabix.

    Logging ping is just the first step on monitoring.



  • Thanks for that.. i'll take a look at those. Have never heard of either so will see how it goes.

    What i would love is somehow having a way of testing the bandwidth of one of my clients links, for example i allocate them a connection of 2mb/1mb and they complain about speed, i would like to be able to check their connection, similar to going to a speedtest site from their computer, but doing this from my server.  Something that tellls me that their antenna is receiving 2mb/1mb or if not, then what are they receiving.

    I don't know if this is possible?



  • Hey,

    you can write a script which does the ping for you and wrote the results to a file. the shedule the scripte you can use cron (pfsense package) and start the package - lets say every 12h or so.

    But please don't ask me to write this script for you - I can not.



  • Iperf is very usefull to test bandwidth, take a look on it.



  • You could add the IPs you want to monitor as gateways under "routing". (even though these probably arent actual gateways).
    Under RRD-graphs quality you can now see how the delay to these configured pseudo-gateways behaves over time.


Log in to reply