peers UNRESPONSIVE

[lvlts]

hi.
several peers are no longer online and appear UNRESPONSIVE:

v0.0000.0000.0000.0015.kw0vfw3tmb6u6p21z5jmmymdlumwknlg3x8muk5mcw66tdpqlw30.k UNRESPONSIVE in 0kb/s out 0kb/s "Magik6k-sbg1"
v0.0000.0000.0000.001b.yrgb0xwfr9pz8swvnv6m9by8zw7v7uxxhl07qz318cjuvfgs1fc0.k UNRESPONSIVE in 0kb/s out 0kb/s "jazzanet"
v0.0000.0000.0000.0019.8268mn1bvz66nbb74tqw7ynjkcjrtruv8pgjf9kr34zv5d60p3r0.k UNRESPONSIVE in 0kb/s out 0kb/s "llygaid.cwningen.cymru"
v0.0000.0000.0000.0017.7ktfb2n336bguhfx81ts15qgjb8mjj4rz3vrnvj2dw89wsmmtpg0.k UNRESPONSIVE in 0kb/s out 0kb/s "penfar.cwningen.cymru"
v0.0000.0000.0000.0015.1nctdb89gtfrlnu71zyq97n14frl1r4z0ylwzc8vn7kpvrzu4yl0.k UNRESPONSIVE in 0kb/s out 0kb/s "igel-amersfoort"

the peers above are used, in my specific environment, only over ipv4.

are there any plans on bringing them back on?

thanks

[whoizit]

I can confirm "Magik6k-sbg1" "jazzanet" "igel-amersfoort", many days, maybe weeks or months unresponsive

[ansuz]

@magik6k, @wfleurant, any comment?

I've also pinged the other operators via email.

I know that I've been having trouble pinging nodes lately, even when they are known to be available.

If we don't get any feedback from the operators, then we can remove the listings.

[magik6k]

Should be fixed, can you confirm it's working?

[lvlts]

@magik6k: the ipv4 peer is still UNRESPONSIVE on my side. the details of the peer are the ones in magik6k.net.k

[magik6k]

Looks like it's fixed now:

$ ./peerStats | grep outer | wc -l
72

[whoizit]

yrgb0xwfr9pz8swvnv6m9by8zw7v7uxxhl07qz318cjuvfgs1fc0.k v0  fail  0    0    0    4K   jazzanet
g2xyf69w70q4q2nzfyhs5ybdhpgx0uz56zxqlj27g2ytnklqvxv0.k v0  fail  0    0    0    440B florianb
1nctdb89gtfrlnu71zyq97n14frl1r4z0ylwzc8vn7kpvrzu4yl0.k v0  fail  0    0    0    560B igel-amersfoort

[cwningen]

I've updated things; let me know if you've any issues (the keys have all changed though)

[lvlts]

@cwningen the updated IPv4 peers (coes, penfar, traed) are marked unresponsive on my side. I've tested this from two nodes on different networks.

v0.0000.0000.0000.001b.s8luk50utykxh6l228ycyrfydclcdddl0143wmg5mf0cpw42w4h0.k UNRESPONSIVE in 0kb/s out 0kb/s "coes.cwningen.cymru"                                                                                                                                               
v0.0000.0000.0000.0019.pp6c01cnz51t2vyl1jmzbply1n662c13nm6mzprx0g5djkvl3470.k UNRESPONSIVE in 0kb/s out 0kb/s "penfar.cwningen.cymru"                                                                                                                                             
v0.0000.0000.0000.0017.p8q8bsbvlr3xjh2hqlzyfcgjsk2mjm7fl8s5w73v68925n4f6nb0.k UNRESPONSIVE in 0kb/s out 0kb/s "traed.cwningen.cymru"

[cwningen]

Odd, I can see they're all up and I have connection to and can see various things through them. Although given the timing of your comment it might be down to my upstreams AS44684 having issues over the weekend. Are they still appearing down to you?

[whoizit]

can't connect to eu/ru/spb/ru.spb.tokakoka.k from 2 different PC/networks

[lvlts]

@cwningen I am exhibiting the same issues on two of my nodes, toward the peers over IPv4, maybe someone else can join in and let us know if it's working for them?

[whoizit]

Can't connect to *.swningen.cymru ipv4 from NL and from RU

[cwningen]

Odd. cjdroute was receiving the packets but not sending back on the correct address as these hosts have multiple addresses, it used the defaults. I've explicitly set the bind addresses for v4 and v6 accordingly so it should now work for others. Have confirmed it does work over v4 here post change and restart.