I am now following this issue:
https://urldefense.us/v3/__https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5201*note_124749__;Iw!!G_uCfscf7eWS!dRZVFZFavYzNg2Rm-FU6Eq76O4Nraf4aDu7NJwUA2kb3CTaAjT2JUJ1eCCtfaI2OJzSNrWoSfm4-J5mHC2n5wvuPIQSm$
Gruss Heinz
> On 14. Nov 2025, at 17:21, Heinz Junkes (FHI) via Tech-talk <[email protected]> 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:
>
> (ip 141.14.135.182 and 141.14.135.183 are two archiverAppliances running in this net)
>
> ...
> 2025-11-14T17:07:45.407564873 DEBUG pvxs.udp.io UDP Rx 428, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:45.940291259 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 00000066 00000017 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 9A570103 74637000 03000000 02124648
> 0030 : 493A4D50 3A494D4F 423A6D79 54656D70
> ...
> 2025-11-14T17:07:45.940332959 DEBUG pvxs.udp.io UDP Rx 110, 141.14.135.182:39511 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:46.398251043 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 00000577 00000011 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 2B000000 061C4648
> 0030 : 4946454C 3A524644 6174613A 4C494E31
> ...
> 2025-11-14T17:07:46.398324183 DEBUG pvxs.udp.io UDP Rx 1407, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 0000 : CA028003 0000017B 00000011 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 0B000000 07194648
> 0030 : 4946454C 3A524644 6174613A 5348425F
> ...
> 2025-11-14T17:07:46.398500943 DEBUG pvxs.udp.io UDP Rx 387, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> errlog: lost 5 messages
> 2025-11-14T17:07:46.920376898 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 0000004F 00000018 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 9A570103 74637000 02000000 02124648
> 0030 : 493A4D50 3A494D4F 423A6D79 54656D70
> ...
> 2025-11-14T17:07:46.920405489 DEBUG pvxs.udp.io UDP Rx 87, 141.14.135.182:39511 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:47.389270513 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 0000057B 00000012 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 2B000000 061C4648
> 0030 : 4946454C 3A524644 6174613A 4C494E31
> ...
> 2025-11-14T17:07:47.389340053 DEBUG pvxs.udp.io UDP Rx 1411, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 0000 : CA028003 0000019D 00000012 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 0C000000 07194648
> 0030 : 4946454C 3A524644 6174613A 5348425F
> ...
> 2025-11-14T17:07:47.389509583 DEBUG pvxs.udp.io UDP Rx 421, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> errlog: lost 7 messages
> 2025-11-14T17:07:48.380313173 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 0000057B 00000013 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 2B000000 061C4648
> 0030 : 4946454C 3A524644 6174613A 4C494E31
> ...
> 2025-11-14T17:07:48.380446583 DEBUG pvxs.udp.io UDP Rx 1411, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 0000 : CA028003 00000181 00000013 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 0B000000 021B4648
> 0030 : 4946454C 3A524644 6174613A 5348425F
> ...
> 2025-11-14T17:07:48.380662973 DEBUG pvxs.udp.io UDP Rx 393, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:48.880371388 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 00000066 0000001A 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 9A570103 74637000 03000000 02124648
> 0030 : 493A4D50 3A494D4F 423A6D79 54656D70
> ...
> 2025-11-14T17:07:48.880415578 DEBUG pvxs.udp.io UDP Rx 110, 141.14.135.182:39511 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:49.371193113 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 000004E9 00000014 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 27000000 031A4648
> 0030 : 4946454C 3A524644 6174613A 4C494E32
> ...
> 2025-11-14T17:07:49.371242433 DEBUG pvxs.udp.io UDP Rx 1265, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:49.860324188 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 00000066 0000001B 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 9A570103 74637000 03000000 02124648
> 0030 : 493A4D50 3A494D4F 423A6D79 54656D70
> ...
>
>
> 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 ]
> GUID 0x0D5DC20423F82D6367A9991D version 2: tcp@[ 141.14.131.228:42479 ]
> GUID 0x31EC156900000000A6F9DD00 version 2: tcp@[ 141.14.137.80:5075 ]
> GUID 0x3BD94CBB98B48A44F3222CAA version 2: tcp@[ 141.14.137.82:5075 ]
> GUID 0x3D28C96800000000332CF600 version 2: tcp@[ 141.14.135.248:5075 ]
> GUID 0x412CE9BBB99971C4925B7F98 version 2: tcp@[ 141.14.136.101:5075 ]
> GUID 0x78A51380147E8E0A16815C4A version 2: tcp@[ 141.14.135.182:43725 ]
> GUID 0x7F1F3778BDA21463248755EF version 2: tcp@[ 141.14.135.181:39019 ]
> GUID 0x9E7BB02B21880EF8374DC25A version 2: tcp@[ 141.14.135.182:5075 ]
> GUID 0xA2D6A7048B0325099A66752E version 2: tcp@[ 141.14.135.181:5075 ]
> GUID 0xADE023B474DF8FD6ACC071D7 version 2: tcp@[ 141.14.131.228:5075 ]
> GUID 0xBD17A7945C075D000CB3D8FA version 2: tcp@[ 141.14.136.102:5075 ]
> GUID 0xC0C2E391F3D2CD759A1A9506 version 2: tcp@[ 141.14.140.98:5075 ]
> GUID 0xF2D7806100000000509A8E35 version 2: tcp@[ 141.14.136.67:5075 ]
> GUID 0xF3072338078D3E052A4F58E4 version 2: tcp@[ 141.14.134.173:5075 ]
>
> However, when I run pvlist with GUID, the debug output on the target stops immediately:
>
> on the client:
>
> (base) hactar:~ junkes$ pvlist 0x0224EB2FE0ED7782E367B71A
> my:custom:pv
> rtems:aSubExample
> rtems:ai1
> rtems:ai2
> rtems:ai3
> rtems:aiExample
> rtems:aiExample1
> rtems:aiExample2
> rtems:aiExample3
> rtems:calc1
> rtems:calc2
> rtems:calc3
> rtems:calcExample
> rtems:calcExample1
> rtems:calcExample2
> rtems:calcExample3
> rtems:circle
> rtems:circle:angle
> rtems:circle:period
> rtems:circle:step
> rtems:circle:tick
> rtems:circle:x
> rtems:circle:y
> rtems:compressExample
> rtems:line
> rtems:line:a
> rtems:line:b
> rtems:myExample:version
> rtems:subExample
> rtems:xxxExample
>
>
>
> on the target:
>
> ...
> 2025-11-14T17:07:49.860368588 DEBUG pvxs.udp.io UDP Rx 110, 141.14.135.182:39511 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:50.362140943 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 000004FA 00000015 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 27000000 07194648
> 0030 : 4946454C 3A524644 6174613A 5348425F
> ...
> 2025-11-14T17:07:50.362181533 DEBUG pvxs.udp.io UDP Rx 1282, 141.14.135.181:53495 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:50.840340618 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA028003 0000004F 0000001C 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 9A570103 74637000 02000000 02124648
> 0030 : 493A4D50 3A494D4F 423A6D79 54656D70
> ...
> 2025-11-14T17:07:50.840393388 DEBUG pvxs.udp.io UDP Rx 87, 141.14.135.182:39511 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 2025-11-14T17:07:50.886855378 DEBUG pvxs.udp.io UDP 0x191c8a8 event 2
> 0000 : CA020003 1D000000 00000000 81000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 53F90000 00
> 2025-11-14T17:07:
>
>
>
> Could this be a sequence from pvlist on hactar (141.14.128.70)?
>
> 2025-11-14T17:16:45.626920608 DEBUG pvxs.udp.io UDP Rx 37, 141.14.128.70:62857 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> errlog: lost 22 messages
> 2025-11-14T17:16:46.359944095 DEBUG pvxs.udp.io UDP 0x191de60 event 2
> 0000 : CA020003 1D000000 00000000 81000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : 89F50000 00
> 2025-11-14T17:16:46.359979465 DEBUG pvxs.udp.io UDP Rx 37, 141.14.128.70:62857 -> 141.14.128.12:5076 @1 (0.0.0.0:5076) : orig 0
> 0000 : CA02C004 00000029 DD8CB957 8E53BA41
> 0010 : 661D4B2E 00000000 00000000 00000000
> 0020 : 0000FFFF 00000000 13D30374 63700000
> 0030 : 00
> 2025-11-14T17:16:46.360029445 DEBUG pvxs.udp.io Send 0.0.0.0:5076 -> 141.14.128.70:62857, 141.14.128.12:5076,mve0
> 2025-11-14T17:16:46.492956116 DEBUG pvxs.udp.io UDP 0x191de60 event 2
> 0000 : CA028003 00000572 00000012 00000000
> 0010 : 00000000 00000000 0000FFFF 00000000
> 0020 : D0F70103 74637000 2B000000 061C4648
> 0030 : 4946454C 3A524644 6174613A 4C494E31
> ...
>
>
> Heinz
>
>> On 13. Nov 2025, at 16:35, Michael Davidsaver <[email protected]> wrote:
>>
>> On 11/13/25 2:51 AM, Heinz Junkes (FHI) via Tech-talk wrote:
>>> Access to PVs on this host not possible with either ca or pva:
>>>
>> Oh. The implementations of RSRV and PVXS are different enough that I see this as a strong hint that there is an RTEMS/libbsd issue involved.
>> With PVXS you can turn on logging for UDP reception. I did not suggest this initially because it should be quite noisy. But in this case maybe not?
>>
>>> epicsEnvSet("PVXS_LOG", "pvxs.udp.io=DEBUG")
>>
>>
>> This will log many lines mentioning "UDP Rx". eg.
>>
>>> 2025-11-12T17:05:54.475528766 DEBUG pvxs.udp.io UDP Rx 49, 10.127.127.1:53277 -> 10.127.127.255:5076 @4 (0.0.0.0:5076) : orig 0 replyfrom 10.127.127.1:5076
>>
>>
>> You would see a different format for these lines depending on the exact version of PVXS.
>>
>
- Replies:
- Re: pvxs Access/list problem Michael Davidsaver via Tech-talk
- References:
- Re: pvxs Access/list problem Heinz Junkes (FHI) via Tech-talk
- Fwd: pvxs Access/list problem Heinz Junkes (FHI) via Tech-talk
- Re: Fwd: pvxs Access/list problem Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
RE: Modbus-TCP "authorization" Abdalla Ahmad via Tech-talk
- Next:
Re: pvxs Access/list problem Michael Davidsaver via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
<2025>
2026
- Navigate by Thread:
- Prev:
Re: Fwd: pvxs Access/list problem Michael Davidsaver via Tech-talk
- Next:
Re: pvxs Access/list problem Michael Davidsaver via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
<2025>
2026
| 
