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. :-(
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:
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:
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. ;-)
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.
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. :)
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"
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.
Only issue remaining in net 103 is with the host:
1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.
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
Well, I'll turn IVM off, like it has been for many years.
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.
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.
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.
Well, I'll turn IVM off, like it has been for many years.
Confirmed, it has been removed from your nodelist entries. ;-)
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.
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.
Host entry 1:320/0 and node 1:320/119, got the IVM flag removed. ;-)
Wilfred van Velzen wrote to Kurt Weiske <=-
Still not fixed:
Calling '1:103/0'. Call time: '0000-2400' UTC.
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.
New node in net 154: ,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM, INA:thenoiseforest.invisik.net,IBN
Calling 1:154/120 (74.95.142.91:24554) error
(Connection timed out)
Down node 2:463/407 was removed. That could have been an oportunity
to update another node in net 463:
2:463/877 bbs.ncc.org.ua:24554 2a01:d5:0:21b:f1d0:2:463:877
Error: Connection timed out
2:463/877 bbs.ncc.org.ua:24554 62.205.153.104
Error: Connection timed out
Maybe it's a temporary problem. The last time I checked this node in
May this year it was ok.
The prolog was updated with the seasonal wishes (and remarks and requests ;-))...
The prolog was updated with the seasonal wishes (and remarks and
requests ;-))...
New one ;-)
;S Ollands: Hartstikke Zalige Kerst en Nieuwjaar
Node 1:229/705 is no longer Pvt, and got ,CM,INA:halcyonbbs.scisweb.org,IBN
added. Timeout on IPv6, connect on IPv4 with: BinkIT/2.41,JSBinkP/4,sbbs3.20d/Linux
Attempted new RIN entry in R19: ;E,43,Fireside_BBS,Little_Flock_AR,Vincent_Jacobs,-Unpulished-,300,XA ,INA:firesidebbs/com,IBN
;E -- Invalid phone number -- '-Unpulished-'
And the INA is also wrong. But there is a connect on the corrected
INA, with: BinkIT/2.41,JSBinkP/4,sbbs3.20d/Win32
Hi All,
On 2025-12-12 13:09:20, I wrote to you:
New node in net 154:
,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,
INA:thenoiseforest.invisik.net,IBN WvV> Calling 1:154/120(74.95.142.91:24554) error WvV> (Connection timed out)
Not fixed yet.
New node in net 154:,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,
INA:thenoiseforest.invisik.net,IBN WvV> Calling 1:154/120(74.95.142.91:24554) error WvV> (Connection timed out)
Not fixed yet.
We're working on it. I can connect to him, but opening that port to
the world is one of the things he needs to finish yet.
Holidays are getting in the way :)
New node in net 154:,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,
INA:thenoiseforest.invisik.net,IBN WvV> Calling 1:154/120(74.95.142.91:24554) error WvV> (Connection timed out)
Not fixed yet.
We're working on it. I can connect to him, but opening that port to
the world is one of the things he needs to finish yet.
1 Minute job!?
Holidays are getting in the way :)
You could mark the node 'Hold' for the time being...
New node in net 221: Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...
New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...
Network 221 segment updated, but as you know in R20 you have to wait a week...
New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...
Network 221 segment updated, but as you know in R20 you have to
wait a week...
I don't, but there are no daily updates in R20?
...New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...
Network 221 segment updated, but as you know in R20 you have to
wait a week...
I don't, but there are no daily updates in R20?
Yep. As you can see, the updates get into the Z2DAILY's only once in a week:
=== Cut ===
grep "Host,221,Finland" Z2DAILY.3* Z1DAILY.337:Host,221,Finland_(331),Ylojarvi,Tommi_Koivula,-U
Z1DAILY.365:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U
=== Cut ===
| Sysop: | Fercho |
|---|---|
| Lugar: | La Plata, Buenos Aires |
| Usuarios: | 26 |
| Nodos: | 10 (0 / 10) |
| Uptime: | 128:02:24 |
| Llamadas: | 131 |
| Archivoss: | 15,915 |
| Mensajes: | 39,400 |
Novedades:
Servidor de Quake 3 Arena Online! - Conectate a ferchobbs.ddns.net, puerto 27960 y vence con tu equipo!