-
Hi, I am very new to this, and it is a setup that is already in place. Basically, I need to add a new FWD node however i need to NAT the SO manger IP, this is fine, and I can add the forward node to the manager, but I noticed no logs were being forwarded. on inspection of the logs the file beat docker container was still pointing to the real IP of the SO manger which can't route. How do I update the docker container image so the filebeat uses the correct IP and can route |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
What logs are you trying to forward? The forwarding should all be done by the forward node itself without modification of the filebeat docker container. You successfully added the FWD node to the manager node and it shows up in the Grid dashboard? Your forward node should be pointing to an address it can reach.
Have you taken a look at the docs |
Beta Was this translation helpful? Give feedback.
-
Hi so this was actually an odd one as our manager was on a seperate network sending data behind a NAT IP on an ASA what we did was actually NAT on the docker interface as we couldnt amend the sls file as that would of broke our other forwarders: iptables -t nat -A PREROUTING -i docker0 -p tcp -d 10.5.X.X -j NETMAP --to 10.100.Y.Y |
Beta Was this translation helpful? Give feedback.
Hi so this was actually an odd one as our manager was on a seperate network sending data behind a NAT IP on an ASA what we did was actually NAT on the docker interface as we couldnt amend the sls file as that would of broke our other forwarders:
iptables -t nat -A PREROUTING -i docker0 -p tcp -d 10.5.X.X -j NETMAP --to 10.100.Y.Y