> On 06/02/2023 9:22 AM EDT robert evans LAST_NAME via wsjt-devel
> <wsjt-devel@lists.sourceforge.net> 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
> > <wsjt-devel@lists.sourceforge.net> 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 cheap switches do not have a monitoring capability (sometimes
> > referred to as an aggregation port). You can only see your own traffic.
> >
> > Mike W9MDB
> >
> >
> >
> >
> >
> >
> >
> >
> > On Friday, June 2, 2023 at 06:04:08 AM CDT, Peter Sumner via wsjt-devel
> > <wsjt-devel@lists.sourceforge.net> wrote:
> >
> >
> >
> >
> >
> > 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 any network problems.
> >
> > Regards,
> > Peter, vk5pj
> >
> > On Fri, Jun 2, 2023 at 4:37 PM Alex Lelievre via wsjt-devel
> > <wsjt-devel@lists.sourceforge.net> wrote:
> > > 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
> > >> <wsjt-devel@lists.sourceforge.net> wrote:
> > >>
> > >> Hello,
> > >> while WSJT-X is a small part of this puzzle, it is a key one so hence I
> > >> am posting this here. I have for a long time now been using WSJT-X (v1.8
> > >> right through to the current release for ARM v2.61 ) on a Raspberry Pi
> > >> for a dedicated WSPR station with two Icom rigs on VHF. Over time both
> > >> the Pi3 and Pi4 have been used along with tests with the Raspberry Pi 32
> > >> and 64 bit O/S. Each of these configurations have been quite stable
> > >> with the exception of the spots and status on WSPRnet just stop getting
> > >> through.
> > >>
> > >> On the last incarnation of my setup I actually loaded one of the popular
> > >> firewall packages (UFW) thinking I could then be exact by defining the
> > >> allowed apps and ports for WSJT-X to get to WSPRnet. All was good for a
> > >> few weeks then back to the no spots and no status on WSPRnet.
> > >> 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 wrong at my end?
> > >>
> > >> have looked for ways to set the WSJT-X syslogs to be more granular but
> > >> no luck so far
> > >>
> > >> Regards,
> > >> Peter, vk5pj
> > >> _______________________________________________
> > >> wsjt-devel mailing list
> > >> wsjt-devel@lists.sourceforge.net
> > >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > >
> > >
> > >
> > > _______________________________________________
> > > wsjt-devel mailing list
> > > wsjt-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > >
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
