Interface Issue on Setup with Virtualbox

[eli0tc]

Hello,

I'm attempting to install v2.3.21 as a VM on a Windows 10 host running Virtualbox. I am running into the below error upon installation:

The IP being routed by Linux is not the IP address assigned to the management interface (enp0s3).
This is not a supported configuration, please remediate and rerun.

I configured the interfaces via Virtualbox as below:

The problem apparently comes from the fact that the route set using the monitor interface have a lower metric:

Any idea on how to resolve this? Is changing the line concerned in the installation script to ignore this enough or would it lead to other complications later on?

[dougburks]

Try removing the IP address from your sniffing interface.

[eli0tc]

I could do that with DHCP configuration on my pfSense acting as gateway/DHCP server. I no longer get this error message but now I get stuck at the screen "Running initial configuration step". I let it run for a few hours, still 0%.

[dougburks]

Is there some reason why you need a static/DHCP IP address on your sniffing interface? Most folks configure their sniffing interface to have no IP address whatsoever (no static, no DHCP).

[eli0tc]

Not really. Looks like the setup process is trying to assign an IP to both interfaces (I managed to go beyond the error message by specifying my DHCP server to ignore request from sniffing interface MAC address). Also I could finished the installation by doing a fresh install.

EDIT: After more testing on several new fresh installations (using both static and DHCP for the management interface) it is working as expected (no IP assigned for the sniffing interface). Problem was from my side obviously.

[jpl33]

IF you can't get along without an IP on your sniffing interface:
your routing table has two default GW, because of the IP on your sniffing interface (enp0s8).
try deleting the default gw attached to enp0s8. since both your interface are on the same subnet, it won't hurt your routing.
Also your sniffing interface has a lower metric than your management interface, so your traffic is routed through your sniffing interface.
try changing the interface metric to a higher value than the management.

[ivanrdrgz]

Hi! I don't know if it is too late to write in this post.

I have a similar problem. Instead of VirtualBox I am using ESXi from vSphere Client. I am creating an enterprise network to do security testing with a SecurityOnion machine (for a university job). My SecurityOnion machine is connected to a pfSense firewall through the management interface. The gateway for Security Onion is 192.168.30.1 and its IP address is 192.168.30.10/24. I am sure that the network itself is well configured and that the IP addresses are well given. The sniffing interface is connected to a vSwitch (in ESXi I can't create an interface without connecting it to a vSwitch), which has no other machines connected to it. The sniffing interface also has no IP address. I have seen that configuring DHCP in pfSense solves this, but I don't want dynamic address assignment at all. Do you have any idea how to solve this?

Thank you very much in advance and best regards.

[ivanrdrgz]

I assumed you know what the error is but maybe I should have not. The error is:
The IP being routed by Linux is not the IP address assigned to the management network interface (ens160). This is not a supported configuration, please remediate and rerun setup".
I'm using an Standalone config, and this error appears right after giving the IP address to the management NIC.

Thanks again!

[dougburks]

@ivanrdrgz From #1720:

Start a new discussion instead of replying to somebody else's discussion
Please search to see if you can find similar discussions that may help you. However, in order to avoid confusion, please do NOT reply to somebody else's discussion with your own issue. Instead, please start a new discussion and in that new discussion you can provide a hyperlink to the related discussion.