sshnpd configuration
Last updated
Last updated
sshnpd is the daemon that runs on a device to facilitate access using NoPorts.
These mainly mirror the parameters from but there's one fewer as the socket rendezvous is only ever set by the client.
This argument is the device address, a.k.a. the to address, since this is the address that the device is associated with. This argument is mandatory, in the form of an atSign. For example:
This is the address of the client(s) that will be allowed to connect to the device. For example:
As an alternative to defining a list of managers a policy manager can be used, and the policy defined on that manager will describe which clients are allowed to connect. For example:
The device name. This is used to associate multiple devices with the same atSign. By default the value is default so unless you want that as the device name you will need to include this parameter. For example:
An example of a complete command might look like this:
The daemon should normally be run as a service so that it starts up automatically and can be restarted if it should fail.
The rest of the configuration for sshnpd is contained in a separate guide:
Lots of configuration can be done to sshnpd by editing this file, such as changing the user that sshnpd runs as, changing the atSigns, enabling/disabling verbose logging, and more.
Sample override.conffile:
Adding additional arguments is as simple as modifying the Environment=additional_args=""string found inside of override.conf .
The example adds the --permit-open to the string of additional args which enables clients to access ports 22, 3389, and 2221 on localhost.
Don't forget to update sshnpd by executing (may require sudo):
Most mainstream Linux distributions use to manage services, and we provide a systemd unit file that's configured by the . That file can be edited after installation to customize or add additional options. For distributions such as OpenWrt we provide config and init files that can be customized with a text editor or configured through the web admin interface.
If you installed sshnpd through the , then you can modify the /etc/systemd/system/sshnpd.service.d/override.conf file to take advantage of the configurations and options listed above to tailor sshnpd to your needs.