From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox 1/1] network-api: make address field optional
Date: Fri, 8 Aug 2025 10:01:00 +0200 [thread overview]
Message-ID: <8cce04f6-1499-4789-9a79-1398ae17dde5@proxmox.com> (raw)
In-Reply-To: <1f3e1441-d742-42e8-bccd-a7efd16b931b@proxmox.com>
On 8/8/25 9:29 AM, Christian Ebner wrote:
> Tested this with success on a device with wwan interface, reporting a
> link type `link/none` in `ip link show` output!
>
> Unfortunately this does not fix the issue on a host were I have an IPv6
> tunnel set up. The link there reports as `link/sit 0.0.0.0 peer <peer-ip>`.
>
> So it would be probably best to bundle mac address and link type ether
> in a struct or named tuple, and leave the option for other link types
> which might have different, non-mac hardware addresses.
Thanks for testing this, I'll look into implementing your suggestion!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-08-08 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 14:29 [pbs-devel] [PATCH proxmox{, -network-interface-pinning} 0/2] fix reading ip link output for interfaces without MAC address Stefan Hanreich
2025-08-06 14:29 ` [pbs-devel] [PATCH proxmox 1/1] network-api: make address field optional Stefan Hanreich
2025-08-08 7:29 ` Christian Ebner
2025-08-08 8:01 ` Stefan Hanreich [this message]
2025-08-06 14:29 ` [pbs-devel] [PATCH proxmox-network-interface-pinning 1/1] network-interface-pinning: adapt to optional mac address Stefan Hanreich
2025-08-08 11:56 ` [pbs-devel] superseded: [PATCH proxmox{, -network-interface-pinning} 0/2] fix reading ip link output for interfaces without MAC address Stefan Hanreich
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=8cce04f6-1499-4789-9a79-1398ae17dde5@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=c.ebner@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 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.