Review - TOP-201 Super Mini 720P HD IP-Cam (The Cheapest IP Cam So Far !!)

Hi.
As FTP video recording is not possible because of non existing local storage I played a little bit with camera and managed to mount NFS (network file system) in camera.
This could be solution for storage but the problem is how to tell software to use mounted NFS as storage. I altered firmware and tried to mount NFS on /mnt/sdcard and /mnt/usb/0 but camera wont use it as storage.
Does anyone have idea how to instruct camera software to use mounted NFS?
Don, what developers say about adding NFS support to firmware? That would be a great feature.
 
Don, I will update windows and IE tonight. But meanwhile let me ask you, please. Does the camera have to be password protected in order for Device Manager to run firmware update? I think you've mentioned that in one of your previous replies. You've wrote:

"The Device Manager requires that the user and password fields in the Device Manager window. Contain an admin User Id and Password for any firmware upgrade to be done successfully."

Is that so? Why am I getting an error message when trying to assign a password?

Yes, I was using all newest CMS and Device Manager yesterday trying to update firmware.
 
Last edited by a moderator:
TheUberOverLord said:
Much like FTP. This manufacturer most likely would not support any NFS interface in the future, without the mini IP Camera board having a SD card to cache video recordings. So that if anything were to go wrong with the NFS interface. Like it could with the FTP interface. That the mini IP Camera would be able to queue files as needed to the SD card.

Because of this. I personally don't think that any mini IP Camera boards manufactured by this manufacturer would ever support NFS in the future, without those mini IP Camera boards also having a SD card. Due to not being able to support a fallback if there were issues with the NFS interface.

Also. This manufacturers CMS ("Camera Management System") supports local storage. Which is a far cry from supporting NFS.

Note: There is also a VMS ("Video Management System") which this manufacturer currently has in beta. I am not sure what features it has over their CMS software. But it would still require a Windows system to be on 24/7/365 to run it. More here ("Translated from Chinese to English using an online translator"):

http://www.microsofttranslator.com/bv.aspx?from=&to=en&a=http://bbs.xm030.com/thread-3623-1-1.html

Don
Click to expand...

Thanks for your reply Don. I readed earlier informations at links you sent (and also xm030.com wiki and bbs).

So, NFS has much less overhead than FTP and could easily be used as storage because support for mounting NFS already exists in current firmware. I manualy mounted NFS share in camera and could read and write on it.
On 100Mbps local network it's speed is almost equivalent to class 10 SD card (10MBytes/sec) so video caching would be no problem. There are no delays in writing to NFS share because is optimized for purposes like this (FTP is ment to be used for other stuff). Developers should try this method because I suppose they don't have to change much in camera software (just point recording to mounted folder).
I found this feature exists on some other cameras (other manufacturers) so it's definitively possible (that cameras also lacks at internal storage).

I will continue to try to enable this feature myself but it's a little bit hard because I don't have source code and what I'm doing is trial and error method.

I'm doing this because camera is strong enough to do all the job itself (motion detection) so no need for NVR or computer just some storage (network HDD).

Tom
 
TheUberOverLord said:
You are very welcome.
...
It appears that both the SD card format and the video files stored on the SD cards of the mini IP Camera boards that include SD cards. Use a proprietary format created by this manufacturer. Which actually requires the use of programs provided by the manufacturer called "DiskPlayer" or "VDiskPlayer" for this series of mini IP Camera boards and cameras that include SD cards. To be able to access those files directly from the SD card.

Which of course would also complicate creating 3rd party methods to access video recording files stored on the SD cards of the mini IP Camera boards that have those SD cards or even using other mounting methods.

Since the SD card is supposedly formatted using the manufacturers proprietary format one can assume that the firmware would need to write in that format as well. If this is true? The problem is that there is very little specific documentation of the mini IP Camera boards with a SD card about their SD card access.
...
Don
Click to expand...

Thanks for your reply, it is very useful.
Unfortunately, use of proprietary sd card format could be a big problem in my attempt to use NFS mount instead of SD card mount as a storage.


Tom
 
Don,

After multiple attempts to upgrade firmware via CMS and Device Manager, the firmware number does not change and remains to be: V4.02.R12.00006510.10010.1303. In Device Manager I made sure that checkbox on the left of the Camera is checked. I've also tried all above in a different boot, using Win 7 32bit and there I was able to access the camera via IE using ActiveX, however firmware upgrade via IE is not changing the firmware number either. No matter which method I'm doing, firmware is not upgrading. It gives me messages such as "upgrade compete" or similar, then camera reboots. When it comes back - firmware is same. I suppose this is because I bought it from Amazon and it's probably re-branded?

Do you think I better send it back and get one from http://www.buyincoins.com ? Is it worth having newest firmware???

Another question is this: How many pictures can be emailed or sent to an FTP upon motion detection event? Can a whole sequence be emailed/FTPed ? How frequently alarm snapshots can be taken, i.e. every 1 sec, 5 sec.. etc..? Is that time interval adjustable? Thanks!
 
DaveP said:
Maybe the 'new' firmware has been named incorrectly and is indeed the old, lol
Click to expand...

Yeah... I wish it would be that easy... it is version:
General_HZXM_IPC_HI3518E_50H10L_S38_RT3070_V4.02.R 12.20150317_ALL.bin from Don's link. Why is it not updating? Has anyone tried that firmware version?
 
Hi.

After a lot of hours reading. :-) I didn't find the answer on the snapshot request.

Is there any hope for URL snapshots? That's actually all I need for my Homeseer installation.

Regards
Morten

"Hardware" : "HI3518E_50H10L_S39"
System: V4.02.R.12.00006510.10010.1407
Build date: 2014-09-15 19:22:36
 
Don: You are everywhere! =)

I've a ANRAN branded ipcam wich I bought for fun a year ago. All the screens and settings i've seen so far in this thread is exactly the same as mine Anran branded bullet cam.
I was wondering.Is it possible to upgrade the FW for this ANRAN branded cam with a generic file from the links above?
This is how my config/settings page look like.

attachment.php
 

Attachments

  • Skärmklipp.JPG
    Skärmklipp.JPG
    27.8 KB · Views: 412
TheUberOverLord said:
Currently, there are no methods to pull a snapshot using a URL to pull a image directly from this series of mini IP Cameras. This manufacturer is aware that this is a well wished for feature. Not sure if they will ever add it or not.

Don
Click to expand...

Hi Don.

:-(

Thanks for all your good information. :-)

Regards
Morten
 
TheUberOverLord said:
Currently, there are no methods to pull a snapshot using a URL to pull a image directly from this series of mini IP Cameras. This manufacturer is aware that this is a well wished for feature. Not sure if they will ever add it or not.

Don
Click to expand...

Don - I take it this means that we are unable to use this camera with your Embedding of IP Camera Secure in Website package (thanks for that by the way)?
 
Hello EveryOne!

Does anybody managed to force these camera for record movies under Linux headless?

I use Ubuntu 14 and already spent a whole day trying to make this camera works.

First of all I tried Motion. That works perfect with my USB camera. But Motion now is useless because the camera doesn't feed MJPEG streams at its latest firmware (only h264). But Motion works only with MJPEG or just stream of JPegs.

Then I tried to use ZoneMinder. But I can't find the right parameters for the camera path. ZM doesn't see the camera....
 
TheUberOverLord said:
Yes.

You can use FFmpeg. More details here:

https://www.ffmpeg.org/

If you need to get the proper RTSP URL's ("For the main and sub stream video") that can be used with this series of mini IP Camera boards from this manufacturer. Then please also see the link below which can also help you use these mini IP Cameras with ZM ("Zone Minder") as well:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=19499&viewfull=1#post19499

Don
Click to expand...

Hello Don,

As usually I didn't get it completely. So as I understand:

1. You also think that Motion can't work with these cameras due to absence MJPEG stream in the latest firmware.
2. You think that ZoneMinder can work with this camera.
3. Probably ZM should work with the camera but FFMpeg should be involved.

I didn't get it with points 2 and 3. :) It is not clear how to enter values of the camera with ZM. This variant:
attachment.php

Brings me this error:
Unable to get RTP Info identifier from response 'RTSP/1.0 200 OK Server: H264DVR 1.0 Cseq: 3 Range: npt=now- Session: 42522670 '

ZoneMinder 1.26.5. May be probably I should upgrade to 1.28 version....

With FFMPeg as I understan - I should receive a feed from the camera to FFMpeg Server and stream this to somewhere. And ZM should get this stream as input. I checked documentation for FFMpeg and found that in general it is possible but I can't understand how :)
 

Attachments

  • 2015-05-07_9-27-35.png
    2015-05-07_9-27-35.png
    19 KB · Views: 392
Later I've upgraded to the latest version of ZM (1.28.1). And used FFMpeg stream (FFMpeg server is not installed):
attachment.php

I have user admin and don't have password (as it is by default).

But I got the following records in Log:
attachment.php


And no records.....

Later I reduced the FPS values to 10 and 25 (for alarm) and now I get constantly this error in log:
Unable to open input rtsp://192.168.1.10:554/user=admin&channel=1&stream=0.sdp?real_stream--rtp-caching=100 due to: Operation now in progress

Later I've changed the URL to rtsp://192.168.0.110/user=admin&password=tlJwpbo6&channel=1&stream=0.sdp?real_stream and it started to write something to the disk.

PS. In the screens above I used wrong IP address to the camera. The right address is 192.168.0.110. I also tried to use the URLs above with the right IP address with the same result.

PSS. Using AVReg I got the URL that works in VLC. It is rtsp://192.168.0.110:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream
But not in ZM not in AVReg I don't see the life feed from the camera. Just broken picture and nothing else....

This drives me crazy :)
 

Attachments

  • 2015-05-07_10-04-45.png
    2015-05-07_10-04-45.png
    15.1 KB · Views: 392
  • 2015-05-07_10-04-26.png
    2015-05-07_10-04-26.png
    16.3 KB · Views: 391
Last edited by a moderator:
TheUberOverLord said:
When your password is blank/empty for this camera you must use the hash for that blank/empty password as the password in the RTSP URL. You can also use the hash for any password you set these mini IP Cameras to by using its hash as well. The command to locate a hash for any users password for these mini IP Cameras is:
Don
Click to expand...

I personally give up with this camera. It is not a good product and looks like a piece of shit :) It is almost not usable with configurations which are a little bit different from the default. And my personal thought that it works well only with the provided windows software :-/
I tried different variants with ZoneMinder and AVReg => no picture and not video even if programs can see the camera.

I also was surprised with VLC when HD stream pauses after 2 seconds of translation but the alternative stream works well.

BTW the addresses which work with VLC and which are provided as a responce from 8899 port:
rtsp://192.168.0.110:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream--rtp-caching=100 <=== VLC Plays for two secs
rtsp://192.168.0.110:554/user=admin_password=tlJwpbo6_channel=1_stream=1.sdp?real_stream--rtp-caching=100 <== VLC plays well
 
????????? ????????? said:
I personally give up with this camera. It is not a good product and looks like a piece of shit :) It is almost not usable with configurations which are a little bit different from the default. And my personal thought that it works well only with the provided windows software :-/
I tried different variants with ZoneMinder and AVReg => no picture and not video even if programs can see the camera.

I also was surprised with VLC when HD stream pauses after 2 seconds of translation but the alternative stream works well.

BTW the addresses which work with VLC and which are provided as a responce from 8899 port:
rtsp://192.168.0.110:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream--rtp-caching=100 <=== VLC Plays for two secs
rtsp://192.168.0.110:554/user=admin_password=tlJwpbo6_channel=1_stream=1.sdp?real_stream--rtp-caching=100 <== VLC plays well
Click to expand...

It works like a champion with BlueIris... I have also used it with Xeoma and iSpy
 
Don - you are the calmest person I've ever seen :) But this camera makes me completely insane. I moved it from the city location to my village house. And trying to make it works.

I found that - it doesn't send e-mails anymore with the new provider. I tried to login to the mail server of the provider via Telnet and even chat for a while with their mail-sender. But the camera still can't send e-mails :) That is ridiculous.

Moreover I'm trying to set up sending pictures to my Linux FTP and this thing makes me sad. I've tried two different FTP servers. Spent hours googling for specific settings for the FTP servers with no result. It works with Windows FTP as a charm and completely refuses to work with Linux FTP :)

Here is an example of an attempt to send some pictures to Linux FTP from the camera :)

vsftpd.log [----] 144 L:[ 1+20 21/ 43] *(2323/4681b) 0010 0x00A
[*][X]
Sat May 9 18:39:50 2015 [pid 30077] CONNECT: Client "192.168.0.110"
Sat May 9 18:39:51 2015 [pid 30076] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:39:53 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:39:54 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 18:39:55 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 18:39:56 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 18:39:59 2015 [pid 30089] CONNECT: Client "192.168.0.110"
Sat May 9 18:40:00 2015 [pid 30086] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:40:02 2015 [pid 30090] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:40:03 2015 [pid 30090] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 18:40:04 2015 [pid 30090] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 18:40:05 2015 [pid 30090] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 18:40:08 2015 [pid 30101] CONNECT: Client "192.168.0.110"
Sat May 9 18:40:09 2015 [pid 30098] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:40:11 2015 [pid 30110] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:40:12 2015 [pid 30110] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 18:40:13 2015 [pid 30110] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 18:40:14 2015 [pid 30110] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 18:40:17 2015 [pid 30121] CONNECT: Client "192.168.0.110"
Sat May 9 18:40:18 2015 [pid 30120] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:40:20 2015 [pid 30122] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:40:21 2015 [pid 30122] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 18:40:22 2015 [pid 30122] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 18:40:23 2015 [pid 30122] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 18:40:25 2015 [pid 30128] CONNECT: Client "192.168.0.110"
Sat May 9 18:40:26 2015 [pid 30127] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:40:29 2015 [pid 30132] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:40:30 2015 [pid 30132] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 18:40:31 2015 [pid 30132] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 18:40:32 2015 [pid 30132] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 18:40:54 2015 [pid 30157] CONNECT: Client "192.168.0.110"

Later I turned on more detailed log:
Sat May 9 19:04:33 2015 [pid 31587] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 19:04:33 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "230 Login successful."
Sat May 9 19:04:33 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "PWD"
Sat May 9 19:04:33 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "257 "/volume1/EMule/Cam""
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD /volume1/EMule/Cam"
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD /192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Failed to change directory."
Sat May 9 19:04:35 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "MKD 192.168.0.110_0012129310f3"
Sat May 9 19:04:35 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Create directory operation failed."
Sat May 9 19:04:35 2015 [pid 31589] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 19:04:35 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD 192.168.0.110_0012129310f3"
Sat May 9 19:04:35 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:36 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "MKD 2015-05-09"
Sat May 9 19:04:36 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Create directory operation failed."
Sat May 9 19:04:36 2015 [pid 31589] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 19:04:36 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD 2015-05-09"
Sat May 9 19:04:36 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:37 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "MKD 01"
Sat May 9 19:04:37 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Create directory operation failed."
Sat May 9 19:04:37 2015 [pid 31589] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 19:04:37 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD 01"
Sat May 9 19:04:37 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:38 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "MKD pic"
Sat May 9 19:04:38 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Create directory operation failed."
Sat May 9 19:04:38 2015 [pid 31589] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 19:04:39 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD .."
Sat May 9 19:04:39 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:39 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD .."
Sat May 9 19:04:39 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:40 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD .."
Sat May 9 19:04:40 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:40 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD /192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 19:04:40 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Failed to change directory."
Sat May 9 19:04:41 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "QUIT"
Sat May 9 19:04:41 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "221 Goodbye."

It even doesn't send the pictures to the server.
 
Last edited by a moderator:
TheUberOverLord said:
I am trying to help you resolve your issues as quickly as I can. If I didn't remain calm why trying to do so. Then most likely, it might impact my ability to help you.

1. Your version of FTP AKA vsftpd ("The first two letters of vsftpd stand for very secure") is ("Not") using a standard version of the FTP protocol. Which is a unsecure protocol.

vsftpd uses a modified secured version of the FTP protocol and is not using the normal FTP protocol. Which the manufacturer of this series of mini IP Cameras currently does not support. More about the program vsftpd which you are trying to use as FTP ("Which won't work in this case") here:

https://security.appspot.com/vsftpd.html#about

2. I can't help you with your email issue unless you tell me who your Email provider is. I can say that GMAIL and normal FTP work fine.

More here on how to setup Email and FTP for this series of mini IP Cameras from this manufacturer:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=28481&viewfull=1#post28481

Note: I run and/or operate many different Linux servers ("Over ten") including two DigitalOcean VPS cloud servers which are running Ubuntu 14.04.2 LTS (GNU/Linux 3.8.0-29-generic i686) and have no issues with using normal versions of FTP with these mini IP Cameras on any of the ten Linux servers I run and/or operate.

Don
Click to expand...

Hello Don,

Your help is priceless for us. You work instead of the manufacturer :)

As to the issues:

1. vsftpd combines both FTP and SFTP. I can connect to the server from FAR Manager using strict FTP mode (active or passive modes works OK):
attachment.php


The same - I checked the connection with built it Windows ftp client which is surely not SFTP. And it works.

I also tried to use proftpd and the behaviour looked similar. I'd be happy if I can strict vsftp to only ftp mode but to be honest I don't know how.

2. As to e-mail. It was configured and it worked well at home. But outside of the home with different provider it doesn't work. Mail testing is not passing.
attachment.php


The only the responce I got is "Failed to connect to server". As I wrote before - I opened the server via telnet from inside of the same network where the camera is and it opened.
 

Attachments

  • FTP.png
    FTP.png
    19.7 KB · Views: 387
  • email.png
    email.png
    13.3 KB · Views: 338
You must log in or register to reply here.
Top Bottom