Wilfred van Velzen wrote to Nighthawk <=-
This was from last year, and R88 hasn't been in the Z2 nodelist since early this year, so I had to find a nodelist from last year, to get the connect info:
# telnet mastodontbbs.hopto.org 2323
Trying 190.211.29.29...
telnet: connect to address 190.211.29.29: Connection timed out
If this is still the right hostname and portnumber: It's not working.
Wilfred van Velzen wrote to Nighthawk <=-
If this is still the right hostname and portnumber: It's not working.
Now I'm getting a login prompt from a mystic bbs, but no binkp connect
on that port...
On the binkp port there's no connect.
@MSGID: 4:801/188 ede0230a
@TID: Mystic BBS 1.12 A42
@TZUTC:
Wilfred van Velzen wrote to Nighthawk <=-
This was from last year, and R88 hasn't been in the Z2 nodelist
since early this year, so I had to find a nodelist from last year,
to get the connect info:
# telnet mastodontbbs.hopto.org 2323 Trying 190.211.29.29... telnet:
connect to address 190.211.29.29: Connection timed out
If this is still the right hostname and portnumber: It's not working.
Well, at least something good should have come up from rescanning
FN_SYSOP: I can finally access several messages that needed an
answer.
We've had an issue back in 2019 that R88 (Chile) was stripped out
of the nodelist by accident. This has been fixed now.
The only problem is that Patricio hasn't been very active lately.
We will check on him and update if necessary.
If this is still the right hostname and portnumber: It's not
working.
Now I'm getting a login prompt from a mystic bbs, but no binkp
connect on that port...
On the binkp port there's no connect.
I spoke with Patricio, he was moving his system from Mystic
to Synchronet. Please test again, all is good now.
Sysop: | Gate Keeper |
---|---|
Location: | Shelby, NC |
Users: | 790 |
Nodes: | 20 (0 / 20) |
Uptime: | 14:13:31 |
Calls: | 12,110 |
Calls today: | 6 |
Files: | 5,294 |
D/L today: |
13 files (3,658K bytes) |
Messages: | 564,649 |