Concern:
Certain IP addresses are not usable, resulting in devices not being found due to errors in JetAdvice Edge log details.

Error:
"SendToAsync: Socket Exception AccessDenied Permission denied : Permission denied at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.SendTo(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint remoteEP) at System.Net.Sockets.UdpClient.Send(Byte[] dgram, Int32 bytes, IPEndPoint endPoint) at EF.Snmp.Client.Internal.UdpSenderFactory.UdpSender.fDWNu0pchc(UdpSendRequest ) at EF.Snmp.Client.Internal.UdpSenderFactory.UdpSender.SendToAsync(UdpSendRequest request, CancellationToken ct)"

Reason:
Check the subnet address of the Edge Connector. One of the IPv4 ranges, IPv4 addresses or hostnames resolves to an IPv4 address which is defined as either a network address or a broadcast address for that subnet (i.e. it is not a valid address), and Linux will prevent packets from being sent to that address without elevated permissions

• e.g. Edge IPv4 address is 10.1.2.25 with a subnet of 255.255.255.128
  If a range of 10.1.2.1-254 is added, the error will be thrown when Edge attempts to connect to 10.1.2.127 (Broadcast address) and 10.1.2.128 (Network address)
  
  The 2 possible /25 networks for 10.1.2.* are
  Network Address Usable Range Broadcast Address
  10.1.2.0         10.1.2.1-10.1.2.126 10.1.2.127
  10.1.2.128 10.1.2.129-10.1.2.254 10.1.2.255

Fix:
In this case, split the IPv4 range depending on the subnet
10.1.2.1-10.1.2.126
10.1.2.129-10.1.2.254

or remove the individual IPv4 address or hostname that resolves to that address