I have TrueNAS on hardware with 3 nics, I bonded them together (named bond01). I then created a bridge network for instances (named br01). Neither of those use MACVLAN that I can see.
The networking is working, it’s getting an IP on my actual network.
However I cannot ping the host. I know that is a limit of MACVLAN, but as I said I do not think it’s using that. Clearly it is? Not overly familiar with TrueNAS networking, hoping for suggestions.
Thanks!
Are you using LACP for the bond? Does your switch support that? Also the number of links in an LACP bundle must be a power of 2.
I am using LACP, yes, I have a Ubiquiti us-48-500w which does support it.
You think that is causing the issues because it’s not a power of 2? TrueNAS has been running like this for months, I just added the bridge today for instances. And again they work on the bridge and are getting the correct IP.
Edit, I looked. Its recommended to use LACP in power of two but not required. I did notice that when I went to “move” the IP address from the bond to the bridge, it did not “remove” it from the bond. Watching several video, after adding the alias it did not remove it from the bond. I am wondering if it’s because it’s not static, I have a reservation.
Logged into UNIFI console. That bridge was causing some errors. Once I deleted the bridge, the errors stopped.
Sorry, any suggestions to allow the instances to get an IP from the network, not a NAT from TrueNAS?
At least in FreeBSD/TN CORE if you create a bridge you must move the IP address of the host system from the physical member interface - the bond in your case - to the bridge.
I do not know for sure how Linux/TN CE behaves in that regard.
Any VLANs in the mix?
No VLANS. I think it might be that DHCP is enabled on the bond. I think I have to remove DHCP and move the IP as an alias on the bridge? I am going to try that and hope for the best!
This worked! I was just being an id10t. By bad, thanks for the help!
