[pve-devel] [PATCH pve-manager] NetworkEdit: allow setting 'mtu' option for guest network devices

[Dylan Whyte]

Hi,

Tested on Linux (Fedora 32 & Debian 11) and Windows 2019 server, and all 
seems to work.

Best regards,

Dylan


On 2/7/22 13:18, Oguz Bektas wrote:
> we already have the 'mtu' option inside the API, so we can just expose
> that option inside the 'Advanced' menu for guest network interfaces.
>
> Signed-off-by: Oguz Bektas <o.bektas at proxmox.com>
> ---
>   www/manager6/qemu/NetworkEdit.js | 9 +++++++++
>   1 file changed, 9 insertions(+)
>
> diff --git a/www/manager6/qemu/NetworkEdit.js b/www/manager6/qemu/NetworkEdit.js
> index b39cffdc..4ce7e7a2 100644
> --- a/www/manager6/qemu/NetworkEdit.js
> +++ b/www/manager6/qemu/NetworkEdit.js
> @@ -19,6 +19,7 @@ Ext.define('PVE.qemu.NetworkInputPanel', {
>   	me.network.macaddr = values.macaddr;
>   	me.network.disconnect = values.disconnect;
>   	me.network.queues = values.queues;
> +	me.network.mtu = values.mtu;
>   
>   	if (values.rate) {
>   	    me.network.rate = values.rate;
> @@ -112,6 +113,7 @@ Ext.define('PVE.qemu.NetworkInputPanel', {
>   			    'macaddr',
>   			    'rate',
>   			    'queues',
> +			    'mtu',
>   			];
>   			fields.forEach(function(fieldname) {
>   			    me.down('field[name='+fieldname+']').setDisabled(value);
> @@ -161,6 +163,13 @@ Ext.define('PVE.qemu.NetworkInputPanel', {
>   		value: '',
>   		allowBlank: true,
>   	    },
> +	    {
> +		xtype: 'proxmoxintegerfield',
> +		name: 'mtu',
> +		fieldLabel: 'MTU',
> +		value: '',
> +		allowBlank: true,
> +	    },
>   	];
>   
>   	me.callParent();


Tested-by: Dylan Whyte <d.whyte at proxmox.com>