Networking Issue when Configuring Bridge Interfaces

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:
  • 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
Network Information:
The networks in question are as follows:
Management
  • defined as 192.168.1.0/24
  • VLAN ID: 1
  • Gateway: 192.168.1.1
Storage
  • defined as 172.16.33.0/24
  • VLAN 33
  • Gateway: 172.16.33.1
Remote Access
  • defined as 10.254.0.0/24
  • VLAN 254
  • Gateway: 10.254.0.1
User
  • defined as 10.1.0.0/22
  • VLAN 10
  • Gateway: 10.1.0.1
Digging in deeper... Here is the information regarding what is and is not working...

Working Scenario:
Interfaces:
InterfaceNetworkConfigured IP Address
igb0Management (192.168.1.0/24)192.168.1.20
igb1Currently Unusedn/a
ix0Storage Network (172.16.33.0/24)172.16.33.20
ix1Member of lagg0n/a
ix2Member of lagg0n/a
ix3Currently Unusedn/a
lagg0LACP Trunk from Switchn/a
vlan10User Network (10.1.0.0/22)10.1.0.20
vlan254Remote 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
DestinationGateway
10.1.0.0/2210.1.0.1
10.254.0.0/2410.254.0.1
172.16.33.0/24172.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:
InterfaceNetworkIP AddressChanges
igb0Management (192.168.1.0/24)192.168.1.20None
igb1Current Unusedn/aNone
ix0Storage Network (172.16.33.0/24)172.16.33.20None
ix1Member of lagg0n/aNone
ix2Member of lagg0n/aNone
ix3Current Unusedn/aNone
lagg0LACP Trunk from Switchn/aNone
vlan10User Network (10.1.0.0/22)n/a - Set on Bridge InterfaceIP Removed from Interface
vlan254Remote Access Network (10.254.0.0/24)n/a - Set on Bridge InterfaceIP Removed from Interface
bridge10User Network (10.1.0.0/22)10.1.0.20Member vlan10 Added & IP Set
bridge254Remote Access Network (10.254.0.0/24)10.254.0.20Member 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.
 

57HL&gXjw!

Dabbler
Joined
Mar 10, 2021
Messages
10
Was just testing some more and I have some more information...

Just now having configured bridge10 (vlan10->lagg0) again, I see I am no longer able to reach ANY network other than the management network on 192.168.1.0/24. When attempting to ping anything within either of these networks from TrueNAS, I receive ping: sendto: invalid argument
 
Top