FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции ENET.SYSOP


	Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.

Введите FGHI ссылку:

Присутствуют сообщения из эхоконференции ENET.SYSOP с датами от 10 Jul 13 21:42:12 до 03 May 24 12:02:39, всего сообщений: 12492

Ответить на сообщение

К списку сообщений

Предыдущее сообщение

Следующее сообщение

= Сообщение: 10529 из 12492 ===================================== ENET.SYSOP =
От   : Michiel van der Vlist            2:280/5555         11 Apr 21 11:33:56
Кому : Wilfred van Velzen                                  11 Apr 21 11:33:56
Тема : Why am I getting this ... #3
FGHI : area://ENET.SYSOP?msgid=2:280/5555+6072c28e
На   : area://ENET.SYSOP?msgid=2:280/5555+6071df0e
= Кодировка сообщения определена как: CP850 ==================================
Ответ: area://ENET.SYSOP?msgid=2:292/854+103a3210
Ответ: area://ENET.SYSOP?msgid=2:280/464+6072d5e0
==============================================================================
Hello Wilfred,

Saturday April 10 2021 19:22, I wrote to you:

WV>> There seems to be a problem with routing to 2:5058/0. Maybe due
WV>> to because there is a new Host for this net in this weeks
WV>> nodelist...

MV> Yes! I think that is it. Someone is using an out of date nodelist...

I think I have it figured out now. The problem is between 2:520/715 (AKA 2:50/0) and 2:5058/0. These are the vias for a ping routed via 2:5020/715 to 2:5058/0

@Via 2:280/5555 @20210411.084253.103.UTC FMail-W32(Pack) 2.1.3.7-B20170919
@Via 2:5020/715 @20210411.084333.UTC RNtrack 2.1.10/Win
@Via 2:5020/830 RNtrack 1.32/LNX/Perl 11 ┴░┴┐╦Ç 2021 11:43:34 UTC+0300
@Via 2:5058/108 FTrack 3.1.1-as10/W32 11 Apr 2021 13:47:49 UTC+0500

5058/108 is the old 5058/0. He is no longer in the nodelist, but the system is still up and running. He no longer shows the /0 AKA.

5020/715 routes mail for 5058/104 directly to 5048/104. But mail for 5058/0 is routed to 5020/830. Probably for historic reasons. This is the first error.

5020/830 routes mail for 5058/0 to 5058/108. Maybe using an old nodelist. This is the second error. The miracle is that 5058/108 correctly drops it at 5058/0. :-)

I have notified the sysops concerned.

This PING thing is really great for tracking routing problems. ;-)

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

К главной странице гейта