TCP Ports for receiving Axis Object Analytic Events
Answered
Does anybody know if the ports on which NX Witness receives Object Events from Axis cameras are static, or can they change? It seemed like after a restart of NX the ports changed? I'm just trying to work out local firewalling on the VM running NX.
2024-03-19 11:27:25.308 2050365 INFO nx::network::http::TestHttpServer(0x7f938017c8c0): Started on 1.1.1.1:33609
2024-03-19 11:28:06.727 2050365 INFO nx::network::http::TestHttpServer(0x7f9380293400): Started on 1.1.1.1:39699
2024-03-19 11:49:57.168 2050365 INFO nx::network::http::TestHttpServer(0x7f938017c8c0): Stopped (NX Restart)
2024-03-19 11:52:36.554 2050365 INFO nx::network::http::TestHttpServer(0x7f9380739bc0): Started on 1.1.1.1:44447
2024-03-19 11:58:19.809 2050365 INFO nx::network::http::TestHttpServer(0x7f938014e180): Started on 1.1.1.1:46029
Thanks
-
Good question Campbell Steven.
To be honest, I don't know, but will ask around if someone knows it, and let you know once I know more. -
Thanks Norman - Nx Support once discovered it would be a good one to add to the required ports page as an option for if you are running Axis cameras.
-
Hi Campbell Steven,
What you shared is part of a private build and can be ignored, and there is no need to forward any ports, all metadata is received along with the mediastream via RTSP.
-
Oh right, it was just on an official release of: 5.0.0.36634 not any beta or unreleased build.
What I noticed is blocks like this on the local firewall of the VM showing the Axis cameras calling back to these TCP ports where the camera is 2.2.2.2 and the server is 1.1.1.1:
Mar 19 11:51:26 cus-nxwitness2 kernel: [26008892.963630] [UFW BLOCK] IN=ens19 OUT= MAC=c2:5c:6c:43:be:ef:00:50:00:00:be:ef:08:00 SRC=2.2.2.2 DST=1.1.1.1 LEN=60 TOS=0x00 PREC=0x00 TTL=61 ID=28978 DF PROTO=TCP SPT=52214 DPT=39699 WINDOW=64240 RES=0x00 CWR ECE SYN URGP=0
And until I allowed these on the firewall the object analytic events didn't seem to work for us.
-
Hi Campbell Steven,
That is strange. What you shared shouldn't exist in a release.
However, please upgrade to 5.1.3, which is the latest and greatest, and let us know if the issue still occurs.
You can use the following update credentials:Build Number: 38363
Password: lszxqn
Post is closed for comments.
Comments
5 comments