From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Sichert <l.sichert@proxmox.com>
Subject: applied: [PATCH network v2] tests: use valid ipv6 snat data for sdn config generation
Date: Wed, 13 May 2026 05:08:17 +0200 [thread overview]
Message-ID: <177864169610.4078454.15640186505139384592.b4-ty@b4> (raw)
In-Reply-To: <20260507144717.80160-1-l.sichert@proxmox.com>
On Thu, 07 May 2026 16:47:15 +0200, Lukas Sichert wrote:
> It is not possible to NAT ipv6 to ipv4. Rules like
> 'ip6tables -t nat -A POSTROUTING -s '2a08:2142:302:3::/64' -o vmbr0 -j
> SNAT --to-source 10.0.1.10'
> fail with:
> 'Bad IP address "10.0.1.10"'
> On a real system, the outgoing interface is resolved via 'ip route get
> 2001:4860:4860::8888'. 'ip route get' cannot output an
> ipv4 address if querying for an ipv6 address. If the 'ip route get'
> query is executed without an ipv6 address configured, the query fails.
> However, the simulated wrapper function currently returns '(vmbr0,
> 192.168.0.1)'.
>
> [...]
Applied, thanks!
[1/1] tests: use valid ipv6 snat data for sdn config generation
commit: 0e93afc970a8f29e98c93e9b4989f2caf582e5d5
prev parent reply other threads:[~2026-05-13 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 14:47 [PATCH network v2] tests: use valid ipv6 snat data for sdn config generation Lukas Sichert
2026-05-13 3:08 ` Thomas Lamprecht [this message]
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=177864169610.4078454.15640186505139384592.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=l.sichert@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 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.