RetroBBS - alt.bbs.mystic - Issues with PING functionality

Issues with PING functionality

<1650211790@f360.n221.z2.fidonet.org>

https://www.rocksolidbbs.com/computers/article-flat.php?id=1237&group=alt.bbs.mystic#1237

Path: i2pn2.org!i2pn.org!news.bbs.nz!.POSTED.agency.bbs.nz!not-for-mail
From: nospam.Tommi.Koivula@f360.n221.z2.fidonet.org (Tommi Koivula)
Newsgroups: alt.bbs.mystic
Subject: Issues with PING functionality
Date: Sun, 17 Apr 2022 19:07:58 +1200
Organization: Agency HUB, Dunedin - New Zealand | bbs.nz/#Fidonet
Message-ID: <1650211790@f360.n221.z2.fidonet.org>
References: <1649924243@f5555.n280.z2.fidonet.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Injection-Info: news.bbs.nz; posting-host="8IWYKlztXHa0+IViEdY46zrq8kpk7dC9fTbT74JiSDQ";
logging-data="4457"; mail-complaints-to="abuse@news.bbs.nz"
User-Agent: VSoup v1.2.9.47Beta [95/NT]
X-MailConverter: SoupGate-Win32 v1.05
X-Comment-To: Michiel van der Vlist

by: Tommi Koivula - Sun, 17 Apr 2022 07:07 UTC

* Originally in FIDOTEST
* Crossposted in MYSTIC

Thursday April 14 2022 10:13, Michiel van der Vlist wrote to Flavio Bessa:

MV> No response from your PING robot yet. But I noticed something odd in the
MV> via
MV> lines of a ping to 464 routed through your system:
MV>
MV> @Via 2:280/5555 @20220414.073614.608.UTC FMail-W32(Pack) 2.1.3.7-B20170919
MV> @Via 0:0/0 @20220414.043431.UTC Mystic 1.12 A47
MV> @Via 4:90/1 @20220414.043743 FMail/Win32 1.60+
MV> @Via 1:229/426 @20220414.033728 D'Bridge 4
MV> @Via 1:229/426@fidonet @20220414.073729.UTC O/T-Track+ 2.85
MV> @Via 2:280/464 @20220414.074202.227.UTC FMail-lnx64(Toss)
MV> 2.1.0.18-B20170815
MV>
MV> Note the 0:0/0 in the via line generated by your system. The UTC time
MV> stamp is
MV> also wrong.

I noticed the same thing happening in another Mystic. This one is running A48.

===
Via 2:221/6.6 @20220417.155028.UTC hpt/w32-wc 1.9 2022-04-14
Via 0:0/0 @20220417.114640.UTC Mystic 1.12 A48
Via 2:221/6 @20220417.155056.UTC hpt/lnx 1.9 2022-02-13
Via 2:221/1 @20220417.155144.UTC O/T-Track+ 2.85
===

'Tommi

Re: Issues with PING functionality

<208303899@f215.n129.z1.fidonet.org>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1245&group=alt.bbs.mystic#1245

copy link Newsgroups: alt.bbs.mystic

Path: i2pn2.org!i2pn.org!news.bbs.nz!.POSTED.agency.bbs.nz!not-for-mail
From: nospam.g00r00@f215.n129.z1.fidonet.org (g00r00)
Newsgroups: alt.bbs.mystic
Subject: Re: Issues with PING functionality
Date: Tue, 19 Apr 2022 15:08:57 +1200
Organization: Agency HUB, Dunedin - New Zealand | bbs.nz/#Fidonet
Message-ID: <208303899@f215.n129.z1.fidonet.org>
References: <1650211790@f360.n221.z2.fidonet.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Info: news.bbs.nz; posting-host="8IWYKlztXHa0+IViEdY46zrq8kpk7dC9fTbT74JiSDQ";
logging-data="22533"; mail-complaints-to="abuse@news.bbs.nz"
User-Agent: VSoup v1.2.9.47Beta [95/NT]
X-MailConverter: SoupGate-Win32 v1.05
X-Comment-To: Tommi Koivula

by: g00r00 - Tue, 19 Apr 2022 03:08 UTC

TK> MV> No response from your PING robot yet. But I noticed something odd in
TK> MV> lines of a ping to 464 routed through your system:
TK> MV>
TK> MV> @Via 2:280/5555 @20220414.073614.608.UTC FMail-W32(Pack) 2.1.3.7-B201
TK> MV> @Via 0:0/0 @20220414.043431.UTC Mystic 1.12 A47
TK> MV> @Via 4:90/1 @20220414.043743 FMail/Win32 1.60+

TK> I noticed the same thing happening in another Mystic. This one is

Thanks for bringing this to my attention.

I believe this was already fixed although somewhat recently, but I could be
mistaken. There was a bug where the zone wasn't fuzzy matching zone 1-4 when
pinging across FidoNet zones.

But I will make a note to set up a test between two separate zone pings here to
see what I can come up with.

.... If you choose not to decide, you still have made a choice

Heisenberg may have been here.

computers / alt.bbs.mystic / Issues with PING functionality

computers / alt.bbs.mystic / Issues with PING functionality

Subject	Author
Issues with PING functionality	Tommi Koivula
Re: Issues with PING functionality	g00r00