We can connect, but he still uses the default binkd configuration
file:
We can connect, but he still uses the default binkd configuration
file:
Hi Michiel,
On 2022-06-06 18:20:12, you wrote to me:
MvdV> On Monday June 06 2022 18:03, you wrote to me:
WV>> We can connect, but he still uses the default binkd configuration
WV>> file:
MvdV> That is not what I see:
MvdV> 17:24 [992] creating a poll for 2:240/49@fidonet (`d' flavour)
MvdV> 17:24 [992] clientmgr started
MvdV> + 17:24 [3952] call to 2:240/49@fidonet
MvdV> 17:24 [3952] trying f49.n240.z2.binkp.net
MvdV> [2001:7d0:4f41:1b00:5da5:cde2:78d6:9068]... 17:24 [3952] connected + 17:24
MvdV> [3952] outgoing session with f49.n240.z2.binkp.net:24554
MvdV> [2001:7d0:4f41:1b00:5da5:cde2:78d6:9068]
MvdV> - 17:24 [3952] OPT CRAM-MD5-9c32d534f7fd2740d7d93d481976bc47
MvdV> + 17:24 [3952] Remote requests MD mode
MvdV> - 17:24 [3952] SYS RedFrog BBS
MvdV> - 17:24 [3952] LOC Tallinn/Estonia
MvdV> - 17:24 [3952] ZYZ Eku
MvdV> - 17:24 [3952] TIME Mon, 06 Jun 2022 18:24:04 +0300
MvdV> - 17:24 [3952] VER Mystic/1.12A47 binkp/1.0
MvdV> - 17:24 [3952] BUILD 2021/12/24 21:21:08 Raspberry Pi/32
MvdV> + 17:24 [3952] addr: 21:4/182@fsxnet (n/a or busy)
MvdV> + 17:24 [3952] addr: 2:240/49@fidonet
MvdV> - 17:24 [3952] QSIZE 0 files 0 bytes
MvdV> + 17:24 [3952] done (to 2:240/49@fidonet, OK, S/R: 0/0 (0/0 bytes))
MvdV> 17:24 [3952] session closed, quitting...
MvdV> 17:24 [992] the queue is empty, quitting...
17:24 Is from before I did the test, and I wrote the reply (18:03). I just re-did the test, and it's still wrong...
We have a new one:
109 2:240/49 Ergo Paalman T-6in4 he.net
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 991 |
Nodes: | 10 (1 / 9) |
Uptime: | 132:01:57 |
Calls: | 12,960 |
Calls today: | 2 |
Files: | 186,574 |
Messages: | 3,266,098 |