From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] www: sdn: improve naming of vm network device in bridge view
Date: Mon, 17 Nov 2025 15:25:02 +0100 [thread overview]
Message-ID: <8c8a9385-9152-4447-9810-cb91a38a5db0@proxmox.com> (raw)
In-Reply-To: <20251117140307.161410-1-g.goller@proxmox.com>
Am 17.11.25 um 15:03 schrieb Gabriel Goller:
> When selecting a bridge we show all the ports and also decode the
> firewall bridge port name. The name contaians the vmid and the vm
> network device index. If we apply
> https://lore.proxmox.com/pve-devel/20251117140121.160192-1-g.goller@proxmox.com/
> the full interface name will be shown (`net{index}`), so this is a
> better name for the column.
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
> www/manager6/sdn/ZoneBridgesPanel.js | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/www/manager6/sdn/ZoneBridgesPanel.js b/www/manager6/sdn/ZoneBridgesPanel.js
> index 600b23b0a8f8..f89f7956434a 100644
> --- a/www/manager6/sdn/ZoneBridgesPanel.js
> +++ b/www/manager6/sdn/ZoneBridgesPanel.js
> @@ -76,7 +76,7 @@ Ext.define('PVE.sdn.ZoneBridgePortsPanel', {
> dataIndex: 'vmid',
> },
> {
> - text: gettext('Network Device Index'),
> + text: gettext('VM Network Device'),
Is this really limited to VMs or can CTs also be shown? For the latter we
might want to use "Guest Network Device"
> flex: 1,
> sortable: true,
> dataIndex: 'index',
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-17 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 14:03 Gabriel Goller
2025-11-17 14:25 ` Thomas Lamprecht [this message]
2025-11-17 14:30 ` Gabriel Goller
2025-11-17 14:42 ` 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=8c8a9385-9152-4447-9810-cb91a38a5db0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@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