6:13 from manual - If you made manual changes directly to the /etc/network/interfaces file, you can apply them by running ifreload -a This will avoid rebooting pve as I understand
Wish I had seen this weeks or months ago; learned the hard way thru experimentation on some of this; learned other stuff however ; so not a loss. The experimentation was, uh, frustrating because not only had I added a new 4 port NIC, wasn't sure that it was working or not. Was tired of replugging things to move them at a switch; Now back to work.. Thanks for the video.
Awesome @MrPir84free.....experimenting and learning the hard way is always frustrating, but like you, I feel better for it afterwards...generally sticks that way :) Be sure to join the forums and share your experiences there and help others to pass along the knowledge too: www.virtualizationhowto.com/community
Personally I do this slightly different: create N bridges for all my VLANs and then bind each of them to port enp4s0.X. Then create N Linux VLANs enp4s0.X . I found this more readable to which VLAN my VM is connected to. Having said that - looking forward to see how we can use SDN introduced in recent version of Proxmox.
Thank you SO much for this video. I was stuck on getting into the web gui on my newly deployed ProxMox server due to needing to have the management IP address on a specific vlan. this was an extremely clear and straightforward tutorial. well done.
Just a note that may come in handy. For larger Xeon servers, such as xeon gold, we ran into a problem with VLANs being broken due to spectre and meltdown mitigation's. I had to disable them. While this may be fixed in Kernel 6.5, I had major production issues with 6.2.
When showing reconfigurations do not apply the reconfiguration by rebooting the host. Linux should not require a reboot to take configuration changes. If this were a production system you'd take it down for the time that's needed to do a reboot. Alternatively it might be better to show the specific proxmox configuration to reload the modified network configuration which should be much faster and almost immediate.
I'm still looking for someone on YT to cover the OpenVSwitch configuration in Proxmox. Everyone and their dog does videos on the linux networking, but no one does the OpenVSwitch networking which is suppose to be better. Why? I'm really curious to know?
Configuring OVS in Proxmox is very easy. Not sure about RU-vid tutorials but there are a few good websites that explain howto configure OVS. Just Google it.
sorry i'm confused here, how do i remote into the new vlan IP address if i don't already have a host on that subnet? seems like when i apply those changes in the interfaces file i'm going to lose access to my server all together
I want to see an updated video for VLAN management using the new SDN features with existing externally managed (UniFi) VLANs including tagging the host os
Hi i have a problem with configuration on my proxmox VE at the beginning of the installation i freshly install it and can't access the web GUI, i try to ping from another pc the IP address of the proxmox but nothing, get in the router i use and he doesn't see the proxmox too, so im 100% sure the problem is in the proxmox, now my question is how do i fix this i watch a lot of crap suggestions from changing my ip to rewriting the whole network/interface file nothing work can you help mi how proxmox is connecting to the internet wath i have to change DHCP IP or more.
Erm.. thanks but this puts the VM on the same Vlan as the management of the host. What if you want the management on say 10.0.0.x and different VLANs for your VMs perhaps 192.168.0.x and 192.168.1.x I cannot get that to work. Ping between VMs on the same VLAN works but none of the VMs can get to the firewall (which is on 10.0.0.x) and thus no external traffic.
If I make vmbr0 VLAN aware but don't set a VLAN tag in the network device net0 of a VM, will the latter act as a VLAN trunc so that i could use that VM as a docker host and putt the docker containers on different VLANs using 802.1q MAC VLANs in docker?
Brother i'd love to know your suggestion about building a small data center for a cloud computing service company running with Proxmox as a core system. Is it a good idea to run with proxmox as the core system? Thank you!
Hello, thank for this tutorial! Any idea how to add IP Pools in Promox? Or how to add automatically a next public ip to the next VM that will be created!
@eoeoeovideos thank you for the comment. Interesting question. I would like to learn more about your use case. Sign up on the forums and create a thread and let's discuss this in more detail: www.virtualizationhowto.com/community
Good information here. I am trying to configure bonds and vlans, in conjunction with bridges. Basically, I want to create 2 bonds, 1 for the mgmt, and the other for my vm's. I want to have the vlans 'aware' on the vm-network, and not the mgmt bond. I can create the bonds but am having issues creating or assigning the bridge to the vm-network. Any suggestions as to how I might be able to get this done? Thanks for your videos and suggestions you might have
@seapro4018 thank you for your comment! Hey hop over to the forums if you don't mind and sign up there to create a topic and we can discuss this in more detail: www.virtualizationhowto.com/community
Thanks! I have a question about DHCP. If I have an external DHCP server and configure the IP helper on the switch for the respective VLANs, after configuring the VLAN bridge on the host is the VM able to automatically obtain an IP address from the external DHCP?
I am having troubles with trying to get a VM in proxmox to communicate with a device outside of proxmox, separated by a L2 switch. I configured the connection from the proxmox server to the switch to be a trunk port and the connection from the switch to the external device to be an access port, accessing vlan 10. As vmbr0 is being used for something else, I created another linux bridge vmbr1, which is linked to a subinterface, ens33.10, of my physical network interface, ens33 (chatgpt told me that I could do this). I then followed your video to create a linux vlan, which creates vmbr0.10 subinterface which is then use by proxmox to communicate with the internal VM. After all this set up, the internal VM is still unable to communicate with the external VM. Any ideas?
@iluvpeanuts7919 Thank you for the comment! Do you mind creating a forum post under the Proxmox help forum? We can get into more detail to troubleshoot it there. Looking forward to diving in...here is a direct link to the proxmox help forum: www.virtualizationhowto.com/community/proxmox-help/
@jirkalottmann let me know if you have more questions, be sure to sign up on the VHT forums here: www.virtualizationhowto.com/community if you want to discuss anything in more detail
This did not work for me. It actually made it so I could no longer access my PVE at all. I triple checked everything and I did not get it wrong. I had to access from the console to put it back in order to gain access again.
@jefffontenot1782 thank you for the comment! Ping me on the forums if you need more detailed help in your environment: www.virtualizationhowto.com/community
@matthewbennett2844 yes you would need to make sure your switch ports uplinkng your proxmox host are configured as trunks that pass all VLANs or is tagged with all VLANs you have configured on your Linux VLANs in Proxmox. Let me know if you have any other questions. Sign up on the VHT forums and we can discuss in more detail www.virtualizationhowto.com/community
@@fbifido2vlan1 by default is the native vlan. Native vlan means the frames are untagged. So the command vlan 2-4094 is permitting all frames tagged within that range. If you changed it to say vlans 20, 40, & 60, but the network had vlans 10, 20, 30, 40, 50, & 60, the vswitch will block/drop any frames tag as 10, 30, & 50 while allowing vlans 20, 40, & 60. Thing of a trunk port as an access port, but instead of access vlan X it's native vlan X and any other vlan frames allowed on the trunk are tagged so the switch knows how to forward them
Showing error Nested Virtualization Using Windows 11 and VMWare workstation When power on Eve in VMWARE showing error VMware Workstation Error whie powering on: VMware Player does not support nested virtualization on this host. Module 'HV power on faied. Faled to start the virtual machine.
You really should learn a little about creating videos. All the cuts and the continuous auto focus are really distracting. With a little preparation, these should be easy to avoid.
@roylavender7241 Thank you for the comment and the constructive criticism. Always trying to get better, unfortunately video is not one of my strengths, but still learning :)
@@VirtualizationHowto The content was great. It really amazes me that Proxmox is still so un-polished when it comes to supporting something as simple as VLANs. I must admit I was dumbfounded that you had to jump through these hoops so I looked in a bunch of other places. Sure enough, this is what you need to do. I mean the CLI commands aren't difficult but come on, if you make a GUI for your product, you'd think it would support these basic functions. Especially after all this time. Anyway, thank you for the content.
Oh, and for your next video, just change the setting on your camera from continuous auto focus to single auto focus. Unless you are moving around a lot (which you aren't in videos like this), continuous auto focus is horrible. Its a simple, one-click, setting and makes the video look much more professional IMHO.
Get over it. He took out all the stuff that didn't need to be in the video so that we only got the important stuff. Who cares about the cuts. I care about useful content only. He shouldn't have to re-film it for a fringe group of picky Karens.
