stayrtr and Juniper 19.4

[sarasalingam]

Hi team,

We are having issues with stay-rtr and juniper 19.4 router. We are seeing lots of retransmission and VRP are not getting update by juniper routers. We are also seeing on wireshark, "tcp window full" message on the capture. There is no issue with Cisco router running 7.7.x

show validation session    
Session                                  State   Flaps     Uptime #IPv4/IPv6 records
xx.xx.xx.xx                           Connect     4            23/5 <--- Stay-rtr
xx.xx.xx.yy                       Up          0 4d 06:26:23 343532/187642 <--- routinator

regards,
Skanda

[job]

What version of StayRTR are you running?

Are you using rpki-client?

What operating systems are in play?

Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?)

[sarasalingam]

What version of Stay-RTR are you running? [Skanda ]0.4.0 Are you using rpki-client? [Skanda] What do you mean ? What operating systems are in play? [Skanda] RHEL 7.9 and StayRTR is running as docker continer Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?) [Skanda] Yes. Same network. From: Job Snijders ***@***.***> Sent: Tuesday, 4 April 2023 4:48 PM To: bgp/stayrtr ***@***.***> Cc: Skanda Arasalingam ***@***.***>; Author ***@***.***> Subject: Re: [bgp/stayrtr] stayrtr and Juniper 19.4 (Issue #97) [External email] Please be cautious when clicking on any links or attachments. --- What version of StayRTR are you running? Are you using rpki-client? What operating systems are in play? Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?) — Reply to this email directly, view it on GitHub<#97 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVANCVCKDQMASBUAQCEBXODW7O7YPANCNFSM6AAAAAAWSH26JM>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[benjojo]

Can you try and upgrade to 0.51, but before you do that, if you could install gdb and run "gcore <stayrtr-pid>", gzip the result and maybe we can figure out a secure way to transmit the coredump for analysis

…

On Tue, 4 Apr 2023, 08:33 sarasalingam, ***@***.***> wrote: What version of Stay-RTR are you running? [Skanda ]0.4.0 Are you using rpki-client? [Skanda] What do you mean ? What operating systems are in play? [Skanda] RHEL 7.9 and StayRTR is running as docker continer Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?) [Skanda] Yes. Same network. From: Job Snijders ***@***.***> Sent: Tuesday, 4 April 2023 4:48 PM To: bgp/stayrtr ***@***.***> Cc: Skanda Arasalingam ***@***.***>; Author ***@***.***> Subject: Re: [bgp/stayrtr] stayrtr and Juniper 19.4 (Issue #97) [External email] Please be cautious when clicking on any links or attachments. --- What version of StayRTR are you running? Are you using rpki-client? What operating systems are in play? Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?) — Reply to this email directly, view it on GitHub< #97 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AVANCVCKDQMASBUAQCEBXODW7O7YPANCNFSM6AAAAAAWSH26JM>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#97 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALPK4VQ2QRCQXYWI2GWUALW7PFD7ANCNFSM6AAAAAAWSH26JM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[sarasalingam]

Ben , What is the secure channel to share some snap shots Wireshark captures ? We can catch via team or something to share some screen snap shots. Regards, Skanda Arasalingam From: Ben Cox ***@***.***> Sent: Tuesday, 4 April 2023 6:05 PM To: bgp/stayrtr ***@***.***> Cc: Skanda Arasalingam ***@***.***>; Author ***@***.***> Subject: Re: [bgp/stayrtr] stayrtr and Juniper 19.4 (Issue #97) [External email] Please be cautious when clicking on any links or attachments. --- Can you try and upgrade to 0.51, but before you do that, if you could install gdb and run "gcore <stayrtr-pid>", gzip the result and maybe we can figure out a secure way to transmit the coredump for analysis

On Tue, 4 Apr 2023, 08:33 sarasalingam, ***@***.***<mailto:***@***.***>> wrote: What version of Stay-RTR are you running? [Skanda ]0.4.0 Are you using rpki-client? [Skanda] What do you mean ? What operating systems are in play? [Skanda] RHEL 7.9 and StayRTR is running as docker continer Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?) [Skanda] Yes. Same network. From: Job Snijders ***@***.***<mailto:***@***.***>> Sent: Tuesday, 4 April 2023 4:48 PM To: bgp/stayrtr ***@***.***<mailto:***@***.***>> Cc: Skanda Arasalingam ***@***.***<mailto:***@***.***>>; Author ***@***.***<mailto:***@***.***>> Subject: Re: [bgp/stayrtr] stayrtr and Juniper 19.4 (Issue #97) [External email] Please be cautious when clicking on any links or attachments. --- What version of StayRTR are you running? Are you using rpki-client? What operating systems are in play? Are the two RTR servers located in similar places in the network topology (aka are the traceroute the same?) — Reply to this email directly, view it on GitHub< #97 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AVANCVCKDQMASBUAQCEBXODW7O7YPANCNFSM6AAAAAAWSH26JM>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***<mailto:***@***.******@***.***>>> — Reply to this email directly, view it on GitHub <#97 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALPK4VQ2QRCQXYWI2GWUALW7PFD7ANCNFSM6AAAAAAWSH26JM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub<#97 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVANCVGTS7NX2I3Z3DEIM7LW7PI2PANCNFSM6AAAAAAWSH26JM>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[benjojo]

email them to stayrtr (at) benjojo.co.uk , If you want to encrypt them you can use

Age: age1x43ujrr5f6z8wydfa8az6qz6v3dw4usxgfgk599gngkcs5f7n92qrcpa2k
GPG: https://keybase.io/benjojo

[job]

is this still an issue?

[job]

Might be related to TCP_NODELAY being set in versions older than 0.6.0. This was fixed here 5bd081b

please try with latest version, if issues still persists please open a new ticket!