Support for ARTPEC-5 and ARTPEC-4?

[tris]

Thank you for the most excellent app! I'm running it on three Axis cameras (ARTPEC-6 and ARTPEC-7).

In case it's possible to support older cameras on SDK 2, here's the (lightly edited) getAllProperties output from my M5525-E:

$ curl --anyauth -s -u root http://10.8.0.26/axis-cgi/basicdeviceinfo.cgi --data '{"apiVersion":"1.0","context":"","method":"getAllProperties"}' | jq
Enter host password for user 'root':
{
  "apiVersion": "1.0",
  "data": {
    "propertyList": {
      "Architecture": "mips",
      "HardwareID": "757",
      "ProdVariant": "",
      "WebURL": "http://www.axis.com",
      "ProdNbr": "M5525-E",
      "SerialNumber": "xxxxxxxxxxxx",
      "Brand": "AXIS",
      "SocSerialNumber": "",
      "Soc": "Axis Artpec-5",
      "BuildDate": "Oct 29 2020 11:52",
      "ProdShortName": "AXIS M5525-E",
      "Version": "8.40.4.1",
      "ProdFullName": "AXIS M5525-E PTZ Dome Network Camera",
      "ProdType": "PTZ Dome Network Camera"
    }
  },
  "context": ""
}

I also have a P5414-E running firmware 6.50.5.8 (latest available) which does not have the /axis-cgi/basicdeviceinfo.cgi endpoint. It's listed on https://camstreamer.com/download-app-all-supported-cameras as "Artpec-4 (MIPS) SDK 2".

[tris]

Some testing (manually copying tailscale_1.38.4_mipsle.tgz over) reveals that tailscaled appears to run fine on the P5414-E, but then amusingly the OOM killer comes for it as soon as I run tailscale up. So I think that one is probably not worthwhile.

I still have high hopes for ARTPEC-5, but I temporarily lost VPN access to that camera -- will report back.

[Mo3he]

Hi, Sorry for my delayed response, I have been trying to understand how to compile the acap for version 2.0 that would work on Artpec5 but have had no luck so far. please try the below instructions as this is esentially what the acap does but using a script.

To install Tailscale on Axis cameras Copy the files "tailscale" and "tailscaled" for the correct proccesor to the camera in a new directory /usr/local/packages/tailscale cd /usr/local/packages/tailscale chmod 777 tailscaled chmod 777 tailscale Copy "tailscaled.service" to /etc/systemd/system systemctl daemon-reload systemctl enable tailscaled.service systemctl start tailscaled.service cd /usr/local/packages/tailscale ./tailscale up Copy URL to browser to authenticate Tailscale

[bryanjhv]

I'm trying to run Tailscale inside a M5525-E (ARTPEC-5) also. After some investigation, here's what I've found so far:

• It uses AXIS SDK 2, which is not available anymore from Axis.
• Only compiler I found is in Docker image at https://github.com/trunnion/cargo-acap/blob/8d5dce4cd1de5788e7387e19e4dac9afa8f59f5e/cargo-acap-build/Dockerfile#L32.
• Supports at least two kinds of APPTYPE (lua undocumented and artpec-5/mipsisa32r2el).
• The architecture used by ARTPEC-5 is MIPS little-endian using soft-float feature (non standard).
• When targeting artpec-5, OS checks if binary is dynamically linked, fails if APPNAME binary is static.

So, with these details, we find that:

• It's hard to use C/C++ without a custom-built MIPSEL compiler that uses soft-float.
• Same goes for Go, which using GOOS=linux and GOARCH=mipsle generates a static binary.
• Rust neither, by requiring a custom compiler like C/C++ and also a custom target and rustc.

That in mind, options would be reduced to:

• Zig CC/C++ if wanting to use C/C++ (generates a dynamic exe).
• Pure Zig using Release* (until https://github.com/ziglang/zig/issues/19433 is solved) and LinkLibC.

I'll keep trying some method until it works. Is there anything else I should take into account? Like, for example, ways to disable the OOM killer mentioned above, and other quirks?