10:22 Just noticed that 172.12.*.* is not a private IP range. Only 172.16+.*.* are in the private IP range. Meaning the after 172, the second octet needs to be 16 or greater.
You are right, but in practice this has absolutely no effect as it’s a fully NAT’d network. You can really use anything you want :) great catch though! If theres anything else you’d like to see in a follow up video, just let me know!
Wouldn’t it have an effect if you assigned an IP on the inside that was also in use on the Internet? So if 172.12.12.12 was a web server on the Internet and one of your VM’s was also assigned 172.12.12.12. How would you get there?
I'm new to Proxmox stuff so pls tell me - if I want to set up SDN on my node and my 'real' local network is 172.12.12.X (I mean in this network work all my computers / prinetrs etc.) then do I need to create subnet ( like here 10:50 ) 172.12.12.0/24 also?
If you are only planning on having a single network that is bridged directly to your LAN, it really doesn't make sense to use SDN. You should just use the standard bridge tied directly to the physical network interface from your Proxmox VE server that connects back to your switching. SDN is beneficial if you have multiple VLANs you wish to create for different VMs/containers or if you want to create a NAT'd network that can get out to the internet but nothing can get in to the devices on it, etc.
Remember that it won't work automatically if using Proxmox Firewall. This is because the dhcp request is blocked by the firewall. The official wiki page "Setup Simple Zone With SNAT and DHCP" shows how to solve the problem.
Trying to run Proxmox is really janky to be honest, when your using TrueNAS Scale for storage. iSCSI barely works and NFS seems to be the only solution but that is horrible slow, even with 10G and SATA SSDs.
Ah ah, I have that exact same problem witht he same setup. ISCSI barely works for me too. I can configure it, but only one node of the cluster sees the iscsi lun shares, the others ignores it whatever I do. It's infuriating.
@@mitcHELLOworld Yeah, I found out where was the "problem". It's config and shitty documentation. TrueNas makes you declare your Zvol as extents... and then you had to manually declare those extents as Associated Targets... it was trial and error, but it's truly bad UI design and bad documentation.
Yes, part 2 please, really interesting
Coming soon!
Thank you! Please Provide the Part 2. you explain it very well
Coming soon!
@@45Drives Still coming soon?
Software Defined Routing .. yes please!
Is part 2 still coming? We really need it guys!
Part 2 please 😀
Looking forward to part 2.
Coming soon!
10:22 Just noticed that 172.12.*.* is not a private IP range. Only 172.16+.*.* are in the private IP range. Meaning the after 172, the second octet needs to be 16 or greater.
172.16.0.0/12. From 172.16.0.0 to 172.31.255.255
You are right, but in practice this has absolutely no effect as it’s a fully NAT’d network. You can really use anything you want :) great catch though! If theres anything else you’d like to see in a follow up video, just let me know!
Wouldn’t it have an effect if you assigned an IP on the inside that was also in use on the Internet? So if 172.12.12.12 was a web server on the Internet and one of your VM’s was also assigned 172.12.12.12. How would you get there?
I want to know a little more about OVS
Great content! Is part two still on the docket? I've been eagerly waiting to see if I want to go this route (pun intended)
Yes, part II is in the works!
I'm new to Proxmox stuff so pls tell me - if I want to set up SDN on my node and my 'real' local network is 172.12.12.X (I mean in this network work all my computers / prinetrs etc.) then do I need to create subnet ( like here 10:50 ) 172.12.12.0/24 also?
If you are only planning on having a single network that is bridged directly to your LAN, it really doesn't make sense to use SDN. You should just use the standard bridge tied directly to the physical network interface from your Proxmox VE server that connects back to your switching.
SDN is beneficial if you have multiple VLANs you wish to create for different VMs/containers or if you want to create a NAT'd network that can get out to the internet but nothing can get in to the devices on it, etc.
@14:40 - why can't it show a drop-down list of all your current bridge?
Remember that it won't work automatically if using Proxmox Firewall.
This is because the dhcp request is blocked by the firewall. The official wiki page "Setup Simple Zone With SNAT and DHCP" shows how to solve the problem.
Can you please add the link to "45 home lab" channel in the description? I found it to be: www.youtube.com/@45HomeLab
@15:42 - does this mean we can create VLAN in any ZONE ????
- can we create VALN in Simple, VLAN, QinQ, VXLAN, EVPN Zones ????
Plz part 2 🎉
give us a tech tip on bench pressing, holy guns
Haha appreciate it man. Have a cpl bench pressing videos on my channel under shorts actually 😅
@@mitcHELLOworld 335 holy crap
We'll commence internal talks on this immediately! 😅💪
Part 2 please
Trying to run Proxmox is really janky to be honest, when your using TrueNAS Scale for storage. iSCSI barely works and NFS seems to be the only solution but that is horrible slow, even with 10G and SATA SSDs.
Been running on iscsi for the last four years with no problem whatsoever.. what problems did you face?
I have been running Proxmox VE on 5 servers with TrueNAS Scale for storage for years now and it has been reliable and performant.
Ah ah, I have that exact same problem witht he same setup. ISCSI barely works for me too. I can configure it, but only one node of the cluster sees the iscsi lun shares, the others ignores it whatever I do. It's infuriating.
@@floriantthebault521sounds like you don’t have persistent reservations configured or setup properly.
@@mitcHELLOworld Yeah, I found out where was the "problem". It's config and shitty documentation. TrueNas makes you declare your Zvol as extents... and then you had to manually declare those extents as Associated Targets... it was trial and error, but it's truly bad UI design and bad documentation.