Splunk Dev

Forwarding the logs from UF to Splunk instance on different networks

raghu_vedic
Path Finder

I installed splunk in one server and also enabled the receiver please check related urls

url - http://:{private ip address}8000

reciever - http://:{private ip address}9997

I installed universal forwarder in other server (different network too) when I add forwarder server with hostname, it is not connecting because it is taking public IP address instead of private IP address. please let me know, how to solve the problem to forward the logs from UF to splunk instance on different networks.

Tags (1)
0 Karma
1 Solution

woodcock
Esteemed Legend

Indexers receive EVERYTHING by default; there is no whitelisting. So if you have outputs.conf setup on your UF correctly (use IP Addresses), you should be good-to-go. If it doesn't work, check your standard network things (ACL, firewall, ports, SELinux, etc.).

View solution in original post

0 Karma

ephemeric
Contributor

Do not hardcode IP addresses in prod. In dev, sure, for testing. If you change your IPs once in prod it becomes unwieldy.

Use DNS. In your case: you haven't stated the hostname you're using so we assume it is colliding with the public DNS namespace.

Change your hostnames to a private namespace or if you must use FQDNs in the public namespace, put entries in `/etc/hosts`:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255	broadcasthost
::1             localhost
192.168.20.149  idx01.host.tld
192.168.20.148  idx02.host.tld
0 Karma

woodcock
Esteemed Legend

Indexers receive EVERYTHING by default; there is no whitelisting. So if you have outputs.conf setup on your UF correctly (use IP Addresses), you should be good-to-go. If it doesn't work, check your standard network things (ACL, firewall, ports, SELinux, etc.).

0 Karma

gcusello
SplunkTrust
SplunkTrust

hi raghu_vedic,
a silly question: Why you don't use IP address instead hostname in your forwarder's outputs.conf? so you haven't any DNS problem.
Bye.
Giuseppe

0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...