Jail connectivity issue

[victort]

The VLAN tag is set to 100 in the router's interface, yes.
Yes, the bridge does have the VLAN as its sole member.

Should DHCP be enabled on the bridge or the VLAN interface? It is currently enabled on the Bridge interface.

Bridge.

If it doesn’t get an IP, something else is wrong as I just ran these exact steps on my SCALE machine.

 

[djdwosk97]

Bridge.

If it doesn’t get an IP, something else is wrong as I just ran these exact steps on my SCALE machine.

Could an IPMI configuration (with DHCP enabled) be a factor?

 

[Patrick M. Hausen]

Should DHCP be enabled on the bridge or the VLAN interface? It is currently enabled on the Bridge interface.

Does the NAS host itself need to communicate in that VLAN? If not, no DHCP or static IP configuration necessary. It's all layer 2 to connect your jails.

If the NAS needs an IP address in that network, the important point - repeating myself - is that the IP address must be on the bridge interface and on the bridge interface only.

If no VLAN is involved but simply a dedicated NIC without IP address but with jails and/or VMs, it might be necessary to put "up" into the physical interface's "options" field.

HTH,
Patrick

 

[djdwosk97]

Does the NAS host itself need to communicate in that VLAN? If not, no DHCP or static IP configuration necessary. It's all layer 2 to connect your jails.

If the NAS needs an IP address in that network, the important point - repeating myself - is that the IP address must be on the bridge interface and on the bridge interface only.

If no VLAN is involved but simply a dedicated NIC without IP address but with jails and/or VMs, it might be necessary to put "up" into the physical interface's "options" field.

HTH,
Patrick

I want to place the NAS itself on VLAN100 along with a VM (which hosts the TP Link Omada Software Controller). The Plex jail would either be on VLAN100 or VLAN101 -- but VLAN100 would be fine for now. The Omada software does NOT let me disable VLAN1 on the router's ports, so the ports carry VLAN1 and VLAN100.

 

[djdwosk97]

Bridge.

If it doesn’t get an IP, something else is wrong as I just ran these exact steps on my SCALE machine.

Does the NAS host itself need to communicate in that VLAN? If not, no DHCP or static IP configuration necessary. It's all layer 2 to connect your jails.

If the NAS needs an IP address in that network, the important point - repeating myself - is that the IP address must be on the bridge interface and on the bridge interface only.

If no VLAN is involved but simply a dedicated NIC without IP address but with jails and/or VMs, it might be necessary to put "up" into the physical interface's "options" field.

HTH,
Patrick

Perhaps this is related .... I'm looking at the client list in my router's interface and I see that TrueNAS is on 10.0.100.52, but the Network is still listed as "LAN" (default VLAN1) as opposed to VLAN100. I can't ping this IP address.

 

[victort]

I want to place the NAS itself on VLAN100 along with a VM (which hosts the TP Link Omada Software Controller). The Plex jail would either be on VLAN100 or VLAN101 -- but VLAN100 would be fine for now. The Omada software does NOT let me disable VLAN1 on the router's ports, so the ports carry VLAN1 and VLAN100.

I think VLAN1 is the default tag for LAN traffic so it makes sense why it wouldn’t allow you to disable it.

 

[djdwosk97]

I think VLAN1 is the default tag for LAN traffic so it makes sense why it wouldn’t allow you to disable it.

Yeah, it is the default.


I'm not sure if this is related or if it's due to the bridge's IP address being set as 0.0.0.0/8, but when I try to "Test Changes", I'm seeing the following error:

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 138, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1213, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 975, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/network.py", line 757, in commit
await self.sync()
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/network.py", line 1845, in sync
await self.middleware.call('interface.bridge_setup', bridge)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1256, in call
return await self._call(
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1224, in _call
return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1128, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/interface/bridge.py", line 57, in bridge_setup
iface.add_member(member)
File "netif.pyx", line 1211, in netif.BridgeInterface.add_member
File "netif.pyx", line 1229, in netif.BridgeInterface.bridge_cmd
OSError: [Errno 16] Device busy

 

[djdwosk97]

I was also able to switch IPMI to the new VLAN with no issue under Network > IPMI with a static IP and a manually set default gateway:

Oct 1 16:54:14 freenas kernel: arp: 00:25:90:d8:5c:c5 is using my IP address 10.0.100.2 on bridge100!
Oct 1 16:55:13 freenas kernel[1048]: Last message 'arp: MAC' repeated 1 times, suppressed by syslog-ng on freenas.local

Might I just need to update the default gateway in Network > Global Configuration?

 

[victort]

Might I just need to update the default gateway in Network > Global Configuration?

Possibly. Give that a try. It will have to be the VLAN100 gateway.

 

[djdwosk97]

Possibly. Give that a try. It will have to be the VLAN100 gateway.

How would I go about resetting the default gateway from the server itself -- in case this doesn't work and stops me from getting to the web GUI?

 

[victort]

How would I go about resetting the default gateway from the server itself -- in case this doesn't work and stops me from getting to the web GUI?

You would have to have physical access to the server. You can do it if you plug in a monitor and keyboard.

But thats why you have the "Test" option...

 

[djdwosk97]

You would have to have physical access to the server. You can do it if you plug in a monitor and keyboard.

But thats why you have the "Test" option...

There is no test option in the Global Configuration pane. But I do have physical access.

 

[victort]

There is no test option in the Global Configuration pane. But I do have physical access.

My bad.

You should still be able to access the GUI even with a wrong gateway configured. I could be wrong, but my understanding is that the gateway is used for outgoing connections, not incoming.

 

[djdwosk97]

My bad.

You should still be able to access the GUI even with a wrong gateway configured. I could be wrong, but my understanding is that the gateway is used for outgoing connections, not incoming.

Same 0.0.0.0/8 IP address and device busy error.

 

[djdwosk97]

TrueNAS seems to be doing something weird where it's taking down my whole internet when it restarts (can't even connect to wifi). I can only connect to WIFI as soon as the server shuts down. Could there be some setting that's causing a loop between the two NICs that's overwhelming the router (my best guess as to why it booting up and spitting out a bunch of ARP messages and ipmi kcs messages causes the network to fail). I did notice that DHCP was enabled on both interfaces. Could that be the cause?

EDIT: It finished booting up a second time. This time I disconnected the second ethernet cable and I was able to add a VLAN and bridge interface. DHCP is still on the physical interface and the physical interface still has an IP address on VLAN1, but now the bridge has an IP on VLAN100.

 

[djdwosk97]

My bad.

You should still be able to access the GUI even with a wrong gateway configured. I could be wrong, but my understanding is that the gateway is used for outgoing connections, not incoming.

My default nameserver / gateway is at VLAN100.

I have a physical interface (with DHCP enabled) on VLAN1 (with an IP address).
I created a VLAN interface and then a bridge interface with a static IP address (10.0.100.3 -- yay!?).

I attempted to ping the bridge's static IP address and I get no response. I attempted to disable DHCP on the physical interface (and its IP address goes away) and enable DHCP on the bridge interface (it has a 10.0.100.3 IP address, which is outside of the DHCP assignment range), and I still can't ping the bridge IP address.

 

[victort]

DHCP should be turned off for all interfaces if you are using a static IP. Try turning it off on all of them, then turning it on for only the bridge, and see if it gives an IP.

 

[djdwosk97]

DHCP should be turned off for all interfaces if you are using a static IP. Try turning it off on all of them.

I turned off DHCP on all interfaces, but I still couldn't ping the bridge IP and I couldn't reach the web GUI with the original physical interface IP address or the bridge IP interface.

 

[victort]

Can you share screenshots of your interfaces?

 

[djdwosk97]

Can you share screenshots of your interfaces?