Acquisition of IP Address

17 posts / 0 new

Fri, 01/13/2023 - 13:06

K6BZZ

I am trying to attach an IP Cam to my AREDN Nano node. I have read many instructions and watched many videos, but have never been able to get the node to recognize the camera IP address. How do you do that? Is it supposed to be automatic when attaching the camera? I know the camera IP address but find nowhere to input it AREDN setup page.
Any help appreciated.

'73 de Dick K6BZZ

Fri, 01/13/2023 - 13:26

K6CCC

Needs to go the other way

Needs to go the other way around. Set the Camera to operate as a DHCP client and the camera will get an address from the node.

Fri, 01/13/2023 - 18:22

K5DLQ

(yes, the camera should be

(yes, the camera should be DHCP)
Also, a lot of cameras don't handle the IP stack very well. Try going to the Advanced Config page and enabling this setting:

Provide default route to LAN devices even when WAN access is disabled
aredn.@wan[0].lan_dhcp_defaultroute

then try again

Fri, 01/13/2023 - 19:03

(Reply to #3) #4

K6BZZ

Camera IP3.20 Sync

Thank you K5DLQ. That is not one of the choices in my Advanced Configuration. Maybe my problem is obsolete firmware. Running 3.20.3.1
Dick K6BZZ

Fri, 01/13/2023 - 19:10

(Reply to #4) #5

K6CCC

Yes, that is ancient firmware

Yes, that is ancient firmware.
However that should not prevent the camera from getting an IP address from the node. Look at Setup > Port Forwarding page. It should list the IP of the camera under DHCP leases.

Fri, 01/13/2023 - 19:48

(Reply to #5) #6

K6BZZ

Sync Camera and DHCP Lease

It lists the LAN IP address, not the camera IP address. Whichever of the 5 LAN addresses is showing in status is the one showing up there.

Fri, 01/13/2023 - 19:54

K6CCC

This is one of my nodes. The

This is one of my nodes. The currently connected devices are circled with the node assigned addresses.

That's right, this forum won;t let me do what I just did to post a picture. And I don't have time to upload the image to a website and link it...

Fri, 01/13/2023 - 20:16

KG7LMI

Re: DHCP

Hard to tell for sure what's happening here, but be aware that DHCP leases shown on the node are only listed when they are requested and assigned. Leases have a time to live, so if the client still has a valid lease, it may not show up on the node, esp if the node was rebooted recently. You can always use an IP scanner (such as Advanced IP Scanner for Windows) on the node's LAN to see what addresses are in use, even if they are not listed on the node. Look a the DHCP address range to determine the range of addresses to scan.

Rob

Fri, 01/13/2023 - 22:03

K6CCC

Here's the image I was trying

Here's the image I was trying to post earlier. The client devices that are connected to this node are shown in the red box.

If the image does not show in your browser, here is a direct link to it: http://extraphotos.info/images/AREDN-DHCP.png

It lists the LAN IP address, not the camera IP address. Whichever of the 5 LAN addresses is showing in status is the one showing up there.

That statement does not make any sense. Can you post a screen capture?

Sat, 01/14/2023 - 00:33

#10

K6BZZ

In setup LAN IP is 10.77.30.1. In DHCP reservation IP is 10.77 30.4.

Image Attachments:

Sat, 01/14/2023 - 00:57

#11

K6CCC

There are all kinds of things

There are all kinds of things wrong on that DHCP reservations page. First off, only your desktop actually is getting an IP Address from the node - 10.77.30.5. So it would appear that the camera is not getting an address from the node. That's your first issue. You have a reservation for something that would get a hostname of just your callsign with an IP of 10.77.30.4 if it has a MAC of 9C:8E:CD:36:80:F2 (if I read that right). From your text I gather that the MAC is that of the camera, so if that was the case the camera would get 10.77.30.4 as a DHCP address. However the camera is not getting a DHCP address from the node.
Your advertised service for the camera is pointing to the node itself rather than the hostname for the DHCP reservation for the camera. Same issue (I think) with the advertised service for the MeshChat. You are pointing to the node itself on port 8080 that is used for the web interface for the node. Full disclosure, I have never run MeshChat on a node - only on a connected RasPi - so not the expert on that one if you are running MeshChat on the node itself.
So your first issue is why is the camera not getting a DHCP IP address from the node. I would confirm that the camera is set up as a DHCP client. Until the camera has an IP Address on the node's LAN subnet, nothing is going to work. BTW, one option you could do is to set the camera itself to a static IP Address on that 10.77.30.4 address and leave the DHCP reservation in place. That will prevent the node from assigning that IP to some other device, and it gives you a way to select that hostname in the Advertised services section. I am doing that with Grandstream phone for the reason mentioned by K5DLQ in post #3

Sat, 01/14/2023 - 12:38

#12

K6BZZ

Now What

Some progress this morning but not there yet. The node now recognizes the camera and the lease is in place however I get this message when trying to connect to the camera. "Not Found. The requested URL/Camera was not found on this server."
Any suggestions appreciated.

K6BZZ

Image Attachments:

Sat, 01/14/2023 - 13:44

#13

nc8q

when trying to connect to the camera.

Exactly, How are you "trying to connect to the camera."?

Your 'Advertised Service' is not 'pointing to' 'Camera',
that link is pointing to your node.

Oh, buy the way, 'Hostname's should be unique in a network.
If your network grows...'Camera' may not be unique.
Would you consider changing the camera's hostname to 'k6bzz-camera' ?

https://docs.arednmesh.org/en/latest/arednGettingStarted/advanced_config.html#port-forwarding-dhcp-services-and-dns-aliases
...
'DHCP Address Reservations"
...
"The hostnames of every device connected to the mesh at large must be unique.
It is best practice to prefix your Amateur Radio callsign to the hostname of each
of your devices in order to have the best chance of it being unique on the mesh network."

73, Chuck

Sat, 01/14/2023 - 13:48

#14

K5DLQ

how are you accessing it?

are you going to http://10.241.51.5 to access it?

Or, using the advertised service named "Camera" that goes to http://k6bzz-2:8080/camera? (This is NOT where your camera is located)

Notes:
your "camera" hostname may not be unique on the mesh. It is best practice to name it with your callsign. ie. k5bzz-camera
Your advertised service "Camera" is probably not correct since it is linking to your NODE, not your Camera.

AND....

You should definitely upgrade to 3.22.12.0 ASAP!

Sat, 01/14/2023 - 15:25

(Reply to #14) #15

K6BZZ

IP Cam Now Working!

Thanks everyone. That was quite an exercise, but we're there now. The camera is working well. There is a long time delay on live view when moving camera. Maybe that's normal. I went to lower resolution and the time delay (about 15 seconds) is the same. It's not a problem but wonder if there is any way to speed up the feed?
See attachment for configuration that works.

Dick K6BZZ

Image Attachments:

Sat, 01/14/2023 - 16:33

#16

nc8q

any way to speed up the feed?

Is it the 'feed'?
You might want to measure the 'feed' to see if the issue is the IP path or the camera.
Tools like 'ping' and 'mtr' might help to discover where the issue is.
Or, if Windows:
https://sourceforge.net/projects/winmtr/

73, Chuck

Sun, 01/15/2023 - 10:29

#17

K6BZZ

Camera Latency

Thanks Chuck. The problem was the camera bandwidth. Too many features turned on. Went to lower resolution, lower frame rate, etc. and have low latency now. Camera is an Amcrest HD1080.

Amateur Radio Emergency Data Network

Menu SF

You are here

Acquisition of IP Address

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Acquisition of IP Address