From: Daniel Tschlatscher <d.tschlatscher@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/2] fix #3719: gui: expose MTU option for containers in web UI
Date: Mon, 17 Oct 2022 15:56:31 +0200 [thread overview]
Message-ID: <20221017135632.569782-1-d.tschlatscher@proxmox.com> (raw)
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.tschlatscher@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
next reply other threads:[~2022-10-17 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 13:56 Daniel Tschlatscher [this message]
2022-10-17 13:56 ` [pve-devel] [PATCH manager 2/2] gui: reorder with advanced section Daniel Tschlatscher
2022-10-19 5:49 ` [pve-devel] [PATCH manager 1/2] fix #3719: gui: expose MTU option for containers in web UI Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017135632.569782-1-d.tschlatscher@proxmox.com \
--to=d.tschlatscher@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox