SOLVED When trying to add bridge network interface, "The network 192.168.100.0/24 is already in use by another interface."

[Kasazn]

Hi all,

As per title, and also using guide from official TrueNAS documentation:

https://www.truenas.com/docs/scale/scaleuireference/virtualization/accessingnasfromvm/

Running latest TN build: TrueNAS-SCALE-22.02.2, server specifications as per my signature.

Any ideas? Need help.

 

[sretalla]

Have you removed the IP from the NIC already?

 

[Kasazn]

Have you removed the IP from the NIC already?

Do I do this first? Because I have static IP set and DHCP disabled.

Then I proceed to create the bridge connection?

 

[Samuel Tai]

You've got a chicken & egg problem, in that you're trying to configure the bridge from one of its members, and to transfer the IP which you're using to access the UI from the member NIC to the bridge. You'll need to temporarily use a different NIC with a different subnet to complete the bridge configuration.

 

[sretalla]

You'll need to temporarily use a different NIC with a different subnet to complete the bridge configuration.

I don't think so... you can remove the IP from the NIC (but don't test the settings), then set it on the bridge and then test. (and don't forget to come back and save within 60 seconds to make it stick like that).

 

[Kasazn]

I am a bit concerned about losing connection to the WebUI. I can reset the NIC to use my current IP (192.168.100.100/24 with Gateway 192.168.100.1) through the console right? I'd have to connect a monitor, mouse and keyboard to my server if things go south.

 

[sretalla]

Worst-case, you can always fix it from a locally attached console KVM. I did mine (3 of them) from the GUI.

 

[SnoppyFloppy]

Do I do this first? Because I have static IP set and DHCP disabled.

Then I proceed to create the bridge connection?

Yes you have to remove the IP from the physical NIC before you try to assign it to the Bridge interface, and no you won't lose the connection to the server by doing that.

You'll need to temporarily use a different NIC with a different subnet to complete the bridge configuration.

You definitely don't need to do that.

 

[Kasazn]

Success! Tried as per official guide.

- Remove IP from physical NIC
- Do not test changes
- Add new bridge connection attaching to existing NIC, in my case I cannot enable DHCP, it will just fail.
- Just add static IP same as phyiscal NIC.
- Test changes.

Tried a few times before this becomes a success. It fails from time to time. Your mileage will vary.

EDIT: It seems that my VM has full access to all my shared folders and datasets when I just limited it to my "vmshare" credential to a specific dataset. Weird.

 

[SnoppyFloppy]

Success! Tried as per official guide.

- Remove IP from physical NIC
- Do not test changes
- Add new bridge connection attaching to existing NIC, in my case I cannot enable DHCP, it will just fail.
- Just add static IP same as phyiscal NIC.
- Test changes.

Tried a few times before this becomes a success. It fails from time to time. Your mileage will vary.

EDIT: It seems that my VM has full access to all my shared folders and datasets when I just limited it to my "vmshare" credential to a specific dataset. Weird.

Yeah I've had to try it a few times before it succeeded as well ... on an earlier release though.

I would argue against putting a server on DHCP either way. My rule of thumb is that serving something, be it apps, network storage, DNS, etc., allays has a fixed IP configured hoth on the host and reserved on the router.