1. Forum
  2. fsxNet
  3. BBS Support/Dev

  • Help with ssh mystic

    From Sneaky@21:1/152 to All on Sat Jun 12 08:22:27 2021
    Hi all

    I am using linix (rasberry pi os) and trying to get ssh in mystic server to work, I have sorted thw cryptlib part and edit mystic config server section ssh to yes and in ipv adpter 127.0.0.1 and have run ./mis -server but I get this message

    unable to open ipv4 port error -1 (13)

    127.0.0.1 is my localhost number but for telnet I have to use 127.0.0.0.0.1
    to open port but it's not going to for ssh, have tried ajusting the port number, but still the same unable to open port.

    so can same ne help me fix this please

    Ian Segers

    --- Mystic BBS v1.12 A47 2020/10/31 (Windows/32)
    * Origin: 2nd Choice Core : New Zealand (21:1/152)
  • From DustCouncil@21:1/227 to Sneaky on Fri Jun 11 22:26:43 2021
    Try this:

    sudo setcap CAP_NET_BIND_SERVICE=+ip /mystic/mis

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)
  • From Sneaky@21:1/115 to DustCouncil on Sat Jun 12 16:39:00 2021
    Hi DustCouncil

    Try this:

    sudo setcap CAP_NET_BIND_SERVICE=+ip /mystic/mis

    must be more to this line,tried and got this

    pi@raspberrypi:~ $ sudo setcap GAP_NET_BIND_SERVICE=+ip /mystic/mis
    fatal error: Invalid argument
    usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]


    but it will be me not understanding the command line, butI sureyou will lety me now

    Thank you
    Ian

    --- SBBSecho 3.11-Win32
    * Origin: 1st Choice Core (21:1/115)
  • From Al@21:4/106.2 to Sneaky on Fri Jun 11 21:51:42 2021
    sudo setcap CAP_NET_BIND_SERVICE=+ip /mystic/mis

    must be more to this line,tried and got this

    pi@raspberrypi:~ $ sudo setcap GAP_NET_BIND_SERVICE=+ip /mystic/mis
    fatal error: Invalid argument
    usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]

    Try it like this..

    sudo setcap 'cap_net_bind_service=+ep' mis

    in your mystic directory. That command works for me, anyway.

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)
  • From DustCouncil@21:1/227 to Sneaky on Sat Jun 12 05:14:17 2021
    pi@raspberrypi:~ $ sudo setcap GAP_NET_BIND_SERVICE=+ip /mystic/mis
    fatal error: Invalid argument
    usage: setcap [-q] [-v] (-r|-<caps>) <filename> [ ... (-r|-<capsN>) <filenameN> ]

    Possibly my mistake as I can only sometimes paste into Syncterm, so I was retyping that comment. Use single-quotes. Try:

    sudo setcap 'cap_net_bind_service=+iep' /mystic/mis

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)
  • From Sneaky@21:1/115 to DustCouncil on Sat Jun 12 19:53:00 2021
    Hi DustCouncil wrote to Sneaky <=-

    Possibly my mistake as I can only sometimes paste into Syncterm, so I
    was retyping that comment. Use single-quotes. Try:

    sudo setcap 'cap_net_bind_service=+iep' /mystic/mis

    no errors this time but still the same, wont open port

    but

    sudo setcap 'cap_net_bind_service=+iep' /mystic/mis
    when i did this said /mystic/mis couldn't find the /mystic/misb dir

    this sudo setcap 'cap_net_bind_service=+iep' mystic/mis

    just went back to prompt as though it worked but did open the port

    my mystic is in /home/pi/mystic

    Thank you

    Ian




    === MultiMail/Win v0.52
    --- SBBSecho 3.11-Win32
    * Origin: 1st Choice Core (21:1/115)
  • From Sneaky@21:1/115 to Al on Sat Jun 12 20:01:00 2021
    Hi Al

    Try it like this..

    sudo setcap 'cap_net_bind_service=+ep' mis

    in your mystic directory. That command works for me, anyway.

    I did try it no errors, just went back to prompt as thought it
    worked but no change to the opening the port in ./mis -server
    still the same.

    Thank you
    Ian

    === MultiMail/Win v0.52
    --- SBBSecho 3.11-Win32
    * Origin: 1st Choice Core (21:1/115)
  • From DustCouncil@21:1/227 to Sneaky on Sat Jun 12 08:13:16 2021
    when i did this said /mystic/mis couldn't find the /mystic/misb dir
    my mystic is in /home/pi/mystic


    Oh I see; that'd be the issue -- you're installing this in a different directory.

    Point it to wherever mis is. In your case, likely:

    sudo setcap 'cap_net_bind_service=+iep' /home/pi/mystic/mis

    When I did this, it did not return any kind of message. But once I did it,
    the ssh server was able to bind to the port.

    Alternately you can move the SSH port over 1024, in which case you shouldn't even have to do this.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)
  • From Al@21:4/106.2 to Sneaky on Sat Jun 12 01:43:22 2021
    sudo setcap 'cap_net_bind_service=+ep' mis

    in your mystic directory. That command works for me, anyway.

    I did try it no errors, just went back to prompt as thought it
    worked but no change to the opening the port in ./mis -server
    still the same.

    After you run that setcap command you can run mis on ports below 1024 without being root or using sudo.

    You can check what capabilities are set with getcap..

    sudo getcap mis, in your mystic directory.

    If there are still errors there must be something wrong. Maybe the port is already in use?

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)
  • From Sneaky@21:1/115 to DustCouncil on Sat Jun 12 21:44:00 2021
    Hi DustCouncil



    Oh I see; that'd be the issue -- you're installing this in a different directory.

    Point it to wherever mis is. In your case, likely:

    sudo setcap 'cap_net_bind_service=+iep' /home/pi/mystic/mis

    When I did this, it did not return any kind of message. But once I did it, the ssh server was able to bind to the port.

    Alternately you can move the SSH port over 1024, in which case you shouldn't even have to do this.

    Ok, well Al ask me to do a sudo getcap mis and said mis =cap_net_bind - service+eip
    so the command worked, I also said I must have 22 running at same time
    which I had,using putty , I shut yje rasberry pi service down and and it opened the port and now
    it listing to the port so thank you very much for your help with that part of my problem

    I have my ssh (22) pointing to network node number in my forwaring router like my 1030 etc
    but if I do 5thchoicecore.ddns.net:22 it just won't connect at all so no logs what else do I have to do in mystic for me to login

    using syncterm, magiterm, putty (connection refused)

    Thank you

    Ian
    === MultiMail/Win v0.52
    --- SBBSecho 3.11-Win32
    * Origin: 1st Choice Core (21:1/115)
  • From Sneaky@21:1/115 to Al on Sat Jun 12 21:53:00 2021
    Hi Al

    sudo getcap mis, in your mystic directory.

    done mis =cap_net_bind - service+eip

    If there are still errors there must be something wrong. Maybe the port
    is already in use?

    yes well I was using rasberrpi service running, I stopped it and that fixed
    it in mis -server it is now listing to the port , that part fixed thank you

    I have the network no pointing to 22 in router and tried to connect but was refused so what else do I have to do to login to my bbs/linux.

    Thank you

    Ian




    === MultiMail/Win v0.52
    --- SBBSecho 3.11-Win32
    * Origin: 1st Choice Core (21:1/115)
  • From Al@21:4/106.2 to Sneaky on Sat Jun 12 03:36:06 2021
    I have the network no pointing to 22 in router and tried to connect but was refused so what else do I have to do to login to my bbs/linux.

    If your mis server is listening but you get no response I would check the settings for your ssh server.

    IPV4 Adapter 0.0.0.0
    IPV6 Adapter ::
    Port 22

    That's what mine looks like.

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)
  • From Sneaky@21:1/115 to Al on Sun Jun 13 08:45:00 2021
    Hi Al

    Al> If your mis server is listening but you get no response I would check
    the settings for your ssh server.

    IPV4 Adapter 0.0.0.0
    IPV6 Adapter ::
    Port 22

    That's what mine looks like.

    Yes that worked, now can ssh into my bbs, thank you very much for you help
    with setting up ssh for me.

    Have a nice day

    Ian

    === MultiMail/Win v0.52
    --- SBBSecho 3.11-Win32
    * Origin: 1st Choice Core (21:1/115)
  • From Al@21:4/106.2 to Sneaky on Sat Jun 12 14:10:44 2021
    Yes that worked, now can ssh into my bbs, thank you very much for you help with setting up ssh for me.

    No problem Sneaky, any time.

    It was actually DustCouncil that hooked you up with the setcap command. I was just commenting.. :)

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)
  • From Sneaky@21:1/152 to DustCouncil on Sun Jun 13 10:06:14 2021
    Hi DustCouncil


    sudo setcap 'cap_net_bind_service=+iep' /home/pi/mystic/mis

    Thank you for pointing this command out to me and yes it did help me

    with yor help + Al it is now working in mystic config server for ssh I had 127.0.0.1
    and it should have been 0.0.0.0 so I can now login and thats great.

    so again thank you for your help with this

    Ian


    ___ MultiMail/Win v0.52

    --- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
    * Origin: 2nd Choice Core : New Zealand (21:1/152)
  • From Sneaky@21:1/152 to Al on Sun Jun 13 10:06:14 2021
    Hi Al

    Yes that worked, now can ssh into my bbs, thank you very much for you help with setting up ssh for me.

    No problem Sneaky, any time.

    Cool thank you

    It was actually DustCouncil that hooked you up with the setcap command.
    I was just commenting.. :)


    Yes I have just sent DustCouncil a thank you message for pointing that out to me.

    Have a nice Day

    Ian

    ___ MultiMail/Win v0.52

    --- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
    * Origin: 2nd Choice Core : New Zealand (21:1/152)