rx78nt1alex
n3wb
Rather new member, but thought I would pass this along. I have a 4MP S3VC POE camera, which has great picture and, from my experience, good night vision. I was frustrated with it not working with Chrome or Firefox, so I got bored and in Chrome, right clicked on the web ui from the login screen, and hit "Inspect". I saw the following.
WebSocket connection to 'ws://XXX.XXX.XXX.XXX:12352/' failed: WebSocket is closed before the connection is established. worker_recv.js:1
Upon allowing the port shown in my forwarding table for testing, I got this.
The websocket connected. 0 worker_recv.js:1
codec_id= 28 raw_player.js:1
(id:0) running... decoder_worker worker_ffmpeg.js:1
I then clicked on Sub-Stream and Main Stream, and the video worked in Google Chrome. Every once in a while, it seems that the time reset to 1-1-18 Tuesday, 00:00, but would come back to normal time when I went to System, Date and Time, Refresh.
After a while, the following showed up and the video froze.
wait timeout, close websocket. 1 worker_recv.js:1
It appears to be tied to the browser getting access to the camera through video.js, though I'm not too sure. Any other info would be good. I plan to keep these ports closed, but thought that if someone really wanted to see it in other browsers would like this. I'm just not too sure about this being a vector of attack, as it isn't a port that is listed in the device configuration you can adjust.
WebSocket connection to 'ws://XXX.XXX.XXX.XXX:12352/' failed: WebSocket is closed before the connection is established. worker_recv.js:1
Upon allowing the port shown in my forwarding table for testing, I got this.
The websocket connected. 0 worker_recv.js:1
codec_id= 28 raw_player.js:1
(id:0) running... decoder_worker worker_ffmpeg.js:1
I then clicked on Sub-Stream and Main Stream, and the video worked in Google Chrome. Every once in a while, it seems that the time reset to 1-1-18 Tuesday, 00:00, but would come back to normal time when I went to System, Date and Time, Refresh.
After a while, the following showed up and the video froze.
wait timeout, close websocket. 1 worker_recv.js:1
It appears to be tied to the browser getting access to the camera through video.js, though I'm not too sure. Any other info would be good. I plan to keep these ports closed, but thought that if someone really wanted to see it in other browsers would like this. I'm just not too sure about this being a vector of attack, as it isn't a port that is listed in the device configuration you can adjust.
