You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a guide for adding an external Security Onion sensor node to an internal manager node through NAT?
I am deploying a Security Onion Distributed architecture within an internal network environment with no Internet access.
I'm trying to add a sensor node located on an external network to a manager node behind NAT (internal network). However, when I attempt to download the repository or connect to the manager via its NAT IP, the connection gets redirected to the manager's internal IP, which is not accessible from the external sensor.
Is there any documentation or recommended approach to handle this NAT scenario properly?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a guide for adding an external Security Onion sensor node to an internal manager node through NAT?
I am deploying a Security Onion Distributed architecture within an internal network environment with no Internet access.
I'm trying to add a sensor node located on an external network to a manager node behind NAT (internal network). However, when I attempt to download the repository or connect to the manager via its NAT IP, the connection gets redirected to the manager's internal IP, which is not accessible from the external sensor.
Is there any documentation or recommended approach to handle this NAT scenario properly?

Beta Was this translation helpful? Give feedback.
All reactions