Hello to you all,
this might not be favoured by all but give the idea a chance, on the WSPR
decode window, the UTC time is shown in the left most column, could this
field be augmented with the Julian day of the year also? for those who do
not know what the Julian day is, simply its the day
> On 06/02/2023 9:22 AM EDT robert evans LAST_NAME via wsjt-devel
> wrote:
>
>
> You can make a hub to use with wireshark for diag.
>
>
> > On 06/02/2023 8:21 AM EDT Black Michael via wsjt-devel
> > wrote:
> >
> >
> > You would run tcpdump on the PI. You cannot watch one computer's
You can make a hub to use with wireshark for diag.
> On 06/02/2023 8:21 AM EDT Black Michael via wsjt-devel
> wrote:
>
>
> You would run tcpdump on the PI. You cannot watch one computer's network
> traffic from another computer using wireshark. Everybody uses a switch now
> and the
You would run tcpdump on the PI. You cannot watch one computer's network
traffic from another computer using wireshark. Everybody uses a switch now
and the cheap switches do not have a monitoring capability (sometimes referred
to as an aggregation port). You can only see your own traffic.
On 02.06.23 07:03, Peter Sumner via wsjt-devel wrote:
A reboot of the PI brings things back to life for a period of time
(seems to vary) but in the end my status and spot on WSPRnet stop appearing.
Looking to see if anyone has come across anything similar or any good
pointers on what might be
Hello Alex,
all other web related activities like web browsing, system update, NTP and
the like remain functional through the whole time, it appears to be on
traffic from WSJT-X that suffers.
Each of the PI's run as a headless devices and all checks are done over
VNC, which is quite sensitive to
Have you tried running WireShark on another machine and watching the traffic?
Perhaps all the traffic dies and not just WSPRnet?
alex
K6LOT
> On Jun 1, 2023, at 10:03 PM, Peter Sumner via wsjt-devel
> wrote:
>
> Hello,
> while WSJT-X is a small part of this puzzle, it is a key one so hence
