From: Maurice Klein via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Maurice Klein <klein@aetherus.de>
Subject: [pve-devel] [PATCH container 0/1] qemu-server add bridged Networking mode
Date: Fri, 9 Jan 2026 13:10:48 +0100 [thread overview]
Message-ID: <mailman.307.1767981922.353.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4795 bytes --]
From: Maurice Klein <klein@aetherus.de>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container 0/1] qemu-server add bridged Networking mode
Date: Fri, 9 Jan 2026 13:10:48 +0100
Message-ID: <20260109121049.70740-1-klein@aetherus.de>
*** BLURB HERE ***
Maurice Klein (1):
Signed-off-by: Maurice Klein <klein@aetherus.de>
src/PVE/QemuServer.pm | 9 +++++-
src/PVE/QemuServer/Network.pm | 19 +++++++++++
src/usr/pve-tap | 59 +++++++++++++++++++++++++++++++++++
src/usr/pve-tap-hotplug | 3 ++
src/usr/pve-tapdown | 16 ++++++++++
5 files changed, 105 insertions(+), 1 deletion(-)
create mode 100755 src/usr/pve-tap
create mode 100755 src/usr/pve-tap-hotplug
create mode 100755 src/usr/pve-tapdown
--
2.39.5 (Apple Git-154)
Aim for my patches:
allow the setup of a network interface in QEMU VMs that uses routed TAP interfaces instead of bridged ones.
Pure L3 design without L2 dependencies Eliminates the need for bridges, broadcast domains, ARP flooding, and other L2-related complexity when it is not required.
See more: https://forum.proxmox.com/threads/feedback-routed-l3-routing-without-bridge.178933/
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2026-01-09 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 12:10 Maurice Klein via pve-devel [this message]
2026-01-09 12:45 Maurice Klein via pve-devel
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=mailman.307.1767981922.353.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=klein@aetherus.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.