[CRTech] Christian Radio Tech [MSG 83445]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: Software "sniffer"
To: CRTech <crtech@crtech.org>
Subject: Re: Software "sniffer"
From: Sherrod Munday <smunday@ieee.org>
Date: Thu, 26 Jul 2018 12:40:32 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=MtQQ9N+03UhzRvQSNTZala/8dV2xKlVuPnsoij66JZk=; b=hqKSfPRVOK9+37yd7IP0Re8IIeHD1RKEoUdrQ50Lx9Aj3dhC6RYuTwB09n9vGV6tpe AmnDW6Cu5mQMtBEWPPXgZH7ND0XCIpDme51QdM36+YZYM7REDfVA3Mf8Rq0KulD0jmx7 r95kx1gEkGfKUzniqMWnhcpkBolXgULLXHfvw7AU+2p2m8s3vn9ObXV5WC4hNDV83q/M Fs9Ex4j54ojcpZdtii945PEplLDBGnWgvXywmSEhtNIfdinEMr6Q9jKk2+09m7ydX3f1 goOoeMNLOrdFpEOiNBXkZqvBVCFBTh8W/HbXVgvOrFqiRjJhDUUyBxiSN35yob6/qSsT QOVA==
In-reply-to: <CAE733jR-r48Qziqpo-01sC7i+FdgxFbT8Rms3QCL_z9MTjCr+Q@mail.gmail.com>
References: <BCE5DE6016EB46899650C223E1E270D5@ProductionPC> <847b51db-dce2-6691-b8d1-03d8c334b0b6@reyware.us> <7534891389AF481F870F468B83DFFB74@ProductionPC> <CAE733jR-r48Qziqpo-01sC7i+FdgxFbT8Rms3QCL_z9MTjCr+Q@mail.gmail.com>
On Thu, Jul 26, 2018 at 12:14 PM, Joel Force <wpgmit@gmail.com> wrote:
> When the software froze, could you access anything on the menus of the UI or
> activate the refresh button? Or was the UI totally locked up?

To build on Joel's questions:

Did the UI just stop doing what it's supposed to do but was otherwise
responsive to UI input?
Did it freeze hard and kill the UI (e.g. white window / greyed out
buttons/text, etc.) with Windows reporting that the program had
stopped responding?
Worst-case, did it crash the OS and generate a blue screen of death (BSOD)?

If the application crashed "gently" you should be able to find a
record of it in Windows' Event Logs (probably under the Application
subitem).  It might give you (and Dave) a clue as to the nature of the
The UI also has its own logging file... (See
C:\ProgramData\Reyware\Amr-100\logs for starters)

Generally, a "keepalive" or "watchdog" routine has to be built into a
program to enable something external to react to a crash of some sort.

Without that, you'd have to externally monitor the program's behavior
to determine if it's "normal."

A quick sniff with the Wireshark and Process Hacker programs shows
that the AmbOS UI software program polls the AMR-100 receiver at least
twice every minute (once for time at the top of each minute) and once
to retrieve RF Stats, etc., and then of course there's the periodic
poll of the baselist.txt file on the receiver that lists all the
contents of the AMR-100's audio files.

So, one thing you could search for is a program that can sniff network
traffic to a certain IP address and alert you if it doesn't see
traffic within a certain time window.  (Sorry, but I don't have any
quick results from Google on such a program for Windows.  Linux would
be a different story...)

If you're the programmer type, you could use a command-line packet
capture utility (like 'tshark' - a command-line interface that's part
of the Wireshark family) in a timed loop that gets reset each time a
new packet is received.  A PowerShell script would do the trick of
launching commands and allowing emails to be sent easily from within
the script with no external mail programs required.


Some other things to check:
* Run a memory tester on the computer.  Maybe you're hitting some bad
RAM and the program/OS are getting unstable?
* Bad caps on an older motherboard causing general flakiness on the computer?
* Network connections good and reliable?
* AMR-100 receiver having issues?

Just some ideas...

Sherrod Munday
References: Software "sniffer"
("Alive Radio" <events@aliveradionetwork.com>, 26 Jul 2018 14:58:22 -0000)
Re: Software "sniffer"
(dave allen <crtech-mail@reyware.us>, 26 Jul 2018 15:06:24 -0000)
Re: Software "sniffer"
("Alive Radio" <events@aliveradionetwork.com>, 26 Jul 2018 15:31:25 -0000)
Re: Software "sniffer"
(Joel Force <wpgmit@gmail.com>, 26 Jul 2018 16:15:01 -0000)
Prev by date: Re: Software "sniffer"
(Joel Force, 26 Jul 2018 16:15:01 -0000)
Next by date: Re: Software "sniffer"
(Alive Radio, 26 Jul 2018 16:41:40 -0000)
Prev by thread: Re: Software "sniffer"
(Joel Force, 26 Jul 2018 16:15:01 -0000)
Next by thread: Re: Software "sniffer"
(Alive Radio, 26 Jul 2018 16:41:40 -0000)