Subj : Weekly nodelist report on noteworthy changes (355)
To   : Wilfred van Velzen
From : Michiel van der Vlist
Date : Fri Dec 20 2024 16:52:15

Hello Wilfred,

On Friday December 20 2024 12:46, you wrote to All:

 WV> The prolog of the Z2 nodlist contains christmas and newyears wishes
 WV> again. This is becoming a fine tradition! ;-)

Indeed. But... in the Z2daily it is in UTF-8.

 WV> "New" node in net 201:
 WV> Pvt,4609,Future_Hacker_Central,Dalarna,Joaquim_Homrighausen,-Unpublish
 WV> ed-,300,XA,MO The XA and MO flags are not useful for a Pvt node, and
 WV> can be left out.

JoHo can't set up a real node?

 WV> Hub,40 in net 5019 got the TRACE flag added.
 WV> It's an AKA of the Host system, so the Host system should also add the
 WV> TRACE flag.

Even if it is the same system, it is theoretically possible that it does not support TRACE on all AKA's...

 WV>  A ping sent to 2:5019/400 got a trace and a ping response
 WV> from 2:5019/400. The Via for the trace response however indicated it
 WV> was from 2:5019/40...

Hmm...

 WV> In Z4 XA flags were changed to XW which is correct. And nodes
 WV> 4:900/107 and 4:902/7 became PVT.

I suspect that in this case "Pvt" may be euphemistic for "Down".

 WV> Remaining binkp connectivity issues in Z4:

 WV> 4:88/0  mastodontbbs.hopto.org:24554  191.114.38.190  Error:
 WV> Connection timed out And AKA's. Probably a dynamic dns update issue
 WV> again...

Probalby something else because now it connects at that same IP: 191.114.38.190.

  16:51 [5496] creating a poll for 4:88/0@fidonet (`d' flavour)
  16:51 [5496] clientmgr started
+ 16:51 [2996] call to 4:88/0@fidonet
  16:51 [2996] trying f0.n88.z4.binkp.net [191.114.38.190]...
  16:51 [2996] connected
+ 16:51 [2996] outgoing session with f0.n88.z4.binkp.net:24554
               [191.114.38.190]
- 16:51 [2996] OPT CRAM-MD5-0bfa75bbaa4ded50a58131896cf5b110
+ 16:51 [2996] Remote requests MD mode
- 16:51 [2996] SYS Mastodont BBS
- 16:51 [2996] LOC Puerto Montt, Chile
- 16:51 [2996] ZYZ Folk3n30
- 16:51 [2996] TIME Fri, 20 Dec 2024 12:51:08 -0300
- 16:51 [2996] VER Mystic/1.12A48 binkp/1.0
- 16:51 [2996] BUILD 2023/01/15 15:30:01 Windows/64
+ 16:51 [2996] addr: 4:880/1@fidonet
+ 16:51 [2996] addr: 4:88/0@fidonet
+ 16:51 [2996] addr: 4:880/0@fidonet
- 16:51 [2996] QSIZE 0 files 0 bytes
+ 16:51 [2996] done (to 4:88/0@fidonet, OK, S/R: 0/0 (0/0 bytes))

 WV> 4:801/203 tbrasilis.ddns.net:24554  64.181.182.128  Error: Connection
 WV> refused

+ 16:56 [3604] call to 4:801/203@fidonet
  16:56 [3604] trying f203.n801.z4.binkp.net [64.181.182.128]...
  16:56 [3604] connected
+ 16:56 [3604] outgoing session with f203.n801.z4.binkp.net:24554
               [64.181.182.128]
- 16:56 [3604] OPT CRAM-MD5-886f41135f5a314d92509fb3e27f4a24
+ 16:56 [3604] Remote requests MD mode
- 16:56 [3604] SYS Terra Brasilis
- 16:56 [3604] LOC Rio de Janeiro, Brazil
- 16:56 [3604] ZYZ Marcelo Correia
- 16:56 [3604] TIME Fri, 20 Dec 2024 15:55:54 0000
- 16:56 [3604] VER Mystic/1.12A48 binkp/1.0
- 16:56 [3604] BUILD 2023/01/15 12:54:18 Linux/64
+ 16:56 [3604] addr: 4:801/203@fidonet
- 16:56 [3604] QSIZE 0 files 0 bytes
+ 16:56 [3604] done (to 4:801/203@fidonet, OK, S/R: 0/0 (0/0 bytes))
  16:56 [3604] session closed, quitting...

 WV> 4:900/108 zooropabbs.ddns.net - Error: Cannot getaddrinfo - Name or
 WV> service not known

Same here.

 WV>  It resolved 2 weeks ago...

And now it doesn't. Shit happens...


Cheers, Michiel

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

.