-
Version2.4.110 Installation MethodSecurity Onion ISO image Descriptionconfiguration Installation TypeEval Locationon-prem with Internet access Hardware SpecsMeets minimum requirements CPU4 RAM12288 Storage for /69.2 Storage for /nsm133.7 Network Traffic Collectionspan port Network Traffic Speeds1Gbps to 10Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailHi everyone, I need some help setting up Security Onion in VMware Workstation Pro for a project. I know this isn’t strictly a Security Onion issue, but I’m struggling with configuring the interfaces properly and could really use some guidance. Here’s my setup: All 3 VMs are on the same NAT subnet. My goal is for the sniffing interface in Security Onion to monitor traffic between the Kali and Metasploitable VMs (e.g., attack traffic) and generate alerts. Unfortunately, I’m not getting any alerts, and it seems the sniffing interface isn’t capturing the traffic. Additional Details:
This leads me to believe that it’s not a Security Onion problem but a misconfiguration in VMware or the network interfaces. Main Issues:
I know the issue is likely with the VMware networking configuration rather than Security Onion itself, but I’d greatly appreciate any advice or guidance on setting up the interfaces to enable proper traffic monitoring. This is for a project, and I’m running out of time, any help would mean a lot! Thank you in advance! Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey AB00-sys, Have you tried putting the Kali and Metasploitable VM on a host-only network? If you need to, you can give a secondary NIC to the Kali box for NAT. |
Beta Was this translation helpful? Give feedback.
Hey AB00-sys,
Have you tried putting the Kali and Metasploitable VM on a host-only network? If you need to, you can give a secondary NIC to the Kali box for NAT.
Hope this helps.