R50.COORD: Очередная проверка IBN-узлов

Vladimir Fyodorov написал(а) к All в Apr 18 10:57:56 по местному времени:


> R50C осуществил очередную проверку IBN-узлов. В целом ситуация
> улучшилась, но до идеала пока далеко. Тревожная ситуация с сетями 5051,
> 5075 и 5097 (Ульяновск, Тольятти и Ухта).

=============================================================================
* Area : R50.COORD
* From : R50C, 2:5020/715.1 (17 Апреля 2018 13:59)
Subj : ** проверка IBN-узлов
=============================================================================
Приветствую Вас, All!

С момента прошлой проверки ситуация явно улучшилась (количество неотвечающих IBN-узлов сократилось почти вдвое), что не может не радовать. Тем не менее, проблемные узлы и хосты остались. Ниже приведена текущая картина. Выделены неработающие хосты. По-прежнему жду от NC соответствующих сетей осязаемой реакции на данные проблемы и напоминаю, что в их обязанности входит как актуализация сетевого сегмента, так и поддержание сетевых хостов в работоспособном состоянии. Не хочется вспоминать про 5.7 FPD, но следующий раз, если картинка не оживёт, видимо, придётся...


По живым узлам сетей 5051, 5075 и 5097 сделана директная рассылка с предложением выбрать нового NC или расформировать сети и перейти в независимые узлы. Жду реакции до конца месяца, после чего сети будут удалены из регионального сегмента.

Также обнаружилась новая проблема, характерная, как мне кажется, для узлов под jNode. Выглядит это так:

+ 17 Apr 00:05:41 [3144] call to 2:5020/570@fidonet
17 Apr 00:05:41 [3144] trying altynclub.ru [213.141.144.86]...
17 Apr 00:05:41 [3144] connected
+ 17 Apr 00:05:41 [3144] outgoing session with altynclub.ru:24554 [213.141.144.86]
- 17 Apr 00:05:41 [3144] SYS Altyn Station
- 17 Apr 00:05:41 [3144] ZYZ Dima Bargamov
- 17 Apr 00:05:41 [3144] LOC Moscow
- 17 Apr 00:05:41 [3144] NDL 115200,TCP,BINKP
- 17 Apr 00:05:41 [3144] VER jNode ver. 1.5 binkp/1.1
- 17 Apr 00:05:41 [3144] TIME Tue, 17 Apr 2018 00:03:16 +0300
- 17 Apr 00:05:41 [3144] OPT CRAM-MD5-70f2327ff2ed770444de97c29e60ae11
+ 17 Apr 00:05:41 [3144] Remote requests MD mode
? 17 Apr 00:05:41 [3144] recv: {W32 API error 10054} An existing connection was forcibly closed by the remote host
+ 17 Apr 00:05:41 [3144] done (to 2:5020/570@fidonet, failed, S/R: 0/0 (0/0 bytes))
17 Apr 00:05:41 [3144] session closed, quitting...

Причём, на парольной сессии всё ок:

+ 17 Apr 00:05:51 [1636] call to 2:5020/570@fidonet
+ 17 Apr 00:05:52 [1636] outgoing session with altynclub.ru:24554 [213.141.144.86]
- 17 Apr 00:05:52 [1636] SYS Altyn Station
- 17 Apr 00:05:52 [1636] ZYZ Dima Bargamov
- 17 Apr 00:05:52 [1636] LOC Moscow
- 17 Apr 00:05:52 [1636] NDL 115200,TCP,BINKP
- 17 Apr 00:05:52 [1636] VER jNode ver. 1.5 binkp/1.1
- 17 Apr 00:05:52 [1636] TIME Tue, 17 Apr 2018 00:03:26 +0300
- 17 Apr 00:05:52 [1636] OPT CRAM-MD5-d84aaeff28e6bb9d6f69dd93a84612f6
+ 17 Apr 00:05:52 [1636] Remote requests MD mode
+ 17 Apr 00:05:52 [1636] addr: 2:5020/570@fidonet
+ 17 Apr 00:05:53 [1636] pwd protected session (MD5)
+ 17 Apr 00:05:53 [1636] sending c:\comm\outbound\d5106606.tu0 as d5106606.tu0 (12956)
+ 17 Apr 00:05:54 [1636] sent: c:\comm\outbound\d5106606.tu0 (12956, 12956.00 CPS, 2:5020/570@fidonet)
+ 17 Apr 00:05:55 [1636] done (to 2:5020/570@fidonet, OK, S/R: 1/0 (12956/0 bytes))

Все ошибки 10054 в отчёте - это оно.


2:50/88: {W32 API error 10060} Connection timed out

>2:5000/0: Remote has no needed AKA

2:5000/99: {W32 API error 10060} Connection timed out
2:5005/14: {W32 API error 10060} Connection timed out
2:5005/67: {W32 API error 10060} Connection timed out
2:5006/26: {W32 API error 10060} Connection timed out
2:5020/570: {W32 API error 10054} An existing connection was forcibly closed by the remote host
2:5020/785: {W32 API error 10060} Connection timed out
2:5020/828: {W32 API error 10054} An existing connection was forcibly closed by the remote host
2:5020/848: {W32 API error 10054} An existing connection was forcibly closed by the remote host
2:5020/2047: {W32 API error 10054} An existing connection was forcibly closed by the remote host
2:5020/3636: {W32 API error 10060} Connection timed out
2:5022/49: {W32 API error 10060} Connection timed out
2:5023/12: {W32 API error 10060} Connection timed out
2:5023/52: {W32 API error 10061} Connection refused
2:5023/54: {W32 API error 10060} Connection timed out
2:5023/112: {W32 API error 10060} Connection timed out
2:5026/6: {W32 API error 10061} Connection refused
2:5026/16: Cannot getaddrinfo
2:5026/99: {W32 API error 10054} An existing connection was forcibly closed by the remote host
2:5030/74: {W32 API error 10060} Connection timed out
2:5030/999: {W32 API error 10060} Connection timed out
2:5030/1081: {W32 API error 10054} An existing connection was forcibly closed by the remote host
2:5030/2104: Cannot getaddrinfo
2:5033/21: {W32 API error 10061} Connection refused
2:5033/39: {W32 API error 10060} Connection timed out
2:5033/51: {W32 API error 10060} Connection timed out
2:5036/34: {W32 API error 10060} Connection timed out
2:5038/2906: Remote has no needed AKA
2:5050/55: {W32 API error 10060} Connection timed out

>2:5051/0: Cannot getaddrinfo

2:5051/40: {W32 API error 10060} Connection timed out
2:5051/41: Cannot getaddrinfo
2:5051/44: {W32 API error 10060} Connection timed out
2:5054/3: Cannot getaddrinfo

>2:5058/0: {W32 API error 10060} Connection timed out

2:5061/26: {W32 API error 10061} Connection refused
2:5061/58: {W32 API error 10061} Connection refused
2:5061/94: {W32 API error 10060} Connection timed out
2:5066/35: {W32 API error 10061} Connection refused
2:5066/109: {W32 API error 10061} Connection refused

>2:5075/0: {W32 API error 10060} Connection timed out

2:5075/5: {W32 API error 10060} Connection timed out
2:5075/23: Cannot getaddrinfo
2:5075/25: {W32 API error 10060} Connection timed out
2:5075/35: {W32 API error 10060} Connection timed out
2:5080/244: {W32 API error 10061} Connection refused

>2:5097/0: {W32 API error 10060} Connection timed out

2:5097/24: Cannot getaddrinfo
2:5097/303: {W32 API error 10060} Connection timed out

>2:6055/0: {W32 API error 10060} Connection timed out

2:6055/7: {W32 API error 10060} Connection timed out
2:6056/51: {W32 API error 10060} Connection timed out
2:6078/5: Cannot getaddrinfo
2:6078/6: Cannot getaddrinfo

Алексей Баринов
=============================================================================

--- GoldED+/W64-MSVC 1.1.5-b20170303