- √ - HS and camera Cisco CIVS-IPC-2500

[Warichet]

a look on Wireshark is always helpful there (I really don't know these Cisco-Cams at all but I know enough Cisco-datasheets to be sure to know: reading them without seeing in Wireshark what the device really does, is useless anyway

I finally managed to setup Wireshark on the switch and ... surprise
what I'm seeing is not what I expected.
I thought the HS would authenticate with the cam and all subsequent requests would be honored.
Well,no, quite logically what I'm seeing is that the Visu is making the request, (not the HS) hence the pop-up for authentication is for the Visu (Linux & FF)
I guess those Username & Password fields in the Kamera setup are not used in my case (maybe only for the HS Client).
So, I thought it would be enough to create an account in the cam, the same as the local PC user: no go

[makki]

[QUOTE=Warichet;161595]
http://user : password@<ip>/img/video.mjpeg
Thats the same when you type in User/Pass in HS, this is HTTP Basic-Auth

although very questionable about security (not the topic)

Depends, this is Standard. Over HTTPS it's pretty safe, over HTTP it's crap but still standard

Sniffing: a good switch can do that (but sometimes maybe I'm too dumb, so I won't comment that further )

Makki

[Warichet]

Ok, "Kamera-Direktzugriff" means:
a) the Visu-Client - no matter if HS-Client or HSAV - gets the Image via HTTP directly from the cam. The HS is only involved in sending the HTML with <IMG/HREF to the Visu-Client.
b) opposite (not checked) the HS pulls the image into RAM and sends it to the HS/Client via HTTP

Understood ! thank you.

If the cam doesn't support HTTP Basic-auth clean, neither a) nor b) will really help

There is still another option:
http://user : password@<ip>/img/video.mjpeg although very questionable about security (not the topic) this is supposed to be a standard method. Shouldn't it be supported in the HS ? Any chance to get my message to DaCom ?
Also, in the menu "Kameras", there are options about "Passwortschutz, Benutzername, Passwort"
I've tried several variations, included the username & password of the cam admin. No luck !

a look on Wireshark is always helpful there

As a last resort, yes (sniffing on a switch is not easy, I've to setup a hub etc). But even fully understanding the process doesn't guarantee to bring a solution. I fear the worst.

I know enough Cisco-datasheets to be sure to know: reading them without seeing in Wireshark what the device really does, is useless anyway )

ûûh !

[makki]

Ok, "Kamera-Direktzugriff" means:
a) the Visu-Client - no matter if HS-Client or HSAV - gets the Image via HTTP directly from the cam. The HS is only involved in sending the HTML with <IMG/HREF to the Visu-Client.
b) opposite (not checked) the HS pulls the image into RAM and sends it to the HS/Client via HTTP

In both cases, if the cam doesn't do Standard HTTP-Authentication it will lead to trouble.

Case b) might help out if the client doesn't have direct IP-Access to the cam
(i.e. forwarded Ports from the Inet to HS, insane, I suggest a VPN always..)

If the cam doesn't support HTTP Basic-auth clean, neither a) nor b) will really help, a look on Wireshark is always helpful there (I really don't know these Cisco-Cams at all but I know enough Cisco-datasheets to be sure to know: reading them without seeing in Wireshark what the device really does, is useless anyway )

Makki

[Warichet]

You can imagine this like a caching proxy for the cam-images without "Kamera direktzugriff" and as the cam as well as the client might have more free resources I'd avoid it when possible

I've seen the checkbox "Kamera direktzugriff" in the user properties, I understand the word, but not the implications (the help doesn't say much).
So far, with all my tests, this box was checked. Without knowing the implications, I've no clue if it's right or wrong.
I've made a test with "Kamera direktzugriff" unchecked, then it doesn't work anymore (no picture in the Visu). What is the usage of the checkbox ? ie in which case is it unchecked ?
For me, "Kamera direktzugriff" is something like:
http://x.0.1.xx/img/video.mjpeg. But that's something to use within the browser for test purposes, don't see the link with the HS, unless the HS is building the same URL.

Also, I think I've been caught (again)
In a previous post, I've said that http://x.0.1.xx/img/video.mjpeg was working fine. That's correct, but .... it implies a previous login into the camera, hence the password is cached.
When trying from the Visu, or an untouched PC or clearing the cache, it doesn't work anymore, instead the cam displays a pop-up asking for username & password.
This brings my question again: the Visu is running in which context ?
If I know that, I can create a new user in the HS which is the same as the cam admin.

Also, I've tried cheating in the "Kamera" menu, with the "IP-Adresse der Kamera" with something like <username>:<password>@<IP address> no luck, the HS doesn't like it.

I'm stuck, so close to the goal

[makki]

No, it's not a user it's a process or a thread within one. Still many (slow) Cams make this thing in whole not faster..
You can imagine this like a caching proxy for the cam-images without "Kamera direktzugriff" and as the cam as well as the client might have more free resources I'd avoid it when possible

Makki

[Warichet]

if the HomeServer's Visu is accessing the page, which user is that ?

I guess it's not a user accessing the cam, but a process inside the HS ?
I've defined the cam without "Passwortschutz", but also tried with a username & password which I've defined the same way in the cam.
No go.

Any hint ?

[Warichet]

it slows down the HS noticeable

Didn't think about that aspect.

Thank you for your comments

[makki]

Does it make sense to archive camera images to the HS when a NAS is available ?
Any arguments pro/con ?

Absolutely only cons from me: it slows down the HS noticeable (anything related to tcp), if not needed turn on "Kamera Direktzugriff", let the HS do his job slowly and use better suited devices for saving/displaying the pictures
Since I turned that off, 90% of my problems went away (and yes, I should have known better before..)

Makki

[Warichet]

Hi,

I'm at the point where the camera image can be displayed in the Visu.
But each time I want to see the camera image, I need to supply a username/password.
In the camera itself, I can define a list of authorized users, but if the HomeServer's Visu is accessing the page, which user is that ?

Thnaks for any hint.

[Warichet]

Übersetzt: Soweit ich das richtig verstehe benutzt die Cam eine http_post Methode um die Ereignissdaten zum Webserver zu senden. Aber da geht's nicht weiter.

Correct

Isn't there a manual for this?

Ha ! you have a strong sense of humour
Yes, there is a manual (if you call that thing a manual) but it is a copy of what you see on screen, no explanation, no examples, no word about pre-requisites

I know a HTML form sending http post or get to a php script.
Maybe there is something similar?

Yes you are right.
I think something has to be enabled at Apache or PHP, but don't know what, still googling ...

Thank you.

[Bodo]

Hi

I'm sorry, I have no HS.

I understand the cam uses a http_post method to send the event data to the web server, but there it stops.

Übersetzt: Soweit ich das richtig verstehe benutzt die Cam eine http_post Methode um die Ereignissdaten zum Webserver zu senden. Aber da geht's nicht weiter.

Isn't there a manual for this?
I know a HTML form sending http post or get to a php script.
Maybe there is something similar?

[Warichet]

Hi Bodo,

I would prefer NAS, because a harddisk is suited for this

Indeed, that's the first idea that comes to mind, but I'm concerned with the integration. I fear if choosing an easy solution, closes the door for further integration.
As an example, I can't see how I can use an email or an ftp file to trigger a KNX alarm.
So, the http_post might be my best bet, but I'm still unable to make it work.

[Bodo]

Does it make sense to archive camera images to the HS when a NAS is available?

Hi

I would prefer NAS, because a harddisk is suited for this.
I dont know how data storage is solved at HS.
I think something like CF is used and this should not have too many write cycles.

[Warichet]

Hi,

So far, I can see the video stream in the Visu
The camera allows for motion detection, when such an event happens, some actions can take place.
So far I've got email and ftp working
I'm mainly interested in the "http notification" as it seems to be a way to integrate the motion event in the HS via a Webabfrage.

I'm unable to make it work . I understand the cam uses a http_post method to send the event data to the web server, but there it stops.

From Wikipedia, I understand that there are some pre-requisites (the server must be "enabled")
Can someone help me, please ?
Any modifs to php.ini or apache.conf ? modules to be installed ?

I tried the Qnap forum here, without much success.

Thank you