• issue conecting to magicka

    From Blue White@21:4/134 to apam on Sat Jan 2 15:29:45 2021
    apam,
    Happy New Year!

    I am having what may be a self-inflicted issue connecting to my Magicka
    system (see below).

    If I connect to the local IPA using SSH or telnet, it works fine. This is using magiterm.

    If I connect to the possumso.fsxnet.nz address using HTTP, it works fine.

    If I try to connect to the possumso.fsxnet.nz address using SSH or telnet,
    I am NOT able to connect. This is using magiterm (both) and syncterm
    (telnet).

    Now, this morning, when I fired up magiterm and tried to connect via SSH to
    the fsxnet address, it asked for my PASS:. As I had recently upgraded
    linux on both the raspberry pi (host) and the system I was trying to
    connect from, I was not surprised.

    I had some issues getting the password right (right password, wrong case!).
    After I got that stright is when I started having the unable to connect at
    all issue.

    Does magicka remember IPAs it has issues with and does it ban them? If so,
    how do I get my "outside" IPA unbanned so that I can connect to the bbs?

    The issue doesn't appear to be with my login ID since it lets me in if I use the local IPA address. If it does not ban IPAs, what else would you recommend that I look at to restore my ability to SSH to the possumso.fsxnet.nz
    address?

    THANKS!
    Mike

    ... Got my tie caught in the fax... Suddenly I was in L.A.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/182 to Blue White on Sun Jan 3 12:27:02 2021
    I had some issues getting the password right (right password, wrong
    case!).
    After I got that stright is when I started having the unable to
    connect at
    all issue.

    You might have tried logging in too many times in to short a while. There should be a blacklist.ip4 file which may contain your ip address. If it
    does, delete it, and so it doesn't happen again, create a whitelist.ip4
    and pop the ip address in there.

    Andrew


    --- Talisman v0.8-dev (Linux/armv7l)
    * Origin: HappyLand v2.0 - telnet://happyland.zapto.org:11892/ (21:1/182)
  • From Blue White@21:4/134 to apam on Sun Jan 3 09:16:17 2021
    apam wrote to Blue White <=-

    I had some issues getting the password right (right password, wrong
    case!).
    After I got that stright is when I started having the unable to
    connect at
    all issue.

    You might have tried logging in too many times in to short a while.
    There should be a blacklist.ip4 file which may contain your ip address.
    If it does, delete it, and so it doesn't happen again, create a whitelist.ip4 and pop the ip address in there.

    Thanks, that worked! :)




    ... 2 + 2 = 5 for extremely large values of 2.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)