vlan howto

Hi,

I'm not sure I understood You correctly but after I manually typed all the settings (using the shell), they immediately appeared in www, under "System" tab. No reboot was necessary. I'm not sure about the stability nor the correctness of these steps, though.
 
Hello,

I will do some testing...

My gut feeling is that this will not survive a reboot without applying the config to the interfaces file manually.

...

As a thought. This shoud be easy to build into the inteface, without needing a reboot. Infact... pretty much essential! What also makes sense is to allow vlan config to be carried across to all member servers.

That would make the cluster a dream to use :)

Rob
 
My gut feeling is that this will not survive a reboot without applying the config to the interfaces file manually.

Rob

I just rebooted Hardware Node on which I've manually shell-typed above changes and they persisted. The entry in /etc/network/interfaces, /proc/net/vlan/config and brctl show are still showing eth0.100, vlan100 and vmbr1 bridged with eth0.100.

I assume it would be rather easy to implement automatic changes in network settings along the Cluster Hardware Nodes if there is no need to reboot the system.

The second thing is, it would be great to implement the function to configure a OpenVZ VE as the member of many VLANS, using the web interface. For instance, right now to create a DHCP server wth many veth interfaces, each in different vlan, you must manually edit /etc/vz/conf/xxx.conf file:

NETIF="ifname=eth0,bridge=vmbr0,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.0,host_mac=00:18:51:24:71:00;ifname=eth1,bridge=vmbr1,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.100,host_mac=00:18:51:24:71:10;ifname=eth2,bridge=vmbr2,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.200,host_mac=00:18:51:24:71:20;ifname=eth3,bridge=vmbr3,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.300,host_mac=00:18:51:24:71:30;ifname=eth4,bridge=vmbr4,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.400,host_mac=00:18:51:24:71:40;ifname=eth5,bridge=vmbr5,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.500,host_mac=00:18:51:24:71:50;ifname=eth6,bridge=vmbr6,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.600,host_mac=00:18:51:24:71:60;ifname=eth7,bridge=vmbr1,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.1,host_mac=00:18:51:24:71:01;ifname=eth8,bridge=vmbr1,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.2,host_mac=00:18:51:24:71:02;ifname=eth9,bridge=vmbr1,mac=26:37:FD:0A:7E:8B,host_ifname=veth102.3,host_mac=00:18:51:24:71:03"
 
Hi

I just re-read the commands you typed and realised that you actually edited the interfaces file. Of course it would then survive the reboot :)

I think thi is a workable solution. Now just to wait for the chaps at proxmox to build this all into the web interface! From what I can see of the development pace, I expect this will happen quite soon :)

Rob
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!