57HL&gXjw!
Dabbler
- Joined
- Mar 10, 2021
- Messages
- 10
All,
First of all, thank you in advance to anyone who is willing to help resolve some of these issues.
I am hoping someone will be able to help inform as to what is going wrong with my implementation.
TLDR: This is a new TrueNAS Core build installed on a Dell PowerEdge R730XD (full specs listed below). I have been successful in setting up the networking to get this TrueNAS server connected to the various networks it will be serving; however, I have been having profound difficulty in setting up bridge interfaces to use with Jails and Virtual Machines - whenever I configure a bridge (selecting the member interface and setting the IP (removing the IP from the member interface), I lose all networking on that interface. This system will have the necessity to run a small number of applications within the FreeBSD Jail system as well as a small handful of virtual machines. Unfortunately these issues I am experiencing have made leveraging these two critical features impossible.
Hardware:
Hardware upon which TrueNAS has been installed is a Dell PowerEdge 730XD with the following hardware:
The networks in question are as follows:
Management
Working Scenario:
Interfaces:
Network Configurations:
Default Gateway (IPv4): 192.168.1.1
Nameserver 1: 208.67.222.222
Nameserver 2: 208.67.220.220
Static Routes
Under the above-listed scenario everything is functioning as expected; however, the minute the bridge interfaces are configured, TrueNAS loses all connectivity to the network for which the bridge was created.
Broken Scenario:
NOTE: Please notice how when the bridge interfaces have been configured, the IP Address has been removed from the associated vlan interface and placed on the bridge. This has been done per FreeBSD bridge configuration standards.
Interfaces:
No changes to Network Configurations or Static Routes.
Under this "Broken Scenario" TrueNAS has lost all network connectivity to networks 10.1.0.0/22 (User) and 10.254.0.0/24 (Remote Access). After a great deal of research (including on this forum) I identified several recommendations of performing a system reboot following the configuration of a bridge interface... unfortunately this has not solved the problem.
I have confirmed the LACP (lagg0) is properly configured on the side of the switch and properly trunking each of the VLANs necessary.
After a full day of trying to resolve this issue, I am now at my wit's end. I am hoping someone here may be able to shed some additional light on what exactly may be going on here. Thanks again to anyone who can provide any ideas, guidance, or resolutions.
First of all, thank you in advance to anyone who is willing to help resolve some of these issues.
I am hoping someone will be able to help inform as to what is going wrong with my implementation.
TLDR: This is a new TrueNAS Core build installed on a Dell PowerEdge R730XD (full specs listed below). I have been successful in setting up the networking to get this TrueNAS server connected to the various networks it will be serving; however, I have been having profound difficulty in setting up bridge interfaces to use with Jails and Virtual Machines - whenever I configure a bridge (selecting the member interface and setting the IP (removing the IP from the member interface), I lose all networking on that interface. This system will have the necessity to run a small number of applications within the FreeBSD Jail system as well as a small handful of virtual machines. Unfortunately these issues I am experiencing have made leveraging these two critical features impossible.
Hardware:
Hardware upon which TrueNAS has been installed is a Dell PowerEdge 730XD with the following hardware:
- 2x Intel Xeon E5-2630's
- 96Gb RAM
- Intel 2P X520/2P I350 (Daughter Board)
- Intel X520-2 (PCI)
- PERC H730P Mini - in HBA Mode
- 2x 1100W PSU
The networks in question are as follows:
Management
- defined as 192.168.1.0/24
- VLAN ID: 1
- Gateway: 192.168.1.1
- defined as 172.16.33.0/24
- VLAN 33
- Gateway: 172.16.33.1
- defined as 10.254.0.0/24
- VLAN 254
- Gateway: 10.254.0.1
- defined as 10.1.0.0/22
- VLAN 10
- Gateway: 10.1.0.1
Working Scenario:
Interfaces:
Interface | Network | Configured IP Address |
igb0 | Management (192.168.1.0/24) | 192.168.1.20 |
igb1 | Currently Unused | n/a |
ix0 | Storage Network (172.16.33.0/24) | 172.16.33.20 |
ix1 | Member of lagg0 | n/a |
ix2 | Member of lagg0 | n/a |
ix3 | Currently Unused | n/a |
lagg0 | LACP Trunk from Switch | n/a |
vlan10 | User Network (10.1.0.0/22) | 10.1.0.20 |
vlan254 | Remote Access Network (10.254.0.0/24) | 10.254.0.20 |
Network Configurations:
Default Gateway (IPv4): 192.168.1.1
Nameserver 1: 208.67.222.222
Nameserver 2: 208.67.220.220
Static Routes
Destination | Gateway |
10.1.0.0/22 | 10.1.0.1 |
10.254.0.0/24 | 10.254.0.1 |
172.16.33.0/24 | 172.16.33.1 |
Under the above-listed scenario everything is functioning as expected; however, the minute the bridge interfaces are configured, TrueNAS loses all connectivity to the network for which the bridge was created.
Broken Scenario:
NOTE: Please notice how when the bridge interfaces have been configured, the IP Address has been removed from the associated vlan interface and placed on the bridge. This has been done per FreeBSD bridge configuration standards.
Interfaces:
Interface | Network | IP Address | Changes |
igb0 | Management (192.168.1.0/24) | 192.168.1.20 | None |
igb1 | Current Unused | n/a | None |
ix0 | Storage Network (172.16.33.0/24) | 172.16.33.20 | None |
ix1 | Member of lagg0 | n/a | None |
ix2 | Member of lagg0 | n/a | None |
ix3 | Current Unused | n/a | None |
lagg0 | LACP Trunk from Switch | n/a | None |
vlan10 | User Network (10.1.0.0/22) | n/a - Set on Bridge Interface | IP Removed from Interface |
vlan254 | Remote Access Network (10.254.0.0/24) | n/a - Set on Bridge Interface | IP Removed from Interface |
bridge10 | User Network (10.1.0.0/22) | 10.1.0.20 | Member vlan10 Added & IP Set |
bridge254 | Remote Access Network (10.254.0.0/24) | 10.254.0.20 | Member vlan254 Added & IP Set |
No changes to Network Configurations or Static Routes.
Under this "Broken Scenario" TrueNAS has lost all network connectivity to networks 10.1.0.0/22 (User) and 10.254.0.0/24 (Remote Access). After a great deal of research (including on this forum) I identified several recommendations of performing a system reboot following the configuration of a bridge interface... unfortunately this has not solved the problem.
I have confirmed the LACP (lagg0) is properly configured on the side of the switch and properly trunking each of the VLANs necessary.
After a full day of trying to resolve this issue, I am now at my wit's end. I am hoping someone here may be able to shed some additional light on what exactly may be going on here. Thanks again to anyone who can provide any ideas, guidance, or resolutions.