Re: pvxs Access/list problem

[Michael Davidsaver via Tech-talk <tech-talk@aps.anl.gov>]

On 11/14/25 8:21 AM, Heinz Junkes (FHI) wrote:

I have now narrowed it down a little further (hopefully)

When I boot the target and use the debug messages, I get a constant stream of events:

...

When I now display pvlist on another host, I see the target (141.14.128.12):
(I can repeat this several times)

(base) hactar:~ junkes$ pvlist
GUID 0x0224EB2FE0ED7782E367B71A version 2: tcp@[ 141.14.128.12:5075 ]

...

However, when I run pvlist with GUID, the debug output on the target stops immediately:

on the client:

(base) hactar:~ junkes$ pvlist 0x0224EB2FE0ED7782E367B71A

When in "guid" mode, pvlist first sends a UDP discovery ping (same as the no argument case), then opens a TCP connection if it receives a reply with a matching GUID.  So the network traffic of the preceding should be the same as:

pvlist

pvlist 141.14.128.12:5075

If a TCP connection is the trigger, you could try to open a connection with eg. "telnet" or "netcat" and see if the UDP traffic stop coincides on TCP connect or disconnect?  Or maybe you have to send some bytes?