Unfortunately, I didn't cover creating a Bridge when you're using IX's Apps ecosystem in the video Much like when using Sandboxes/Jails or Virtual Machines, you need to disable the apps before creating the Bridge intefrace, and when created, re-configure/re-enable the Apps. To do this: Go to Apps, then Settings -> Unset pool (this will disable apps) Make / Test / Save the changes (ie add the bridge etc) Then go back to Apps and reselect your pool. Your apps should re-deploy with your data intact. I tested this with NextCloud configured with ix-volumes for data.
If you ever remake this with the additional info about un-setting the apps pool, maybe mention that unchecking DHCP may result in having no DNS configured. I was struggling to figure out why I lost internet access from the host when following this guide.
do I have to set the network interface to the bridge in Apps->Settings->Advanced Settings? The problem after setting up the bridge is my jellyfin won't refresh its plugin catalogs. Edit: NVM, restarting truenas fixed it...
i've been looking into VMs in truenas through level1techs tutorial and i was so confused at the networking and bridge part due to inexperience. Your video helped me understand immediately and now i've finally set up my home server for jellyfin. thank you so much sir!
Wow, this video is a true masterpiece of technical expertise! Right from the get-go, it's evident that the creator knows their stuff inside out when it comes to TrueNAS. The way they effortlessly guide us through the intricacies of the system is nothing short of impressive. What's truly remarkable is how they break down complex concepts into digestible chunks, making it easy for viewers of all skill levels to follow along and learn. It's clear that the creator has a deep understanding of the subject matter and a knack for explaining it in a way that's both engaging and informative. Moreover, the attention to detail in this video is outstanding. From the clear and concise explanations to the seamless demonstrations, every aspect is meticulously crafted to ensure a smooth and enriching learning experience. I particularly appreciate how the creator goes the extra mile to anticipate common pitfalls and provide troubleshooting tips along the way. It's this level of thoroughness and foresight that sets this video apart and makes it a valuable resource for anyone looking to dive into the world of TrueNAS. Lastly, I have to give props to the creator for their excellent presentation skills. Their delivery is natural and engaging, keeping me hooked from start to finish. It's evident that they're not just knowledgeable about TrueNAS, but also passionate about sharing their expertise with others. This video is a testament to their dedication and talent, and I can't wait to see what other gems they have in store for us in the future!
This makes so much more sense!!! I am a networking newb and was pulling my hair out for 30 because my VM was connecting to my printers and everything else on the network but I couldn't communicate with the host to access my SMB share. Thanks for the video!
Thanks for this. If anyone is running into an issue when removing the IP address "#### is being consumed by Applications, please use a different node IP in applications configuration.", go to Apps, under settings choose Unset Pool, wait, then go make your IP changes, then come back when you're done and set the pool again.
Thanks ! Note : on VMware ESXi, "Promiscuous mode" needs to be enabled on the VM Network the VM is connected to. Maybe "MAC Address changes" and "Forged Transmits" too, but I don't know as they were already enabled for other test VMs. Without when you apply after creating the bridge, the host will be unreachable.
Great video! I think the basic setup would also apply to setting up a LAG (bond1) interface which would be the next common most confusing thing. I can also see that I did not do the setup for a LAG properly and your video showed me a key area where things get messed up. It would be a good topic for a video to set up a basic LAG.
Yes, and if you want a VM to connect back to the host, then you still need to add the bond to a bridge and have the VM using the bridge back to the host. Assuming you already have a bond network with a static IP, then remove the static IP from the bond network, and create the bridge, then add the bond interface, and set the static ip. test and save, then update your VMs etc to use the bridge. If you don't already have a bond/lagg then you will need to set a static IP on one of your interfaces... test, reconnect to static ip, then save, then you reset your two interfaces (the rewind button), then create the bond, add the two interfaces, and set the static ip... THEN test and save. and then if necessary, make the bridge as above.
A superb video, thank you. Clear & easy-to-follow instructions. The only issue I found was that (even though I'd deleted all Apps & VM's) I couldn't delete the static IP address from the bridge until I'd first created a 'dummy' vlan interface & assigned that to the Apps via "Apps - Settings - Advanced Settings". It then deleted fine. As a request for a future video, would you consider adding a guide to use vlans so that it's possible to have jails on different vlans? I think the process is to create a new vlan with the physical interface as the parent & then create a bridge to that vlan for use by the jail, but I'm a bit confused by it!
Perfect timing, running syncthing in my VM always results in WAN connection (ie slowww!), even after whitelisting local subnet in ufw an nord, but i think this is my problem. Thanks for the video stux!!
4:48 after I removed IP of my enp2s0 interfaces and add this IP to br0 new Interfaces like you, but when Test Change, i cant connect to this IP and over 60 second the change auto Revert and i can connect to this IP without any change, please help
Question! If, from my router, I assigne a static IP for my the trueNAS server, do we always nedd to force an IP in a bridge or leaving it to DHCP would work since the router is assigning a static IP. I'm asking because if I where to force an IP static in trueNAS witout reconfiguring my router to assigned a static IP, it would not connect me to my trueNAS. Thanks for sharing
The Ethernet interface and the bridge have different MAC addresses, thus the router sees them as different devices and hands out different IPs. Although you can do what you ask it’s very tricky to get right. If you tick the DHCP box on the bridge it will use DHCP to acquire a lease
Hi there, I followed the instructions you laid out in the video to create a bridge interface, and in the comments regarding unsetting the pool before the network changes, so I could implement jailmaker. Although after creating the bridge interface and being able to access the webUI, some of my apps were suddenly stuck in a deploying loop, with their logs stating they were unable to reach the internet. Not only that, but my Scale instance is no longer connecting to Github and is giving me an error saying the official charts are unreachable. After trying to troubleshoot some but getting no where, I deleted the bridge in reverse, but i'm still getting errors from trying to refresh the charts and from the same apps, so i'm stuck in this situation.
Check that you have a DNS server set in your network settings. I don’t call this out in the video, but I do do it. In some situations, when you disable DHCP the gateway and dns settings will become empty. They need to not be. The correct answer is normally to use your routers IP as gateway and dns server. Otherwise, I’d suggest that you ask on the TrueNAS forums where your question will get a wider audience
Great video! Do you know how can I do this for an app? I'm trying to setup music-assistant and everything looks correct but I get no sound from the speakers. Probably because it's still using the default k3s interface instead of the external one. Any thoughts? Thank you!
'192.168.0.21' is being consumed by Applications, please use a different node IP in applications configuration. is something im running into whenever trying to get to the step of deleting the alias to add it to the vSwitch, how do i get around this
Go to Apps, then Settings -> Unset pool (this will disable apps) Make / Test / Save the changes (ie add the bridge etc) Then go back to Apps and reselect your pool. Your apps should re-deploy with your data intact. I tested this with NextCloud configured with ix-volumes for data.
@@CaptStux This worked, I am on the curl "dockge.kuma.pet/compose.yaml?port=5001&stacksPath=%2Fopt%2Fstacks" --output compose.yaml step and getting 0curl(6) could not resolve host: dockge.kuma.pet issue. Have you encountered this
I wonder if that also works if k3s (apps) is configured on truenas? I want to migrate away from the k3s apps to jailmaker+docker but unless I have migrated my apps, k3s will still be running.
You need to unset your apps pool before making the changes, and then reselect it after making the changes, much like you need to shutdown/restart the VM/Jails. When I tested this with the TrueNAS NextCloud app and ix-volume for data, the original data was preserved. Pity I didn't cover it in the video :(
Set up your main interface with static IP by disabling DHCP and adding IP alias (use the same IP you are connected to for easy results) Test Changes and then Save them (important) Edit your main interface, remove the alias IP Don't click Test Changes Add a bridge, name it something like br0, select your main interface as a member and add the IP alias that you had on main interface Click Apply and then Test Changes after applying all this is faults back and ip is not assigned to br0
Fantastic video but when I save after removing the IP from the network adapter the IP is still shown unlike yours that is empty. and I cant get any success I'm sure I'm being stupid but any ideas where I'm going wrong ?
Hi i switched to a static IP which i was already using through reservation on my router. So i removed the reservation on the router then set the static ip saved and tested and could access the truenas via it then i went to remove the static ip as demonstrated tried to hit save but after hitting save i get a little red circle with a line through it when the mouse is held over the save button
@@tmarlow5 maybe try setting a different static ip... see if that works. if it does then switch back to the original one again if you still have issues you may be able to reset the interface (using the little rewind icon near the pencil) And if things still don't work, the final fall back is to do it through the system console with a screen/keyboard directly attached to your nas, where you can reset and configure the interfaces without using a network.
Assuming you already have a bond network with a static IP, then remove the static IP from the bond network, and create the bridge, then add the bond interface, and set the static ip. test and save, then update your VMs etc to use the bridge. If you don't already have a bond/lagg then you will need to set a static IP on one of your interfaces... test, reconnect to static ip, then save, then you reset your two interfaces (the rewind button) then create the bond, add the two interfaces, and set the static ip... THEN test and save. and then if necessary, make the bridge as above.
So when i try this, and goto remove the ip, its says "cannot remove 192.168.1.55 as it is being used by applications" (and in typical truenas fashion doesnt say which application). Is there a way around this besides deleting apps? all my apps an VM is stopped, i also stopped smp/nfs.
@@CaptStux cool, thanks stux, just to be clear, is that going into edit on each app an removing any association with that ip, then changing back, or is there another quicker way?
Go to Apps, then Settings -> Unset pool (this will disable apps) Make / Test / Save the changes (ie add the bridge etc) Then go back to Apps and reselect your pool. Your apps should re-deploy with your data intact.
I'm getting the following error: [EFAULT] error creating macvtap interface macvtap2@enp2s0 (00:a0:98:23:78:0d): Device or resource busy. when I try to start my VM. I must be doing something wrong.