I'm guessing you are still polling 24556 - which is a different host
(IPv4 nat going on). If you poll 24553, it should get you bbs.leenooks.net:
IPv4:24553 is alterant (my bbs 2/116) - if you polled it, it would be unsecure (since your not defined on it), and so you shouldnt get any packets.
IPv4:24556 is Hub 3 - I see you poll it and get a bunch of stuff just
fine - but yes the cert wont match the DNS name (alterant.leenooks.net
- which resolves to the IPv4 address).
verify error:num=20:unable to get local issuer certificate
verify error:num=21:unable to verify the first certificate
Exactly what that means I don't know.
That is normal, since the cert is self signed - this is just telling
you that you cannot validate the certificate via a 3rd party (self signed).
Well, we are tansfering both ways with TLS I think? So that is good.
I have taken bbs.linooks.net out of my hosts file since it didn't provide any joy and am back to polling alterant.leenooks.net.
I've noticed when I poll you (just testing for the most part) that I pick up a bunch of PKTs. Are you not able to poll and connect to my node?
It still takes a couple minutes to get my prompt back when I poll your node. I don't know why that is and it's not a critical error. Just a PITA. This is logged after I poll your node..
14:01 [8258] session closed, quitting...
14:03 [8258] rc=(8259)=0
14:03 [8257] rc=(8258)=0
14:03 [8257] the queue is empty, quitting...
Yes, I'm trying to get binkit to poll out - it doesnt seem to be doing
it unless I manually touch binkit.now. Havent figured out why yet.
I am also juggling, because Taurus is also serving the same outbound
for EMSI and other binkp systems. I think they can work together (lock files, etc), just need to do some more testing to be sure.
Perhaps somebody knows what's going on between 01:34 and 03:35 - it
seems I'm waiting on you to send me something?
3/4 09:01:34a 1344 BINKPS Sending file: /MAILER/BOX/00150004.06A\5e5ed0a7.pkt (1.5KB)
3/4 09:01:34a 1344 BINKPS Sent
file: /MAILER/BOX/00150004.06A\5e5ed0a7.pkt (1.5KB)
3/4 09:01:34a 1344 BINKPS Sending file: /MAILER/BOX/00150004.06A\5e5ed161.pkt (1.7KB)
3/4 09:01:34a 1344 BINKPS Sent
file: /MAILER/BOX/00150004.06A\5e5ed161.pkt (1.7KB)
3/4 09:01:34a 1344 BINKPS Sending file: /MAILER/BOX/00150004.06A\5e5ed196.pkt (1.4KB)
3/4 09:01:34a 1344 BINKPS Sent
file: /MAILER/BOX/00150004.06A\5e5ed196.pkt (1.4KB)
3/4 09:01:34a 1344 BINKPS Sending file: /MAILER/BOX/00150004.06A\5e5ed295.pkt (2.0KB)
3/4 09:01:34a 1344 BINKPS Sent
file: /MAILER/BOX/00150004.06A\5e5ed295.pkt (2.0KB)
3/4 09:01:34a 1344 BINKPS We got an M_EOB, but there are still 4 files pending M_GOT
3/4 09:03:35a 1344 BINKPS Timed out receiving first byte of
packet header!
Perhaps somebody knows what's going on between 01:34 and 03:35 - it
seems I'm waiting on you to send me something?
3/4 09:01:34a 1344 BINKPS We got an M_EOB, but there are still 4M_EOB: End-of-Batch. M_EOB command must be transmitted after all the files have been sent.
files pending M_GOT
M_GOT: File acknowledgement, that MUST be transmitted upon receiving of the last data frame for current file.
This is a weird error, especially because Al is receiving the files. It only happens over TLS?
Re: binkd ssl
By: Oli to alter ego on Wed Mar 04 2020 08:42 am
3/4 09:01:34a 1344 BINKPS We got an M_EOB, but there are
still 4 files pending M_GOT
M_EOB: End-of-Batch. M_EOB command must be transmitted after
all the files have been sent.
M_GOT: File acknowledgement, that MUST be transmitted upon
receiving of the last data frame for current file.
So who is sending the M_EOB out so sequence? It would seem Mystic,
given I was sending files "and still had 4 left"?
This is a weird error, especially because Al is receiving the
files. It only happens over TLS?
I would say no - I've noticed this before - but on Hub 3 binkit isnt
doing normal binkp (taurus is). I might look at changing that...
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 10:36:22 |
Calls: | 728 |
Calls today: | 1 |
Files: | 7,667 |
Messages: | 295,534 |