The option to set the mtu parameter for lxc containers already exists
in the backend. It only had to be exposed in the web UI as well.
Signed-off-by: Daniel Tschlatscher <d.tschlatsc...@proxmox.com>
---
www/manager6/lxc/Network.js | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/www/manager6/lxc/Network.js b/www/manager6/lxc/Network.js
index 7b6437c5..d6a35a49 100644
--- a/www/manager6/lxc/Network.js
+++ b/www/manager6/lxc/Network.js
@@ -138,6 +138,14 @@ Ext.define('PVE.lxc.NetworkInputPanel', {
name: 'firewall',
value: cdata.firewall,
},
+ {
+ xtype: 'proxmoxintegerfield',
+ fieldLabel: gettext('MTU'),
+ name: 'mtu',
+ value: cdata.mtu,
+ minValue: 64,
+ maxValue: 65535,
+ },
];
let dhcp4 = cdata.ip === 'dhcp';
@@ -519,6 +527,11 @@ Ext.define('PVE.lxc.NetworkView', {
}
},
},
+ {
+ header: gettext('MTU'),
+ width: 80,
+ dataIndex: 'mtu',
+ },
],
listeners: {
activate: me.load,
@@ -543,6 +556,7 @@ Ext.define('PVE.lxc.NetworkView', {
'gw6',
'tag',
'firewall',
+ 'mtu',
],
});
});
--
2.30.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
