[solved] Purpose of Connectshares

Forum Forums New users New Users and General Questions [solved] Purpose of Connectshares

  • This topic has 3 replies, 3 voices, and was last updated Nov 18-12:42 am by Speedyg869.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #45052
    Member
    Speedyg869

      My question is about the purpose of Connectshares. From the docs in the Connectshares section of the antiX FAQ [https://download.tuxfamily.org/antix/docs-antiX-17/FAQ/connectshares.html], it seems as though Connectshares is for connecting to remote PCs. But does Connectshares have any effect on remote clients connecting to or sharing resources on my antiX PC?
      I’m running antiX 17.4.1.

      Thanks in advance.

      • This topic was modified 2 years, 5 months ago by Speedyg869.
      • This topic was modified 2 years, 5 months ago by christophe.
      #45080
      Member
      olsztyn
        Helpful
        Up
        0
        ::

        From what I know Connectshares function is connecting to shares hosted elsewhere, such as SMB servers.
        I have been using Connectshares extensively to connect to my several NAS servers.
        You might get a better answer from SamK in this forum, who developed/integrated Connectshares into antiX, or other experts. There are multiple videos made by Dolphin_Oracle how to use it…

        Live antiX Boot Options (Previously posted by Xecure):
        https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

        #45243
        Forum Admin
        SamK
          Helpful
          Up
          0
          ::

          But does Connectshares have any effect on remote clients connecting to or sharing resources on my antiX PC?

          If you mean:

            • Can the system on which Connectshares is installed make shares available to the network the answer is yes.
            • Can Connectshares make shares available to the network the answer is no.

          In cases where you have a machine on the network that is constantly available to provide resources to other systems it can be set up to serve shares by installing Samba or NFS. In such circumstances you must be prepared to do all the testing, configuration and maintenance of the chosen server. Additionally you must provide each of the workstations a way of mounting the shares e.g. Connectshares or some other means.

          In-house alternatives available in antiX

          Droopy
          This is a way to make files on your machine available to any other machine without installing any more software (it is shipped pre-installed in antiX-full). When Droopy is started it creates a folder named Public in your home directory. A web server is also started. Any workstation that has a web browser installed can upload and download files to and from that folder. When you close Droopy, the web server is automatically closed. In most cases the default configuration works without needing any changes. If required, it is easy to fine tune the config to suit your requirements. Droopy works with one file at a time, but that is easily managed by putting multiple files in an archive (e.g. *.zip *.tgz) and up/down the archive. Droopy is also able to work via the web browser on your ‘phone.

          A typical use case is impromptu file sharing, because it is simple and quick to use.

          The following video is out of date re set up and configuration. These were improved after the video was made. In terms of usability it is still OK. The video also mentions security but doesn’t say how to change it. Security settings are available via the configuration file for controlling options such as:

            • Use of a password to access the Public folder
            • Use of a certificate to enable https
            • Automatically setting the permissions of files uploaded to your system

          FAQ http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/droopy.html
          Video https://www.youtube.com/watch?v=J2I0okt7mIU

          SSH-Conduit
          This is a suite of apps that enable your system to connect to remote systems and for those remote system to connect to your system. In other words your system is able to operate as a server (provide resources to others) and as a client (obtain resources from others). Both of those roles can be conducted concurrently.

          The FS suite component may be of interest. It provides a way to add (mount) a remote folder into the local system or remove (unmount) it. This makes the remote folders and files available to use on your local machine. You use them as if they are kept in your local laptop. The suite can make connections on an ad hoc basis and/or employ one or more profiles that may optionally be automatically employed when a suite component is started.

          Announcement https://www.antixforum.com/forums/topic/ssh-conduit-suite/
          FAQ http://download.tuxfamily.org/antix/docs-antiX-17/FAQ/ssh-conduit.html
          Video https://www.youtube.com/watch?v=Y0up7Cluf4s

          #45268
          Member
          Speedyg869
            Helpful
            Up
            0
            ::

            @SamK:
            Wow! Great explanation. You have answered all my questions. Thank you!

            It would nice if there was a section in the FAQ which talked about a Windows client / antiX Server configuration using your explanation of the tools above. Then a section which talked about a antiX client / Windows server configuration using Connectshares and SSH-Conduit since it works both ways.

            Can a Mod mark this as resolved or tell me how to do it? Thanks.

            • This reply was modified 2 years, 5 months ago by Speedyg869.
          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.