• Mystic binkp poll logging

    From Dumas Walker@21:1/175 to ALL on Tuesday, March 31, 2020 18:13:00
    Good evening,
    I have a new FTN node that is trying to connect with my system using
    mystic. When he attempts to poll here, he is getting the following log
    output on his end. On my end, I do not see any suggestion that there was
    ever a binkd connection to be lost.

    Mar 30 20:26:58 Queued 1 files (588 bytes) to 1:2320/105

    Mar 30 20:26:58 Polling BINKP node 1:2320/105 (Mike Powell) by IPV4

    Mar 30 20:26:58 Connecting to capitolcityonline.net:24554 port 24554

    Mar 30 20:26:58 Connected IPV4 to 67.131.57.133

    Mar 30 20:26:58 Connection lost

    Mar 30 20:26:58 Authorization failed

    Mar 30 20:26:58 Polled 0 nodes


    Is there an option in mystic to show more of the binkp output to the log so
    we can better trouble shoot this? I suspect he is never reaching the binkd
    on my end but cannot really tell from this output level.

    Thanks!


    * SLMR 2.1a * If an experiment works, something has gone wrong
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106.1 to Dumas Walker on Tuesday, March 31, 2020 16:11:14
    Hello Dumas,

    Is there an option in mystic to show more of the binkp output to the
    log so we can better trouble shoot this? I suspect he is never
    reaching the binkd on my end but cannot really tell from this output level.

    I don't think there is currently. Sometimes when g00r00 is implementing new featues he will increase the log level and logs are very verbose and grow quickly.

    I suspect this link may be having the same trouble connecting to your node that
    I am with the Connection closed by foreign host message.

    Do you have a BBS and a mailer on the same IP? What happens if that link tries to connect to your BBS. Maybe the output will also give us a clue.

    On linux I can do "telnet capitolcityonline.net 24554" and that is how I see the Connection closed message. I get the same on port 23 although I don't know if you have a BBS on port 23.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Dumas Walker@21:1/175 to AL on Tuesday, March 31, 2020 20:22:00
    On linux I can do "telnet capitolcityonline.net 24554" and that is how I see >the Connection closed message. I get the same on port 23 although I don't know >if you have a BBS on port 23.

    I have asked him to try connecting to the bbs to see what happens. You
    should be getting an answer on port 23. What is your IPA, so that I can
    check the bad ip lists and make sure it is not there.

    While you are at it, could you also try port 7636, which is a different
    machine running magicka, or port 27, also a different machine?

    I have checked my router and all filtering is turned off, which has me a
    little worried about why you cannot get through.


    * SLMR 2.1a * Small world, but I wouldn't want to paint it.
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106.1 to Dumas Walker on Tuesday, March 31, 2020 18:10:32
    Hello Dumas,

    I have asked him to try connecting to the bbs to see what happens.
    You should be getting an answer on port 23. What is your IPA, so that
    I can check the bad ip lists and make sure it is not there.

    When I try to connect with nodespy on port 23 an info window pops up that says "Connection terminated".

    While you are at it, could you also try port 7636, which is a
    different machine running magicka, or port 27, also a different
    machine?

    Yes, those two work fine. On port 7636 I got your MagickaBBS login and I was able to connect on port 27 also.

    I have checked my router and all filtering is turned off, which has me
    a little worried about why you cannot get through.

    Something seems to be blocking me (and probably your link) on your port 23 and 24554 although I don't know what.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Al@21:4/106.1 to Dumas Walker on Tuesday, March 31, 2020 18:22:46
    Hello Dumas,

    I have asked him to try connecting to the bbs to see what happens.
    You should be getting an answer on port 23. What is your IPA, so that
    I can check the bad ip lists and make sure it is not there.

    My IP is 104.246.155.40.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to Dumas Walker on Wednesday, April 01, 2020 20:27:17

    On 31 Mar 2020 at 06:13p, Dumas Walker pondered and said...

    Good evening,
    I have a new FTN node that is trying to connect with my system using mystic. When he attempts to poll here, he is getting the following log output on his end. On my end, I do not see any suggestion that there was ever a binkd connection to be lost.

    Is there an option in mystic to show more of the binkp output to the log so we can better trouble shoot this? I suspect he is never reaching the binkd on my end but cannot really tell from this output level.

    g00r00 recently added some logging options to later pre-alpha builds of 1.12 A46 such that you can set 'verbose' logging output for mis and mis poll

    That would be worth exploring if he is running a bleeding edge build.
    Otherwise it's probably a no until A46 is released.

    --- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Dumas Walker@21:1/175 to AL on Wednesday, April 01, 2020 17:05:00
    Yes, those two work fine. On port 7636 I got your MagickaBBS login and I was >able to connect on port 27 also.

    So could my link, so that rules out the router, isp, and modem.

    Something seems to be blocking me (and probably your link) on your port 23 and >24554 although I don't know what.

    I wonder what. I have sent my *.can files to DM via email to see if he
    maybe sees something I do not. I do have several blocks in the
    ip-silent.can file, but neither of you would appear to be covered by any of them.

    From what I can tell, the machine has no active firewall running. ubuntu
    did install one, but running it with the 'status' option shows that it is
    not running.


    * SLMR 2.1a * Bless our young they will inherit our national dept.
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106 to Dumas Walker on Wednesday, April 01, 2020 14:31:46
    Something seems to be blocking me (and probably your link) on your port 23 an >> 24554 although I don't know what.

    I wonder what. I have sent my *.can files to DM via email to see if he
    maybe sees something I do not. I do have several blocks in the
    ip-silent.can file, but neither of you would appear to be covered by any of them.

    That's really curious. I think if it was Synchronet blocking access it would log the activity an IP affected.

    If you can load up a quick & dirty Mystic on some port on that machine I could try that and see if I can connect but I think there is something else happening
    here.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Al@21:4/106 to Dumas Walker on Wednesday, April 01, 2020 14:35:28
    From what I can tell, the machine has no active firewall running. ubuntu
    did install one, but running it with the 'status' option shows that it is
    not running.

    I do actually connect to your machine on port 23 and 24554 but the connection is dropped for some reason.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Dumas Walker@21:1/175 to Al on Wednesday, April 01, 2020 18:17:24
    Re: Mystic binkp poll logging
    By: Al to Dumas Walker on Wed Apr 01 2020 14:31:46

    That's really curious. I think if it was Synchronet blocking access it would log the activity an IP affected.

    I am not sure it would if it was on the ip-silent.can file. It might.

    I have binkd installed on this system. I did think about firing it up on a different port to see what happens.
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106 to Dumas Walker on Wednesday, April 01, 2020 17:19:16
    I am not sure it would if it was on the ip-silent.can file. It might.

    I have binkd installed on this system. I did think about firing it up on a different port to see what happens.

    If you do put binkd online let me know the port and I'll give it a try.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Beery@21:4/164 to Al on Thursday, April 02, 2020 10:15:57
    Yep, I am the link that is being blocked. Sounds like there is more than one of us in the same boat.

    When I try to telnet in from my home system to either port 23 or to port
    24554, it is an immediate disconnect. At work with a different IP, no issue.

    Beery


    On 31 Mar 2020, Al said the following...

    Hello Dumas,

    I have asked him to try connecting to the bbs to see what happens. You should be getting an answer on port 23. What is your IPA, so tha I can check the bad ip lists and make sure it is not there.

    When I try to connect with nodespy on port 23 an info window pops up
    that says "Connection terminated".

    While you are at it, could you also try port 7636, which is a different machine running magicka, or port 27, also a different machine?

    Yes, those two work fine. On port 7636 I got your MagickaBBS login and I was able to connect on port 27 also.

    I have checked my router and all filtering is turned off, which has m a little worried about why you cannot get through.

    Something seems to be blocking me (and probably your link) on your port
    23 and 24554 although I don't know what.

    Ttyl :-),
    Al


    Beery Miller
    9640News.ddns.net:9640

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: FuSiON BBS (21:4/164)
  • From Beery@21:4/164 to Avon on Thursday, April 02, 2020 10:20:40
    g00r00 recently added some logging options to later pre-alpha builds of 1.12 A46 such that you can set 'verbose' logging output for mis and mis poll

    I just updated the setting to watch the log file. I'm doubting this will give any detail since the system isn't even logging my connection. I'll try
    though.

    Beery

    Beery Miller
    9640News.ddns.net:9640

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: FuSiON BBS (21:4/164)
  • From Beery@21:4/164 to Dumas Walker on Thursday, April 02, 2020 10:22:47
    I sent you a note. Any chance you have any blocked countries? Mystic has
    the setup, not sure about Synchronet.

    Beery


    Yes, those two work fine. On port 7636 I got your MagickaBBS login and I >able to connect on port 27 also.

    So could my link, so that rules out the router, isp, and modem.

    Something seems to be blocking me (and probably your link) on your port 2 >24554 although I don't know what.

    I wonder what. I have sent my *.can files to DM via email to see if he maybe sees something I do not. I do have several blocks in the ip-silent.can file, but neither of you would appear to be covered by any of them.

    From what I can tell, the machine has no active firewall running. ubuntu did install one, but running it with the 'status' option shows that it is not running.


    * SLMR 2.1a * Bless our young they will inherit our national dept.
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)

    Beery Miller
    9640News.ddns.net:9640

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: FuSiON BBS (21:4/164)
  • From Al@21:4/106 to Beery on Thursday, April 02, 2020 09:08:54
    Hello Beery,

    Yep, I am the link that is being blocked. Sounds like there is more
    than one of us in the same boat.

    Yep, I just tried to connect there since someone was having trouble and low and
    behold, I couldn't connect either.

    It's odd since others have no problem.

    When I try to telnet in from my home system to either port 23 or to
    port 24554, it is an immediate disconnect. At work with a different
    IP, no issue.

    There must be an answer there somewhere but just what I'm still not sure.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Dumas Walker@21:1/175 to AL on Thursday, April 02, 2020 12:14:00
    @MSGID: <5E8530C7.6855.fsx_bbs@capitolcityonline.net>
    @REPLY: <5E8512F4.6849.fsx_bbs@capitolcityonline.net>
    I am not sure it would if it was on the ip-silent.can file. It might.

    I have binkd installed on this system. I did think about firing it up on a different port to see what happens.

    If you do put binkd online let me know the port and I'll give it a try.

    24553. Thanks!!!!


    * SLMR 2.1a * How am I'm overdrawn? I still have checks left!
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 09:42:26
    Hello Dumas,

    If you do put binkd online let me know the port and I'll give it a
    try.

    24553. Thanks!!!!

    Well yes, I see your OPT CRAM-MD5 info and it waits for input.

    Maybe Synchronet is blocking the connection for some reason.

    I'm going to do a mailer poll in a minute here..

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 09:47:46
    Hello Dumas,

    24553. Thanks!!!!

    Yep, a mailer poll on port 24554 fails and a poll on 24553 succeeds.

    You might have to talk to DM about that.. :)

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 11:48:22
    Hello Dumas,

    24553. Thanks!!!!

    DM has suggested switching the ports on your BinkIT and Binkd mailers to see what changes.

    If you can do that I'll poll and see what happens.

    Let me know what ports to test.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Dumas Walker@21:1/175 to AL on Thursday, April 02, 2020 14:56:00
    Yep, a mailer poll on port 24554 fails and a poll on 24553 succeeds.

    You might have to talk to DM about that.. :)

    I am. One thing he suggested was for me to get the output of the following command from you both and see if it looks different from his (he is able to
    get through on 23 and 24554):

    nmap -p- 67.131.57.133


    * SLMR 2.1a * Waiter: Unemployed actor
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 12:19:40
    Hello Dumas,

    nmap -p- 67.131.57.133

    OK, I have that command running now and will post once I get something.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 13:24:50
    Hello Dumas,

    nmap -p- 67.131.57.133

    Here is what I got, I hope it helps.

    === Cut ===

    Starting Nmap 7.12 ( https://nmap.org ) at 2020-04-02 12:20 PDT
    Stats: 0:39:53 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan Connect Scan Timing: About 76.51% done; ETC: 13:13 (0:12:15 remaining)
    Nmap scan report for host-067-131-057-133.dhcp.fewpb.net (67.131.57.133)
    Host is up (0.11s latency).
    Not shown: 65515 filtered ports
    PORT STATE SERVICE
    21/tcp open ftp
    23/tcp open telnet
    27/tcp open nsw-fe
    80/tcp open http
    119/tcp open nntp
    443/tcp closed https
    513/tcp open login
    587/tcp open submission
    1025/tcp closed NFS-or-IIS
    1123/tcp open murray
    2022/tcp open down
    2122/tcp open unknown
    7636/tcp open unknown
    8080/tcp open http-proxy
    11235/tcp open unknown
    17175/tcp closed unknown
    24553/tcp open unknown
    24554/tcp open binkp
    24555/tcp open unknown
    24557/tcp open unknown

    Nmap done: 1 IP address (1 host up) scanned in 3197.88 seconds

    === Cut ===

    I sent this to DM in SYNCHRONET but here it is just in case it gets lost on the
    way.. :)

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Dumas Walker@21:1/175 to Al on Thursday, April 02, 2020 16:41:43
    DM has suggested switching the ports on your BinkIT and Binkd mailers to
    see
    what changes.

    If you can do that I'll poll and see what happens.

    Let me know what ports to test.


    Actually, I have temporarily removed the filter files. You might try port 23 again and see what happens. On the basis of your nmap output it sure looks like it is open to you now!

    If that does not work, try port 2022. I am using a non-standard SSH port so maybe it won't be blocked if the block is outside my network.

    I would prefer not to try switching the binkit ports as it might fool my connections. I will try it if all else fails, though, but I think 2022 might be a similar test as it is not standard.

    Thanks!
    Mike
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 14:01:36
    Hello Dumas,

    Actually, I have temporarily removed the filter files. You might try
    port 23 again and see what happens. On the basis of your nmap output
    it sure looks like it is open to you now!

    If that does not work, try port 2022. I am using a non-standard SSH
    port so maybe it won't be blocked if the block is outside my network.

    It looks good now. I can connect with my mailer on 24554 and all the other ports as well with telnet.

    I would prefer not to try switching the binkit ports as it might fool
    my connections. I will try it if all else fails, though, but I think
    2022 might be a similar test as it is not standard.

    Yep, don't want to mess with that if we can help it at all.. :)

    Looks like clear skies and gentle breezes now.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Dumas Walker@21:1/175 to AL on Thursday, April 02, 2020 18:14:00
    If that does not work, try port 2022. I am using a non-standard SSH port so maybe it won't be blocked if the block is outside my network.

    It looks good now. I can connect with my mailer on 24554 and all the other ports as well with telnet.

    Looks like clear skies and gentle breezes now.

    Yes, thank you so much for your assistance! I wonder, though, what was in
    my ip-silent.can file that had you blocked. I went over and over it and
    none of the IP ranges started with 104, and none of the ones that were
    close should have included yours. DM also looked at it and did not think
    there was anything wrong.

    I personally think I probably had one of the wildcards set wrong! :O


    * SLMR 2.1a * But my little voice TOLD me to do it!
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
  • From Al@21:4/106 to Dumas Walker on Thursday, April 02, 2020 23:42:26
    Hello Dumas,

    Looks like clear skies and gentle breezes now.

    Yes, thank you so much for your assistance!

    No worries.. :)

    I wonder, though, what was in my ip-silent.can file that had you
    blocked. I went over and over it and none of the IP ranges started
    with 104, and none of the ones that were close should have included
    yours. DM also looked at it and did not think there was anything
    wrong.

    I have avoided any kind of permanent ban of IP addresses because the bad guys just come up with another and someone else may get that IP and then they have a
    problem getting in.

    That does leave all the junk there for your server to deal with but Synchronet seems to do a good job of handling that.

    I personally think I probably had one of the wildcards set wrong! :O

    It would be good to know the W5 of all that so it doesn't happen agian, or if it does we know what the solution is.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Blue White@21:4/134 to Al on Friday, April 03, 2020 17:24:07
    There must be an answer there somewhere but just what I'm still not
    sure.

    It turned out to be that I had a '46.~' entry in the ip-silent.can file. I misunderstood how that worked. Because you both have a node '146.' in your
    IP addresses, you were both blocked as the way I had that entered it was matching the '46.' in your whole address.

    It was really a coincidence that you were one of the people who decided to
    help out. It would have been a needle in a haystack had it not been for
    that one similar node in your IP addresses.

    At any rate, at DM's suggestion, I changed all of the '~' entries to '*'.
    Now all should be good (at least for you two!).




    ... He does the work of 3 Men...Moe, Larry & Curly
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)