Hi All,

Net 463,Ukraine_Capital has been updated. 1 Node has been put on Hold, 1 Down, 1 changed from Hold to Down, and 1 changed to Pvt. And node 1331 has become the new NPK.
This also caused 2 nodes to disappear from the pointlist.

New node in net 229: ,113,Hold_Fast!,Ottawa_ON,Paul_Lopez,-Unpublished-,300,CM,INA:telnet.holdfastbb s.ca,IBN
Connect with Mystic/1.12A47

Andrew Leary has moved, and changed 5 of his nodelist entries: POTS number and flags added, and some host name changes.

In R18 in 2 nets the "Hold,99*,*New*,..." entries have been removed. But there are still a few left in the other nets.

Regards, NPC

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Nodelist,

On Friday May 20 2022 14:34, you wrote to All:

Net 463,Ukraine_Capital has been updated. 1 Node has been put on Hold,
1 Down, 1 changed from Hold to Down, and 1 changed to Pvt. And node
1331 has become the new NPK. This also caused 2 nodes to disappear
from the pointlist.

Good to see. But the NC463 is not finidhed yet. There are some more nodes in that net that need to be looked into. They give Time outs and connection refused.

New node in net 229: ,113,Hold_Fast!,Ottawa_ON,Paul_Lopez,-Unpublished-,300,CM,INA:telnet.h oldfastbb s.ca,IBN Connect with Mystic/1.12A47

Check.

Andrew Leary has moved, and changed 5 of his nodelist entries: POTS
number and flags added, and some host name changes.

OK...

In R18 in 2 nets the "Hold,99*,*New*,..." entries have been removed.
But there are still a few left in the other nets.

OK...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hello Michiel,

On 2022-05-20 15:14:58, you wrote to me:

Net 463,Ukraine_Capital has been updated. 1 Node has been put on
Hold, 1 Down, 1 changed from Hold to Down, and 1 changed to Pvt. And
node 1331 has become the new NPK. This also caused 2 nodes to
disappear from the pointlist.

MvdV> Good to see. But the NC463 is not finidhed yet. There are some more nodes
MvdV> in that net that need to be looked into. They give Time outs and connection
MvdV> refused.

Indeed:

2022-05-20 16:06:35.332 callip.pl v.0.9.4.8. -c /home/fido/etc/callip_fido.cfg -s -n 463
2022-05-20 16:06:35.341 Nodelist for Friday, May 20, 2022 -- Day number 140 parsed, 7 IP-nodes processed (0.009 sec)
2022-05-20 16:06:35.841 2:463/532 212.26.144.6:24554212.26.144.6 Error: Socket read error.
2022-05-20 16:06:36.733 2:463/68 fido.happy.kiev.ua:24554 213.133.161.33 Ok.
2022-05-20 16:06:37.464 2:463/1331 hugayda.aid.in.ua:24554 46.101.104.183 - Got error: No AKAs in common domains or all AKAs are busy.
2022-05-20 16:06:37.464 2:463/1331 hugayda.aid.in.ua:24554 2a03:b0c0:3:d0::177:d001 Ok.
2022-05-20 16:06:37.775 2:463/0 hugayda.aid.in.ua:24554 46.101.104.183 Ok. 2022-05-20 16:06:37.775 2:463/0 hugayda.aid.in.ua:24554 2a03:b0c0:3:d0::177:d001 Ok.
2022-05-20 16:06:50.562 2:463/407 f407.n463.z2.binkp.net:24554 62.149.0.100 Error: Connection timed out
2022-05-20 16:06:50.595 2:463/3232 f3232.n463.z2.binkp.net:24554 31.43.119.59 Error: Connection timed out
2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:24554 62.205.153.104 Ok.
2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:245542a0b:2bc0:ffff:21b:f1d0:2:463:877 Error: Socket read error.


Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: NPC Station (2:280/464)

Hello Nodelist,

On Friday May 20 2022 16:08, you wrote to me:

2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:24554 62.205.153.104
Ok.

2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:245542a0b:2bc0:ffff:21b:f1d0:2:463:877
Error: Socket read error.

When I force IPv4 I get a normal connect. When I do not force IPv4, an attempt to connect via IPv6 is aborted with:

{W32 API error 10054} An existing connection was forcibly closed by the remote host

... and the session closes without falling back to IPv4.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hello Nodelist,

On Friday May 20 2022 16:08, you wrote to me:

2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:24554 62.205.153.104
Ok.

2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:245542a0b:2bc0:ffff:21b:f1d0:2:463:877
Error: Socket read error.

When I force IPv4 I get a normal connect. When I do not force IPv4, an attempt to connect via IPv6 is aborted with:

{W32 API error 10054} An existing connection was forcibly closed by the remote host

... and the session closes without falling back to IPv4.

There is no answer on the POTS number.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hello Nodelist,

Friday May 20 2022 16:35, I wrote to you:

... and the session closes without falling back to IPv4.

There is no answer on the POTS number.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hello Michiel,

On 2022-05-20 16:35:15, you wrote to me:

2022-05-20 16:06:57.331 2:463/877 bbs.ncc.org.ua:24554
62.205.153.104 Ok.

2022-05-20 16:06:57.331 2:463/877
bbs.ncc.org.ua:245542a0b:2bc0:ffff:21b:f1d0:2:463:877
Error: Socket read error.

MvdV> When I force IPv4 I get a normal connect. When I do not force IPv4, an
MvdV> attempt to connect via IPv6 is aborted with:

MvdV> {W32 API error 10054} An existing connection was forcibly closed by the
MvdV> remote host

MvdV> ... and the session closes without falling back to IPv4.

Apparently binkd regards that result as a complete fail, and doesn't continue to try to connect to that node.

callip always tries every possible address for each node.

Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: NPC Station (2:280/464)

Hello Nodelist,

On Friday May 20 2022 17:23, you wrote to me:

MvdV>> When I force IPv4 I get a normal connect. When I do not force
MvdV>> IPv4, an attempt to connect via IPv6 is aborted with:

MvdV>> {W32 API error 10054} An existing connection was forcibly
MvdV>> closed by the remote host

MvdV>> ... and the session closes without falling back to IPv4.

Apparently binkd regards that result as a complete fail, and doesn't continue to try to connect to that node.

So it seems but it is the first time I see binkp behave like this.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hello Michiel,

On 2022-05-20 17:30:08, you wrote to me:

MvdV>>> When I force IPv4 I get a normal connect. When I do not force
MvdV>>> IPv4, an attempt to connect via IPv6 is aborted with:

MvdV>>> {W32 API error 10054} An existing connection was forcibly
MvdV>>> closed by the remote host

MvdV>>> ... and the session closes without falling back to IPv4.

Apparently binkd regards that result as a complete fail, and doesn't
continue to try to connect to that node.

MvdV> So it seems but it is the first time I see binkp behave like this.

I think I've seen this recently when my new providers IPv6 wasn't behaving, before I switched to the HE-net tunnel...

Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: NPC Station (2:280/464)