From: Gabriel Goller <g.goller@proxmox.com>
To: Jakob Klocker <j.klocker@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [RFC proxmox{,-backup} 0/2] fix #7198: count veth uplink for PBS running in an LXC
Date: Tue, 7 Jul 2026 14:14:59 +0200 [thread overview]
Message-ID: <akzs0lcHmYRKb3Ce@luna.proxmox.com> (raw)
In-Reply-To: <20260707112008.321788-1-j.klocker@proxmox.com>
This seems a bit like a band-aid fix to me. Why do we not just get the uplink
interface via the default route: e.g. `ip -j route get 1.1.1.1 | jq .[0].dev`?
next prev parent reply other threads:[~2026-07-07 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 11:20 [RFC proxmox{,-backup} 0/2] fix #7198: count veth uplink for PBS running in an LXC Jakob Klocker
2026-07-07 11:20 ` [PATCH proxmox 1/2] network-api: add is_veth helper to IpLink Jakob Klocker
2026-07-07 11:20 ` [PATCH proxmox-backup 2/2] fix #7198: metric collection: count veth uplink when running in a container Jakob Klocker
2026-07-07 12:14 ` Gabriel Goller [this message]
2026-07-07 12:47 ` [RFC proxmox{,-backup} 0/2] fix #7198: count veth uplink for PBS running in an LXC Fabian Grünbichler
2026-07-08 8:49 ` Gabriel Goller
2026-07-08 8:11 ` Jakob Klocker
2026-07-08 8:45 ` Fabian Grünbichler
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=akzs0lcHmYRKb3Ce@luna.proxmox.com \
--to=g.goller@proxmox.com \
--cc=j.klocker@proxmox.com \
--cc=pbs-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