I'm sure I have something setup wrong, but I don't know what to look for with all the changes. Should be running mis2 for telnet and binkp, but binkp is
one way right now (seems to send and not receive). Is that possible?
Here's the log:
ep 04 22:40:24 FIDOPOLL Version 1.12 A35
Sep 04 22:40:24 Scanning 21:1/145.2
Sep 04 22:40:24 Queued 0 files (0 bytes) to 21:1/145.2
Sep 04 22:40:24 Scanning 80:774/0
Sep 04 22:40:24 Queued 0 files (0 bytes) to 80:774/0
Sep 04 22:40:24 Scanning 21:1/100
Sep 04 22:40:24 Queued 1 files (335 bytes) to 21:1/100
Sep 04 22:40:24 Polling BINKP node 21:1/100
Sep 04 22:40:24 Connecting to ipv4.agency.bbs.geek.nz:24556
Sep 04 22:40:25 Connected
Sep 04 22:40:25 Authorization State: 1 HH:0 NH:1
Sep 04 22:40:25 Sent: NUL SYS Mystic Pi BBS
Sep 04 22:40:25 Sent: NUL ZYZ bcw142
Sep 04 22:40:25 Sent: NUL VER Mystic/1.12A35 binkp/1.0
Sep 04 22:40:25 Sent: ADR 21:1/145@fsxnet
Sep 04 22:40:25 Authorization State: 2 HH:0 NH:1
Sep 04 22:40:25 Recv: NUL OPT CRAM-MD5-1b90c59ee227f08bbb4b7d8f63b668a9
Sep 04 22:40:25 Authorization State: 2 HH:1 NH:0
Sep 04 22:40:25 OPT CRAM-MD5-1b90c59ee227f08bbb4b7d8f63b668a9
Sep 04 22:40:25 Received challenge (1b90c59ee227f08bbb4b7d8f63b668a9)
Sep 04 22:40:25 Authorization State: 2 HH:0 NH:1
Sep 04 22:40:25 Recv: NUL SYS fsxHUB [fsxNet WHQ]
Sep 04 22:40:25 Authorization State: 2 HH:1 NH:0
Sep 04 22:40:25 SYS fsxHUB [fsxNet WHQ]
Sep 04 22:40:25 Recv: NUL ZYZ Paul Hayton
Sep 04 22:40:25 ZYZ Paul Hayton
Sep 04 22:40:25 Recv: NUL VER Mystic/1.12A35 binkp/1.0
Sep 04 22:40:25 VER Mystic/1.12A35 binkp/1.0
Sep 04 22:40:25 Recv: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Sep 04 22:40:25 Sent: PWD CRAM-MD5-6e85be4dcf5ca76d37d720ca2d06d32d
Sep 04 22:40:26 Authorization State: 5 HH:0 NH:1
Sep 04 22:40:26 Recv: OK secure
Sep 04 22:40:26 Authorization State: 5 HH:1 NH:0
Sep 04 22:40:26 State RxS:1 TxS:1 HH:0 NH:1
Sep 04 22:40:26 Sending 02dee6a3.pkt (335 bytes)
Sep 04 22:40:26 Sent: FILE 02dee6a3.pkt 335 1504564824 0
Sep 04 22:40:26 State RxS:1 TxS:2 HH:0 NH:1
Sep 04 22:40:26 Sent: Data 335
Sep 04 22:40:26 State RxS:1 TxS:3 HH:0 NH:1
Sep 04 22:40:26 Recv: EOB
Sep 04 22:40:26 State RxS:1 TxS:3 HH:1 NH:0
Sep 04 22:40:26 State RxS:3 TxS:3 HH:0 NH:1
Sep 04 22:40:27 Recv: GOT 02dee6a3.pkt 335 1504564824
Sep 04 22:40:27 State RxS:3 TxS:3 HH:1 NH:0
Sep 04 22:40:27 State RxS:3 TxS:1 HH:0 NH:1
Sep 04 22:40:27 Sent: EOB
Sep 04 22:40:27 Session complete (1 sent, 0 rcvd, 0 skip)
Sep 04 22:40:27 Scanning 80:603/0.2
Sep 04 22:40:27 Queued 0 files (0 bytes) to 80:603/0.2
Sep 04 22:40:27 Scanning 21:1/145.1
Sep 04 22:40:27 Queued 0 files (0 bytes) to 21:1/145.1
Sep 04 22:40:27 Scanning 21:1/145.3
Sep 04 22:40:27 Queued 0 files (0 bytes) to 21:1/145.3
Sep 04 22:40:27 Scanning 80:603/0.3
Sep 04 22:40:27 Queued 0 files (0 bytes) to 80:603/0.3
Sep 04 22:40:27 Polled 1 nodes
Sep 04 22:51:02 FIDOPOLL Version 1.12 A35
Sep 04 22:51:02 Scanning 21:1/145
Sep 04 22:51:02 Queued 0 files (0 bytes) to 21:1/145
Sep 04 22:51:02 Polling BINKP node 21:1/145
Sep 04 22:51:02 Connecting to 24556
Sep 04 22:51:02 Unable to connect
Sep 04 22:51:17 FIDOPOLL Version 1.12 A35
Sep 04 22:55:44 FIDOPOLL Version 1.12 A35
Sep 04 22:55:44 Scanning 21:1/145
Sep 04 22:55:44 Queued 0 files (0 bytes) to 21:1/145
Sep 04 22:55:44 Polling BINKP node 21:1/145
Sep 04 22:55:44 Connecting to 24556
Sep 04 22:55:44 Unable to connect

So I seem to connect to send but not to receive. Any guesses? This is a whole new setup on a Pi3 with fresh A35 install so all kinds of odd things could
have happened. I can get here from it with nodespy so telnet is fine.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

So I seem to connect to send but not to receive. Any guesses? This is a whole new setup on a Pi3 with fresh A35 install so all kinds of odd
things could have happened. I can get here from it with nodespy so
telnet is fine.

Can you point out what you think is wrong in those logs, exactly?

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

is it related to port forwarding on your router? has your new pi been
assigned a new local ip address which is not what you have assigned to have
the binkp port number forwarded?


Dale.

--- Mystic BBS v1.12 A34 (Raspberry Pi/32)
* Origin: New Mystic BBS (21:2/107)

What I thought was wrong was:
Sep 04 22:51:02 FIDOPOLL Version 1.12 A35
Sep 04 22:51:02 Scanning 21:1/145
Sep 04 22:51:02 Queued 0 files (0 bytes) to 21:1/145
Sep 04 22:51:02 Polling BINKP node 21:1/145
Sep 04 22:51:02 Connecting to 24556
Sep 04 22:51:02 Unable to connect
Sep 04 22:51:17 FIDOPOLL Version 1.12 A35
Sep 04 22:55:44 FIDOPOLL Version 1.12 A35
Sep 04 22:55:44 Scanning 21:1/145
Sep 04 22:55:44 Queued 0 files (0 bytes) to 21:1/145
Sep 04 22:55:44 Polling BINKP node 21:1/145
Sep 04 22:55:44 Connecting to 24556
Sep 04 22:55:44 Unable to connect

What happened is the message when out but never came back. Send and no
receive. There was an *.bsy file caught in echomail/in and several in echomail/out/fidonet that I had to clear by hand. That got it doing something again - it remains to be seen if echomail really starts working. I did an import & export as the semaphore didn't clear so events or semaphores aren't quite right on my system.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

Sep 04 22:55:44 Polling BINKP node 21:1/145
Sep 04 22:55:44 Connecting to 24556
Sep 04 22:55:44 Unable to connect

This is not a valid address 24556 is the port number. What do you have for
the hostname in your Echomail node "session" configuration for 21:1/145?

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/06/17, g00r00 said the following...

Sep 04 22:55:44 Polling BINKP node 21:1/145
Sep 04 22:55:44 Connecting to 24556

This is not a valid address 24556 is the port number. What do you have for the hostname in your Echomail node "session" configuration for 21:1/145?

Under Session:

FSXNet_Hub 21:1/100
Host ipv4.agency.bbs.geek.nz:24556
Timeout 30
BlockSide 16384
CRAM-MD5 Yes
Hide AKAs Yes

Not sure why the log says 24556 without 21:1/100. Right now I've switched
back to mis as I couldn't get mis2 really working right at all, so I fell
back to what had worked and will try mis2 again after mis has worked for a while. The same on the binkp even though I'm not sure it has any problems.
mis seems to be duplicating, by that I mean multiple copies appear and it
seems they fight with each other making login drop almost the instant you log on. I suspect the hacking is causing the multiple copies. Still it doesn't happen for hours so I can fight with that and still operate. Up to today the system hasn't really operated for EchoMail.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

Sep 04 22:55:44 Polling BINKP node 21:1/145

FSXNet_Hub 21:1/100
Not sure why the log says 24556 without 21:1/100. Right now I've switched

No, the system in the logs was 21:1/145 not 21:1/100 - as shown above. You're looking at the wrong address configuration.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/09/17, g00r00 said the following...

Sep 04 22:55:44 Polling BINKP node 21:1/145

FSXNet_Hub 21:1/100
Not sure why the log says 24556 without 21:1/100. Right now I've swit

No, the system in the logs was 21:1/145 not 21:1/100 - as shown above. You're looking at the wrong address configuration.

Them I'm likely looking at the wrong system, my main bbs would send to 21:1/100, the points send to 21:1/145 which sends to 21:1/100. It must have been a point and it was likely before the release A35 so it doesn't matter. I don't think it does that with the A35 release.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)