TIP: Click on subject to list as thread! ANSI
echo: fidotest
to: Michiel van der Vlist
from: John Dovey
date: 2022-04-14 09:03:00
subject: Issues with PING function

 Mvd> Hello Flavio,

 Mvd> Thursday April 14 2022 09:29, I wrote to you:

 MV>> Two ping requests are in the pipe. One crash, one routed.

 MV>> I will try to test the TRACE functionality later.

 Mvd> No response from your PING robot yet. But I noticed something odd in the
 Mvd> via lines of a ping to 464 routed through  your system:

 Mvd> @Via 2:280/5555 @20220414.073614.608.UTC FMail-W32(Pack)
 Mvd> 2.1.3.7-B20170919 @Via 0:0/0 @20220414.043431.UTC Mystic 1.12 A47
 Mvd> @Via 4:90/1 @20220414.043743 FMail/Win32 1.60+
 Mvd> @Via 1:229/426 @20220414.033728 D'Bridge 4
 Mvd> @Via 1:229/426@fidonet @20220414.073729.UTC O/T-Track+ 2.85
 Mvd> @Via 2:280/464 @20220414.074202.227.UTC FMail-lnx64(Toss)
 Mvd> 2.1.0.18-B20170815

 Mvd> Note the 0:0/0 in the via line generated by your system. The UTC time
 Mvd> stamp is also wrong.


Flavio, 
this might be a hint. The message I get with  grunged packets has to do with an invalid DateTime...

JD

--- AfterShock/Android 1.6.8
     
* Origin: Firecat Mobile (4:920/69.1)

SOURCE: echomail via QWK@pharcyde.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.