mjhjmtu

I have an IP Camera from Thundersoft with a Qualcomm Snapdragon 625 chip inside that runs a Linux distribution. It is extremely limited in terms of available commands, and I can't install any new commands without reflashing it (and I'm trying to avoid that).

I'm trying to connect the camera to an external machine learning API, to process the frames from the camera, but I can't connect the camera to the internet and I don't really know how to address the problem.

I tried connecting it through an ethernet cable (it works perfectly on my computer), but when I run ifconfig it returns:

br0 Link encap:Ethernet HWaddr 00:0A:F5:27:C8:C4 
 inet6 addr: fe80::20a:f5ff:fe27:c8c4/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:268 errors:0 dropped:0 overruns:0 frame:0
 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0 
 RX bytes:22048 (21.5 KiB) TX bytes:536 (536.0 B)

eth0 Link encap:Ethernet HWaddr 00:0E:C6:8E:EE:C6 
 inet6 addr: fe80::20e:c6ff:fe8e:eec6/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:1497 errors:3 dropped:2 overruns:0 frame:3
 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000 
 RX bytes:861688 (841.4 KiB) TX bytes:1502 (1.4 KiB)

lo Link encap:Local Loopback 
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:8 errors:0 dropped:0 overruns:0 frame:0
 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0 
 RX bytes:448 (448.0 B) TX bytes:448 (448.0 B)

wlan0 Link encap:Ethernet HWaddr 00:0A:F5:27:C8:C4 
 inet6 addr: fe80::20a:f5ff:fe27:c8c4/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:284 errors:0 dropped:1140 overruns:0 carrier:0
 collisions:0 txqueuelen:1000 
 RX bytes:0 (0.0 B) TX bytes:27096 (26.4 KiB)

What should I do to diagnose and solve the problem?

[EDIT AFTER COMMENTS]

The camera has two modes: USB and LAN, and they can't work at the same time. So in USB mode there's no dhcp client (or at least no process called dhc), but when I run ps in LAN mode (with a program that runs on startup and logs to file, because I don't have access to shell on LAN mode), I get no output, so I don't really know the processes running. About the manual IP assignment, I've tried a few things I found, but I think the camera overwrites the configurations later, because the files change after reboot.

My network does have a DHCP server.

First thing to try is to assign an IP address manually,

ifconfig eth0 192.168.45.1 netmask 255.255.255.0

then use route to make sure that route is also set. Finally do the same on the PC it is connected to, using 192.168.45.2.

Now check with ping if they can reach each other.

If they can't, next step is to figure out how the IP cam uses the bridge br0; possibly it should get the IP address instead, if eth0 is a port in the bridge.

As soon as anything works, you can think about DHCP and how to automate it.