Re: [Dorset] Monitoring Internet Connectivity.
Hi Aidan On 06/03/2019 13:22, aidangcole--- via dorset wrote: Personally, I tend to use SmokePing for this type of thing https://oss.oetiker.ch/smokeping/ Took a look at this as it looked ideal, but does pull in a bunch of dependencies including Apache and a mail server. Cheers Tim On 06/03/2019 13:12, t...@ls83.eclipse.co.uk wrote: Hi Ralph On 06/03/2019 08:53, Ralph Corderoy wrote: Hi, Discussion last night included spotting if one's connection to the Internet suffered problems overnight. The conclusion was a simple script to log data for later inspection with journalctl(1) was probably good enough. Attached is such a bash script. I haven't run it as I'm in a hurry today, so bugs are left as an exercise to the reader to discover. :-) Thanks for this. In the end used the echo rather than logger so that running under nohup just writes the log to nohup.out Will let this run for a few days (with time limit removed) and see what happens. Cheers Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Monitoring Internet Connectivity.
Personally, I tend to use SmokePing for this type of thing https://oss.oetiker.ch/smokeping/ On 06/03/2019 13:12, t...@ls83.eclipse.co.uk wrote: Hi Ralph On 06/03/2019 08:53, Ralph Corderoy wrote: Hi, Discussion last night included spotting if one's connection to the Internet suffered problems overnight. The conclusion was a simple script to log data for later inspection with journalctl(1) was probably good enough. Attached is such a bash script. I haven't run it as I'm in a hurry today, so bugs are left as an exercise to the reader to discover. :-) Thanks for this. In the end used the echo rather than logger so that running under nohup just writes the log to nohup.out Will let this run for a few days (with time limit removed) and see what happens. Cheers Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Monitoring Internet Connectivity.
Hi Ralph On 06/03/2019 08:53, Ralph Corderoy wrote: Hi, Discussion last night included spotting if one's connection to the Internet suffered problems overnight. The conclusion was a simple script to log data for later inspection with journalctl(1) was probably good enough. Attached is such a bash script. I haven't run it as I'm in a hurry today, so bugs are left as an exercise to the reader to discover. :-) Thanks for this. In the end used the echo rather than logger so that running under nohup just writes the log to nohup.out Will let this run for a few days (with time limit removed) and see what happens. Cheers Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] Notes from Bournemouth Pub Meeting Tonight, Tuesday 2019-03-05.
Following on from my question and Ralph's suggestion, I looked at Arch Linux wiki and it suggests that to find out if I can use my dongle in a software Access Point I run iw list. Under supported Interface Modes it needs to have 'AP'. it doesn't. peterm@peterm-MBB-34204H:~$ iw list Wiphy phy0 max # scan SSIDs: 4 max scan IEs length: 2257 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CCMP-256 (00-0f-ac:10) * GCMP-128 (00-0f-ac:8) * GCMP-256 (00-0f-ac:9) Available Antennas: TX 0 RX 0 Supported interface modes: * managed * monitor Band 1: Capabilities: 0x17e HT20/HT40 Peter M. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] Monitoring Internet Connectivity.
Hi,
Discussion last night included spotting if one's connection to the
Internet suffered problems overnight. The conclusion was a simple
script to log data for later inspection with journalctl(1) was probably
good enough. Attached is such a bash script. I haven't run it as I'm
in a hurry today, so bugs are left as an exercise to the reader to
discover. :-)
mtr(1) was also mentioned, e.g. `mtr -i3 8.8.4.4'.
--
Cheers, Ralph.
#! /bin/bash
progname=${0##*/}
peer=8.8.8.8 # Google's Public DNS server.
wait=3 # Seconds to wait for pong.
breather=61 # Seconds between pings to avoid taxing $peer.
today=$(date +%d) # Stop at the end of the day.
lastr=start
let sent=0 changes=0
while true; do
# ping(1)'s -w ignores -c and a timeout doesn't affect exit(2),
# so use timeout(1).
timeout $wait ping -qc1 $peer >/dev/null
r=$?
let sent++
if [[ $r != $lastr ]]; then
echo logger -t $progname $peer: transition: $lastr to $r
lastr=$r
let changes++
fi
[[ $(date +%d) == $today ]] || break
sleep $breather
done
echo $progname: sent: $sent changes: $changes
--
Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
