The Features Menu :: FTP


param.cgi?cmd=getftpattr

Get INSTAR Cloud Server Parameter

  • ft_server: FTP Server Address
  • ft_port: FTP Server Port
  • ft_username: FTP Username
  • ft_password: FTP Password
  • ft_mode: FTP Mode Passive (0) or Port (1)
  • ft_dirname: FTP Directory
  • ft_autocreatedir: Automatically create the directory 0 (no), 1 (yes)
  • ft_dirmode: 0 (All Files in One Directory), 1 (Create a new Folder every Day)
  • ft_ssl: FTPS Encryption - 0 None, 1 FTPS, 2 sFTP
  • ft_insecure: Verify SSL Certificate 1 (no), 0 (yes)

Example

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=getftpattr

cmd="getftpattr";
ft_server="192.168.2.111";
ft_port="21";
ft_username="admin";
ft_password="instar";
ft_dirname="./hello";
ft_dirmode="1";
ft_mode="1";
ft_ssl="1";
ft_insecure="1";
response="200";
GET: http://192.168.2.168/param.cgi?cmd=getftpattr&user=admin&pwd=instar

cmd="getftpattr";
ft_server="192.168.2.110";
ft_port="22";
ft_username="ipcamera";
ft_password="admin";
ft_dirname="instar";
ft_dirmode="0";
ft_mode="1";
ft_ssl="2";
ft_insecure="0";
response="200";
SET: http://admin:instar@192.168.2.168/param.cgi?cmd=setftpattr&ft_server=192.168.178.1&ft_port=21&ft_username=ftpuser&ft_password=123456&ft_mode=1&ft_dirname=.%2F&ft_insecure=1&ft_dirmode=1&ft_ssl=0

cmd="setftpattr";
response="200";

Using sFTP instead of FTPS

Our previous camera series already supported wrapping the FTP upload in SSL (TLS) encryption - FTPS. With the WQHD series we added the secure upload through a so-called SSH tunnel - sFTP. THis can be activated through the ft_ssl parameter:

  • ft_ssl=0: No encryption (Default Port 21)
  • ft_ssl=1: FTPS (Default Port 21)
  • ft_ssl=2: sFTP (Default Port 22)

When using the sFTP service you no longer need an FTP Server to receive the camera upload. You only need a LINUX PC (even a Raspberry Pi is sufficient) and a user for your camera:

useradd -m -d /home/ipcamera ipcamera

This command will add a user called ipcamera and creates a home directory in /home/ipcamera (you can choose a different name and directory). To allow our camera to log in using this user we have to add a password:

passwd ipcamera

New password: password
Retype new password: password
passwd: password updated successfully

In this example we now created a user login with username ipcamera and password password. You can verify that everything worked by switching to this user:

su - ipcamera
$ pwd
/home/ipcamera

Let's create a directory called recordings inside the home directory using the ipcamera user:

mkdir recordings

We can now configure our camera to use this login to upload all alarm recordings into the recordings folder:

cmd="getftpattr";
ft_server="192.168.2.110";
ft_port="22";
ft_username="ipcamera";
ft_password="password";
ft_dirname="recordings";
ft_dirmode="0";
ft_mode="1";
ft_ssl="2";
ft_insecure="1";
response="200";

Note that you have to use the ft_insecure=1 option because your camera's Linux system does not know the the server and cannot verify that it actually is an allowed client.

To get rid of this limitation you run the testftp command (see below) - it will now (since we activated sFTP) return the server Host Key that you can use to add the server to the list of allowed hosts:

cmd="testftp";
hostkey="AAAAC3NzaC1lZDI1NTE5AAAAIHzXGgltq4a8PS6QH9u334FGdxJmEzQ0klKtUw+1iSle";
result="0";
response="200";

To be able to disable the ft_insecure option we can now add the host key to our camera using the testftp command (see below):

param.cgi?cmd=testftp&sethost=AAAAC3NzaC1lZDI1NTE5AAAAIHzXGgltq4a8PS6QH9u334FGdxJmEzQ0klKtUw%2B1iSle

Note that the key might contain letters that are not allowed in URLs and have to be encoded. For example, my key above contained the letter + that would break the command. This letter has to be substituted by %2B as seen in the command above. You can use a service like www.urlencoder.io to make sure the key is save to use with the CGI command:

www.urlencoder.io

We can now also add the camera public key to the list of known hosts on our receiving Linux server using the getpubkey command (see below):

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=getpubkey

cmd="getpubkey";
publickey="ssh-rsa AAAAB3Nz ... DGhllCPSbDXV55ZWtxNNcw==";
response="200";

This key needs to be copied to nano ~/.ssh/authorized_keys on your Linux server - just append it at the end of the file:

ssh-rsa AAAAB3Nz ... DGhllCPSbDXV55ZWtxNNcw==

param.cgi?cmd=getpubkey

Get the public SSH key of your camera. This key can be added to the list of known hosts on your Linux server that you want to use as your sFTP host.

Generate a Public Key

  • publickey: Return your camera's ssh-rsa key.

Example

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=getpubkey

cmd="getpubkey";
publickey="ssh-rsa AAAAB3Nz ... DGhllCPSbDXV55ZWtxNNcw==";
response="200";

param.cgi?cmd=testftp

Use the FTP configuration to upload a test snapshot Test-Snapshot.jpeg to your FTP server.

Test FTP Server Parameter

  • result:
    • 0 : Success
    • -1: Can’t connect to Server
    • -2: Invalid credentials
    • -3: Permission error / Bad path
    • -4: Timeout
    • -5: Server cannot be verified
    • -6: Busy
    • -7: Internal error
    • -8: Unknown error
    • -9: Transfer incomplete

Example

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=testftp
result="0";

param.cgi?cmd=getftpaction

Set FTP Storage Parameter

Recording options on FTP server:

  • enable: Enable / Disables specified upload action to the FTP server [0, 1]
  • interval: Cooldown time between Uploads [1 - 3600] s
  • type: rec, snap, timersnap
    • rec: Alarm video recording
    • snap: Alarm snapshot recording
    • timersnap: Planned snapshot recording

Example

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=getsdaction

cmd="getftpaction";
enable['rec']="0";
interval['rec']="0";
enable['snap']="0";
interval['snap']="15";
enable['timersnap']="0";
interval['timersnap']="820";
response="200";
GET: http://192.168.2.168/param.cgi?cmd=getftpaction&type=snap&user=admin&pwd=instar

cmd="getftpaction";
enable="0";
interval="15";
response="200";
SET: http://admin:instar@192.168.2.168/param.cgi?cmd=setftpaction&type=rec&enable=1&interval=60

cmd="setftpaction";
response="200";

param.cgi?cmd=getftpactionattr

Function | Get Snapshot Count for the Alarm FTP Upload

  • snapcount: Count of snapshots uploaded to the FTP server with every alarm event [1-10]

Example

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=getftpactionattr
cmd="getftpactionattr";
snapcount="5";
response="200";
GET: http://192.168.2.168/param.cgi?cmd=getftpactionattr&user=admin&pwd=instar
cmd="getftpactionattr";
snapcount="5";
response="200";
SET: http://admin:instar@192.168.2.168/param.cgi?cmd=setftpactionattr&snapcount=10
cmd="setftpactionattr";
response="200";

param.cgi?cmd=getsnaptimerftpattr

Set File Name for Interval FTP Snapshot Upload

  • mode: Activate fixed filename (instead of generated by timestamp) [0,1]
  • name: Set filename
  • prefix: Use given name as custom prefix [0,1]

Example

GET: http://admin:instar@192.168.2.168/param.cgi?cmd=getsnaptimerftpattr

cmd="getsnaptimerftpattr";
mode="1";
prefix="1";
name="test";
response="200";
GET: http://192.168.2.168/param.cgi?cmd=getsnaptimerftpattr&user=admin&pwd=instar

cmd="getsnaptimerftpattr";
mode="1";
prefix="1";
name="test";
response="200";
SET: http://admin:instar@192.168.2.168/param.cgi?cmd=setsnaptimerftpattr&name=instar

cmd="setsnaptimerftpattr";
response="200";