Weekly nodelist report on noteworthy changes (311)
From Wilfred van Velzen@2:280/464 to All on Friday, November 07, 2025 11:57:04
Hi All,
New ZIN in Z1:
Pvt,100,Ozz_Nixon,Crestview_FL,Ozz_Nixon,-Unpublished-,300
There is nothing to test. And a Pvt node is not allowed in a ZIN section anyway.
Nodes:
,111,Alien_Signals_BBS,Dutton_ON,Scott_Carter Down,550,Point_Of_No_Return,Toronto_ON,Mark_Da_Silva
Were removed from Net 229.
Node:
,2,Election_Coodinator,Buffalo_NY,Robert_Wolfe
In R13, is still present in the Z2 weekly, that's probably because of: Zone,1,North_America_(309)
Which is 2 days behind the current day. :-(
Regards, Wilfred
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, November 14, 2025 12:40:09
Hi All,
On 2025-11-07 11:57:04, I wrote to you:
Node:
,2,Election_Coodinator,Buffalo_NY,Robert_Wolfe
In R13, is still present in the Z2 weekly, that's probably because of: Zone,1,North_America_(309)
Which is 2 days behind the current day. :-(
This RIN is now also gone from the Z2 nodelist.
Node: ,20,Omicron_Theta,Memphis_TN,Robert_Wolfe is still present in net 261.
Other than that, there are no noteworthy changes this week.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, November 21, 2025 12:52:26
Hi All,
The nodes of Stephen_Hurd in net 103 are updated.
Node 1 had an INA flag added:
1:103/1 bbsdev.net:24554 2001:19f0:6000:94c9::81:241 Ok.
1:103/1 bbsdev.net:24554 45.32.81.241 Ok.
Node 13 is no longer Pvt:
1:103/13 wd1cks.org:24554 2001:19f0:6000:94c9::68:234 Ok.
1:103/13 wd1cks.org:24554 45.32.68.234 Ok.
Node 17 had the ITN flag removed
Only issue remaining in net 103 is with the host:
1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.
In net 135 node was removed:
,230,Nite_Eyes_BBS,Davie_FL,Alex_Corris
New RIN in R19: ,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chipcunk.synchro.net,IBN
It is not a CM node, but if it isn't online you don't expect a TCP/IP connect at all:
+ 21 Nov 12:40:29 [21570] call to 1:19/42@fidonet
21 Nov 12:40:31 [21570] trying chipcunk.synchro.net [74.208.78.19]...
21 Nov 12:40:31 [21570] connected
+ 21 Nov 12:40:31 [21570] outgoing session with chipcunk.synchro.net:24554 [74.208.78.19]
? 21 Nov 12:40:31 [21570] recv: connection closed by foreign host
+ 21 Nov 12:40:31 [21570] done (to 1:19/42@fidonet, failed, S/R: 0/0 (0/0 bytes))
Node 2:221/360 has got the IVM flag added. There is a TCP/IP connect at the default IVM poort (3141), but I can't test the protocol. ;-)
New node in net 341: ,207,Citrick_BBS,Tenerife,Tanausu_Martin_Gonzalez,-Unpublished-,300,CM,XW,IBN:citlmbbs.synchro.net
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21a/FreeBSD
Node 2:5031/52 was put on Hold.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Saturday, November 22, 2025 21:51:18
Hello Wilfred,
On Friday November 21 2025 12:52, you wrote to All:
New RIN in R19: ,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chip cunk.synchro.net,IBN
It is not a CM node, but if it isn't online you don't expect a TCP/IP connect at all:
Or a connect anyway, despite the ZMH restriction. I get a connect:
+ 21:50 [5920] call to 1:19/42@fidonet
21:50 [5920] trying f42.n19.z1.binkp.net [157.250.195.244]...
21:50 [5920] connected
+ 21:50 [5920] outgoing session with f42.n19.z1.binkp.net:24554
[157.250.195.244]
- 21:50 [5920] OPT CRAM-MD5-bae787e19231ee85a60856e1309fd668 CRYPT
+ 21:50 [5920] Remote requests MD mode
+ 21:50 [5920] Remote requests CRYPT mode
- 21:50 [5920] SYS The Ham Shack BBS
- 21:50 [5920] ZYZ Brian Scott
- 21:50 [5920] LOC Siloam Springs, Ar.
- 21:50 [5920] NDL 115200,TCP,BINKP
- 21:50 [5920] TIME Sat Nov 22 2025 14:50:03 GMT-0600 (CST)
- 21:50 [5920] VER BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux binkp/1.1
+ 21:50 [5920] addr: 1:19/42@fidonet
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Saturday, November 22, 2025 23:52:29
Hi Michiel,
On 2025-11-22 21:51:18, you wrote to me:
New RIN in R19:
,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chi
pcunk.synchro.net,IBN
It is not a CM node, but if it isn't online you don't expect a TCP/IP
connect at all:
MvdV> Or a connect anyway, despite the ZMH restriction. I get a connect:
MvdV> + 21:50 [5920] call to 1:19/42@fidonet
MvdV> 21:50 [5920] trying f42.n19.z1.binkp.net [157.250.195.244]...
MvdV> 21:50 [5920] connected
MvdV> + 21:50 [5920] outgoing session with f42.n19.z1.binkp.net:24554
MvdV> [157.250.195.244]
MvdV> - 21:50 [5920] OPT CRAM-MD5-bae787e19231ee85a60856e1309fd668 CRYPT
MvdV> + 21:50 [5920] Remote requests MD mode
MvdV> + 21:50 [5920] Remote requests CRYPT mode
MvdV> - 21:50 [5920] SYS The Ham Shack BBS
MvdV> - 21:50 [5920] ZYZ Brian Scott
MvdV> - 21:50 [5920] LOC Siloam Springs, Ar.
MvdV> - 21:50 [5920] NDL 115200,TCP,BINKP
MvdV> - 21:50 [5920] TIME Sat Nov 22 2025 14:50:03 GMT-0600 (CST)
MvdV> - 21:50 [5920] VER BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux binkp/1.1
MvdV> + 21:50 [5920] addr: 1:19/42@fidonet
Same here, now...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Andrew Leary@1:320/219 to Wilfred van Velzen on Sunday, November 23, 2025 07:09:22
Hello Wilfred!
21 Nov 25 12:52, you wrote to all:
Node 2:221/360 has got the IVM flag added. There is a TCP/IP connect
at the default IVM poort (3141), but I can't test the protocol. ;-)
Attempting to poll using my OS/2 VMODEM capable system resulted in "NO CARRIER" so there still seems to be some kind of issue. I can confirm that ITN sessions to the listed port are answered by FrontDoor/2 and mbcico was able to negotiate a successful WaZOO/EMSI session.
From Tommi Koivula@2:221/360 to Andrew Leary on Sunday, November 23, 2025 14:58:33
Sunday November 23 2025 07:09, Andrew Leary wrote to Wilfred van Velzen:
Hello Wilfred!
21 Nov 25 12:52, you wrote to all:
Node 2:221/360 has got the IVM flag added. There is a TCP/IP
connect at the default IVM poort (3141), but I can't test the
protocol. ;-)
Attempting to poll using my OS/2 VMODEM capable system resulted in "NO
CARRIER" so there still seems to be some kind of issue. I can
confirm that ITN sessions to the listed port are answered by
FrontDoor/2 and mbcico was able to negotiate a successful WaZOO/EMSI session.
Thanks for testing.
There might to be some issue with inbound vmodem connections via haproxy. :)
'Tommi
--- GEcho/2 1.20/Pro
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)
From Tommi Koivula@2:221/360 to Andrew Leary on Sunday, November 23, 2025 17:17:33
Sunday November 23 2025 14:58, Tommi Koivula wrote to Andrew Leary:
Attempting to poll using my OS/2 VMODEM capable system resulted
in "NO
CARRIER" so there still seems to be some kind of issue. I can
confirm that ITN sessions to the listed port are answered by
FrontDoor/2 and mbcico was able to negotiate a successful
WaZOO/EMSI session.
Thanks for testing.
There might to be some issue with inbound vmodem connections via
haproxy. :)
However, I tried to poll you but I get:
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"
'Tommi
--- GEcho/2 1.20/Pro
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)
From Andrew Leary@1:320/219 to Tommi Koivula on Sunday, November 23, 2025 12:33:26
Hello Tommi!
23 Nov 25 17:17, you wrote to me:
Attempting to poll using my OS/2 VMODEM capable system resulted
in "NO
CARRIER" so there still seems to be some kind of issue. I can
confirm that ITN sessions to the listed port are answered by
FrontDoor/2 and mbcico was able to negotiate a successful
WaZOO/EMSI session.
Thanks for testing.
There might to be some issue with inbound vmodem connections via
haproxy. :)
However, I tried to poll you but I get:
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"
I had turned the firewall rule off while testing something and promptly forgot to re-enable it. Fixed now.
From Tommi Koivula@2:221/360 to Andrew Leary on Sunday, November 23, 2025 19:59:43
Sunday November 23 2025 12:33, Andrew Leary wrote to Tommi Koivula:
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket
3141 1-23 17:16 TCP/IP says "Connection refused" 1-23 17:16
Outgoing to 24.62.213.214 from COM5 on port/socket 3141 1-23
17:16 TCP/IP says "Connection refused"
I had turned the firewall rule off while testing something and
promptly forgot to re-enable it. Fixed now.
Yes, the port is now open, but I cannot connect.
ATDT "#BBS.BNBBBS.NET"
NO CARRIER
11-23 19:58 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
11-23 19:58 We are negotiating with the remote
11-23 19:58 COM5 disconnected
11-23 19:58 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
11-23 19:58 We are negotiating with the remote
11-23 19:58 COM5 disconnected
11-23 19:58 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
11-23 19:58 We are negotiating with the remote
11-23 19:58 COM5 disconnected
23 Nov 19:58:40 XEN Mailing noname (1:320/119)
23 Nov 19:58:40 XEN Assuming ID 2:221/360@fidonet
23 Nov 19:58:40 XEN Dialling bbs.bnbbbs.net (cm,vmp,tel)
23 Nov 19:58:43 XEN No connect (no carrier)
23 Nov 19:58:46 XEN Mailing noname (1:320/119)
23 Nov 19:58:46 XEN Assuming ID 2:221/360@fidonet
23 Nov 19:58:46 XEN Dialling bbs.bnbbbs.net (cm,vmp,tel)
23 Nov 19:58:49 XEN No connect (no carrier)
Well, I'll turn IVM off, like it has been for many years. ITN works. ;)
'Tommi
--- GEcho/2 1.20/Pro
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)
From Wilfred van Velzen@2:280/464 to All on Friday, November 28, 2025 12:32:39
Hi All,
On 2025-11-21 12:52:26, I wrote to you:
Only issue remaining in net 103 is with the host:
1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.
No change here.
New RIN in R19: ,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chi pcunk.synchro.net,IBN
It is not a CM node, but if it isn't online you don't expect a TCP/IP connect
at all
The system name, location, and INA for this RIN were updated: ,42,The_Ham_Shack_BBS,Siloam_Springs_AR,Brian_Scott,-Unpublished-,300,XA,INA:hamshack.synchro.net,IBN
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, November 28, 2025 12:41:38
Hi All,
New node in net 124: ,75,The_Ham_Shack_BBS,Siloam_Springs_AK,Brian_Scott,-Unpublished-,300,CM,XW,INA:hamshack.synchro.net,IBN
This is the same system as RIN 1:19/42. So connect, but this new AKA hasn't been configured yet.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Friday, November 28, 2025 12:39:07
Hi Tommi,
On 2025-11-23 19:59:43, you wrote to Andrew Leary:
Well, I'll turn IVM off, like it has been for many years.
Confirmed, it has been removed from your nodelist entries. ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Kurt Weiske@1:218/700 to Wilfred van Velzen on Saturday, November 29, 2025 10:10:15
Wilfred van Velzen wrote to All <=-
Hi All,
On 2025-11-21 12:52:26, I wrote to you:
Only issue remaining in net 103 is with the host:
1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.
No change here.
That's not a nodelist issue, that's a configuration issue on my board -
which I've fixed. My board wasn't configured with 1023/0. Thanks for
letting me know.
From Wilfred van Velzen@2:280/464 to Kurt Weiske on Saturday, November 29, 2025 22:59:28
Hi Kurt,
On 2025-11-29 10:10:15, you wrote to me:
Only issue remaining in net 103 is with the host:
1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.
No change here.
That's not a nodelist issue,
That depends on how you look at it. Reality is different from the nodelist. ;-)
that's a configuration issue on my board - which I've fixed. My board wasn't configured with 1023/0. Thanks for letting me know.
Not yet:
Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.333
Nodelist for Saturday, November 29, 2025 -- Day number 333 parsed, 935 IP-nodes processed (0.013 sec)
Calling '1:103/0'. Call time: '0000-2400' UTC.
Now is: 2159 UTC.
realitycheckbbs.org, 24554
Calling 1:103/0 (73.158.236.238:24554)
OPT CRAM-MD5-7418ea8b688dd86826317567bd34e120 CRYPT
SYS realitycheckBBS
ZYZ Kurt Weiske
LOC Aptos, CA
NDL 115200,TCP,BINKP
TIME Sat Nov 29 2025 13:59:02 GMT-0800 (Pacific Standard Time)
VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:13/0@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Dan Clough@1:135/115 to Wilfred van Velzen on Saturday, November 29, 2025 21:48:43
Wilfred van Velzen wrote to Kurt Weiske <=-
That's not a nodelist issue,
That depends on how you look at it. Reality is different from the nodelist. ;-)
that's a configuration issue on my board - which I've fixed. My board wasn't configured with 1023/0. Thanks for letting me know.
Not yet:
Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.333
Nodelist for Saturday, November 29, 2025 -- Day number 333 parsed, 935 IP-nodes processed (0.013 sec) Calling '1:103/0'. Call time:
'0000-2400' UTC.
Now is: 2159 UTC.
realitycheckbbs.org, 24554
Calling 1:103/0 (73.158.236.238:24554)
OPT CRAM-MD5-7418ea8b688dd86826317567bd34e120 CRYPT
SYS realitycheckBBS
ZYZ Kurt Weiske
LOC Aptos, CA
NDL 115200,TCP,BINKP
TIME Sat Nov 29 2025 13:59:02 GMT-0800 (Pacific Standard Time)
VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:13/0@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.
According to this, he's also RC13 (which he is not).
Come on, Weiske. Do better ferchrissakes. You're a fuckin RC,
supposedly. Quit acting like a clueless n00b.
... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.32-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Sunday, November 30, 2025 09:59:23
* Originally in NODELIST-POLICE
* Crossposted in OS2
28 Nov 25 12:39, Wilfred van Velzen wrote to Tommi Koivula:
Well, I'll turn IVM off, like it has been for many years.
Confirmed, it has been removed from your nodelist entries. ;-)
Yep, VMODEM was pretty nice once, but that was 30 years ago, before BinkP. ;-)
But I still wonder why it works locally in my home network, but does not over the internet. Can anyone confirm a working VMODEM link over the internet? There are not so many IVM flags in the nodelist and some of those are not VMODEM but TELNET servers.
'Tommi
---
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)
From Wilfred van Velzen@2:280/464 to Kurt Weiske on Friday, December 05, 2025 12:40:03
Hi Kurt,
On 2025-11-29 22:59:28, I wrote to you:
1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.
No change here.
That's not a nodelist issue,
that's a configuration issue on my board - which I've fixed. My board
wasn't configured with 1023/0. Thanks for letting me know.
Not yet:
Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.333
Nodelist for Saturday, November 29, 2025 -- Day number 333 parsed, 935 IP-nodes processed (0.013 sec) Calling '1:103/0'. Call time: '0000-2400' UTC.
Now is: 2159 UTC. realitycheckbbs.org, 24554 Calling 1:103/0 (73.158.236.238:24554) OPT CRAM-MD5-7418ea8b688dd86826317567bd34e120 CRYPT SYS
realitycheckBBS ZYZ Kurt Weiske LOC Aptos, CA NDL 115200,TCP,BINKP TIME Sat
Nov 29 2025 13:59:02 GMT-0800 (Pacific Standard Time) VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:13/0@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.
Still not fixed:
Calling '1:103/0'. Call time: '0000-2400' UTC.
Now is: 1138 UTC.
realitycheckbbs.org, 24554
Calling 1:103/0 (73.158.236.238:24554)
OPT CRAM-MD5-2f51796bc88f8ff6226132dfa55f80a5 CRYPT
SYS realitycheckBBS
ZYZ Kurt Weiske
LOC Aptos, CA
NDL 115200,TCP,BINKP
TIME Fri Dec 05 2025 03:38:53 GMT-0800 (Pacific Standard Time)
VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.
But the 1:13/0 aka is at least gone! ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, December 05, 2025 12:42:53
Hi All,
On 2025-11-28 12:41:38, I wrote to you:
New node in net 124: ,75,The_Ham_Shack_BBS,Siloam_Springs_AK,Brian_Scott,-Unpublished-,300 ,CM,XW,INA:hamshack.synchro.net,IBN
This is the same system as RIN 1:19/42. So connect, but this new AKA hasn't been configured yet.
Not fixed yet.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, December 05, 2025 12:54:44
Hi All,
New node in net 229: ,134,The_Montreal_Geek_Times,Montreal_QC,Dimitri_Papadopoulos,-Unpublished-,300,CM,INA:bbs.greektimes.ca,IBN
Connect OK with BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux
Host entry 1:320/0 and node 1:320/119, got the IVM flag removed. ;-)
New node in net 135: ,260,Overfit,Bridgetown_Barbados,John_Merritt,-Unpublished-,300,CM,INA:overfit.retrievo.xyz,IBN
Connect OK with BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux
New node in net 280: ,2070,The_Forze,Almere,Robbert_Langezaal,-Unpublished-,300,CM,IBN:bbs.theforze.eu
Connect with Mystic/1.12A49 binkp/1.0
But:
address: 2:280/9999@fidonet
No such AKA.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)
From Tommi Koivula@2:221/1.1530 to Wilfred van Velzen on Friday, December 05, 2025 19:54:17
05 Dec 25 12:54, Wilfred van Velzen wrote to All:
Host entry 1:320/0 and node 1:320/119, got the IVM flag removed. ;-)
From Wilfred van Velzen@2:280/464 to All on Friday, July 31, 2026 12:08:16
Hi All,
In net 221, nodes 0, 1, 6 and 360 got the IFC flag added.
I get a tcp/ip connect on the IFC port. I receive this string: "binkleyforce 0.27.1/linux-gnu (c) 1997-2000 by Alexander Belkin, 2004-2026 fidonet members", and an EMSI string. On 360 the received string is different: "[CONNECT TCP/IP/192.168.1.127/IFC] T-Mail v.2608.OS2/TCP/IP/Noncommercial (C) 1992-99 by Andy Elkin"
"New" node in net 292: Pvt,140,Light_System,Somewhere,Rudi_Timmermans,-Unpublished-,300,MO
New net in Region 56: Host,385,NC-Montenegro,Heringen_(Werra),Ulrich_Schroeter,-Unpublished-,300,CM,XA,MO,IBN,INA:ambrosia60.spdns.eu,U,ENC,CDP
Pvt,180,Little_Station,Montenegro,Tolik_Vdovichev,-Unpublished-,300,MO
Connect OK with the host, which is just another aka for Ulrich. ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Friday, July 31, 2026 14:45:39
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Friday, July 31, 2026 15:42:43
Hi Michiel,
On 2026-07-31 14:45:39, you wrote to me:
Pvt,180,Little_Station,Montenegro,Tolik_Vdovichev,-Unpublished-,300,M
O
MvdV> MO flag makes no sense for a Pvt node.
Indeed, and the same goes for the other Pvt node (Rudi), in my report...
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, August 07, 2026 12:09:44
Hi All,
New node in net 221: ,250,Twilight_Node,Solvesborg,Peter_London,-Unpublished-,300,CM,INA:twilightnode.org,IBN
Connect OK with: binkd/1.1a-115/Linux
But I think these AKA's: 2:20/9999@fidonet 2:221/9999@fidonet can be removed from his binkd config now. ;-)
New node in net 341: ,202,Vampire_BBS,Madrid,Antonio_Hernandez_Lopez,-Unpublished-,300,IBN,ITN,INA:bbs.vampirebbs.org
Connect OK with: ENiGMA/0.4.0 (new to me)
In net 5053, node 58 became a Hub for node 56. Hold node 59 was removed.
In net 633, node was marked Down ,414,Wicked_Garden_BBS,Burnside_Vic,Hung_Tran I get a connection refused when trying to connect.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Friday, August 07, 2026 12:48:01
Hello Wilfred,
On Friday August 07 2026 12:09, you wrote to All:
New node in net 221: ,250,Twilight_Node,Solvesborg,Peter_London,-Unpublished-,300,CM,INA:tw ilightnode.org,IBN Connect OK with: binkd/1.1a-115/Linux But I think
these AKA's: 2:20/9999@fidonet 2:221/9999@fidonet can be removed from
his binkd config now. ;-)
2:221/9999@fidonet has been removed already. 2:20/9999@fidonet is still there.
New node in net 341: ,202,Vampire_BBS,Madrid,Antonio_Hernandez_Lopez,-Unpublished-,300,IBN, ITN,INA:bbs.vampirebbs.org Connect OK with: ENiGMA/0.4.0 (new to me)
New to me too.
- 12:47 [4540] TIME Fri, 07 Aug 2026 10:46:44 GMT
It flags the time in GMT, so t is probably not alll that new. GMT has been replaced bu UTC decades ago...
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to All on Friday, August 14, 2026 13:14:02
Hi All,
On 2026-08-07 12:09:44, I wrote to you:
New node in net 221: ,250,Twilight_Node,Solvesborg,Peter_London,-Unpublished-,300,CM,INA:t wilightnode.org,IBN
Connect OK with: binkd/1.1a-115/Linux But I think these AKA's: 2:20/9999@fidonet 2:221/9999@fidonet can be removed from his binkd
config now. ;-)
Not fixed yet.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, August 14, 2026 14:16:19
Hi All,
Net 263 Ireland is gone from the nodelist, that must be a mistake!?
In net 5020 node 843 and 814 are put on Hold.
Their domain names don't resolve...
In net 385 no longer Pvt: ,180,Little_Station,Montenegro,Tolik_Vdovichev,-Unpublished-,300,CM,MO,IBN,INA:ls.vdovichev.me
Connect OK with: AfterShock/macOS 0.1.1
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Friday, August 21, 2026 10:21:18
Hello Wilfred,
On Friday August 14 2026 13:14, you wrote to All:
New node in net 221:
,250,Twilight_Node,Solvesborg,Peter_London,-Unpublished-,300,CM,
INA:t wilightnode.org,IBN Connect OK with: binkd/1.1a-115/Linux
But I think these AKA's:
2:20/9999@fidonet 2:221/9999@fidonet can be removed from his
binkd config now. ;-)
Not fixed yet.
Still not fixed.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Tommi Koivula@2:221/360.8110 to Michiel van der Vlist on Friday, August 21, 2026 12:35:31
Hello, Michiel!
Michiel van der Vlist wrote:
Hello Wilfred,
On Friday August 14 2026 13:14, you wrote to All:
New node in net 221:
,250,Twilight_Node,Solvesborg,Peter_London,-Unpublished-,300,CM,
INA:t wilightnode.org,IBN Connect OK with: binkd/1.1a-115/Linux
But I think these AKA's:
2:20/9999@fidonet 2:221/9999@fidonet can be removed from his
binkd config now. ;-)
Not fixed yet.
Still not fixed.
Actually, the nodelisted address is there. So everything related to the police department is ok. ;)
From Wilfred van Velzen@2:280/464 to All on Friday, August 21, 2026 11:42:02
Hi All,
On 2026-08-14 14:16:19, I wrote to you:
Net 263 Ireland is gone from the nodelist, that must be a mistake!?
Ireland is back:
2:263/0 binkd.rima.ie:24554 2a06:5900:8194:100:acb:a059:6e85:1ded Ok. 2:263/0 binkd.rima.ie:24554 51.182.63.136 Ok.
2:263/1 binkd.rima.ie:24554 2a06:5900:8194:100:acb:a059:6e85:1ded Ok. 2:263/1 binkd.rima.ie:24554 51.182.63.136 Ok.
2:263/5 the.alienmindbenders.net:24554 2001:67c:0:b00:214:2aff:fe14:cead Error: No route to host
2:263/5 the.alienmindbenders.net:24554 195.43.155.90 Ok.
There is a Mystic bbs presenting a login prompt on the ITN port, so that flag is not correct.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Friday, August 21, 2026 12:03:59
Hello Tommi,
On Friday August 21 2026 12:35, you wrote to me:
2:20/9999@fidonet 2:221/9999@fidonet can be removed from his
binkd config now. ;-)
Not fixed yet.
Still not fixed.
Actually, the nodelisted address is there. So everything related to
the police department is ok. ;)
I do not see 2:20/9999 in z2daily.233.
If it is present in nodelist.233 and not in the dailies, there is another problem.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to All on Friday, August 28, 2026 12:17:23
Hi All,
On 2026-08-21 11:42:02, I wrote to you:
2:263/5 the.alienmindbenders.net:24554
2001:67c:0:b00:214:2aff:fe14:cead Error: No route to host
2:263/5 the.alienmindbenders.net:24554 195.43.155.90 Ok.
This host name still has an AAAA record, but somehow my binkd now only tries the IPv4 address. So it seems somewhat resolved.
There is a Mystic bbs presenting a login prompt on the ITN port, so that flag
is not correct.
This is not corrected.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, July 03, 2026 12:54:06
Hi All,
New node in net 114: ,30,The_SmallTime_BBS,Apache_Junction_AZ,John_Peasley,-Unpublished-,300,CM,INA:smalltimebbs.firehawke.net,IBN
Connect with: ANetBBS/1.0a
Never heard of that one.
But "No such AKA.", so his config needs to be updated.
New node in net 135: ,386,K4JTT_BBS,Titusville_FL,Ricky_DeLuco,-Unpublished-,300,CM,INA:k4jttbbs.ddns.net,IBN:24555
Connect OK with: Mystic/1.12A48
In net 203 node was updated: ,910,Rabarber,Skelleftea,Alexey_Matrosov,-Unpublished-,300,CM,LO,IBN,INA:1celand1.duckdns.org
Connect OK with: binkd/1.1a-115/Linux
In net 5020 node was updated: ,2613,NoZDR,Moscow,Ruslan_Marchenko,-Unpublished-,300,MO,CM,IBN,INA:nozdr.ru
No phone number anymore, and a changed INA.
# host nozdr.ru
Host nozdr.ru not found: 3(NXDOMAIN)
New node in net 382: ,736,Jegornet,Belgrade,Yegor_Gluhov,-Unpublished-,300,CM,MO,IBN,INA:ftn.jegor.net
Connect on both IPv4 and IPv6 with: binkd/1.1a-115/Linux
But: "No such AKA."
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, July 10, 2026 12:14:52
Hi All,
Node 1:135/260 was directly removed. (,260,Overfit,Bridgetown_Barbados,John_Merritt)
Node 3:633/295 got the XR flag added, which can't be right for a IBN only node. You can't speak the 'bark' protocol on a binkp connection. Bark is modem connections only.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, July 10, 2026 12:15:06
Hi All,
On 2026-07-03 12:54:06, I wrote to you:
New node in net 114: ,30,The_SmallTime_BBS,Apache_Junction_AZ,John_Peasley,-Unpublished-,3 00,CM,INA:smalltimebbs.firehawke.net,IBN
Connect with: ANetBBS/1.0a Never heard of that
one.
But "No such AKA.", so his config needs to be updated.
The AKA problem was fixed.
In net 5020 node was updated: ,2613,NoZDR,Moscow,Ruslan_Marchenko,-Unpublished-,300,MO,CM,IBN,INA:n ozdr.ru
No phone number anymore, and a changed INA.
# host nozdr.ru
Host nozdr.ru not found: 3(NXDOMAIN)
The INA for this node was changed to: INA:2613.ru
Connect OK with: binkd/1.1a-49/Win32
New node in net 382: ,736,Jegornet,Belgrade,Yegor_Gluhov,-Unpublished-,300,CM,MO,IBN,INA:f tn.jegor.net
Connect on both IPv4 and IPv6 with: binkd/1.1a-115/Linux
But: "No such AKA."
Tha AKA problem was fixed.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, July 17, 2026 12:39:50
Hi All,
In net 2320 node was removed: ,106,Captest,Frankfort_KY,Mike_Powell,-Unpublished-,300,CM,MO,XA,INA:capitolcityonline.net,IBN:24556
This was 1 of the 4 nodes of the net Host. So plenty left. ;-)
In net 250 node was removed: ,17,Nottingham_BBS,Nottingham,Richard_Bagshaw,-Unpublished-,300,CM,XX,INA:nottinghambbs.com,IBN
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Friday, July 17, 2026 12:40:00
Hi All,
On 2026-07-10 12:14:52, I wrote to you:
Node 3:633/295 got the XR flag added, which can't be right for a IBN
only node. You can't speak the 'bark' protocol on a binkp connection. Bark is modem connections only.
The XR flag was removed for this node. So "problem" solved. ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
Who's Online
Recent Visitors
Sirdugas
Wednesday, September 24, 2025 20:06:55
from
Nashville Tn
via
Telnet
Sirdugas
Wednesday, September 24, 2025 15:20:27
from
Nashville Tn
via
Telnet
Spyder
Friday, September 19, 2025 16:23:22
from
Sacramento, Ca
via
Telnet
Tom Trooper
Friday, September 12, 2025 16:13:29
from
Nyc
via
Telnet