Allowed IP addresses for ingestion

A location’s IP list determines which sources can send it logs. It does not control application access, which depends on user permissions.

Add an address

1. Open the location, then Manage in the IP address card.
2. Add the source IP address used to reach LogCentral.
3. Check that the address appears in the list.
4. Send a test message and confirm receipt.

An Owner or Member can edit this list. A Reader can view it.

IPv4 and IPv6 addresses are accepted individually. CIDR ranges are not accepted.

Which address should you use?

Behind a router with NAT, allow the public outgoing IP address, not the device’s private IP. The destination port directs logs to the correct location.

For a site with multiple Internet connections, allow the addresses of each connection in use. If a VPN or relay forwards logs, check which source IP actually reaches LogCentral.

Change or remove an address

Add the new address, verify receipt, then remove the one no longer used. The ingestion configuration may need to update before the change takes effect; confirm it with a test.

Removing the last allowed IP disables the location. Add a valid address and check that the location is enabled before testing again.

For a dynamic address, keep the list up to date. With a configured Meraki integration, WAN address synchronization can be managed by the integration; check its status before manually changing a synchronized address.

Logs still not arriving?

Check that the location is enabled, along with the outgoing IP, destination, port and protocol. Also check the log filter rules.

Audit logs help you find changes to the IP list. They are not a record of every rejected network connection. Send your first logs provides the complete test procedure.