Feature requirement: Skip the conflict detection function of creating a network with other network address segments

[InPRTx]

I have a very useful intranet, which can access the container's IP by using the internal IPv6 address. However, I have encountered problems in creating a network during use. I hope to add instructions to skip the detection of address segment conflicts. When I use this command, an error will be reported. I hope to skip the error and bypass the detection.

podman network create --label io.podman.compose.project=app --label com.docker.compose.project=app --ipv6 --subnet fc6a:795e:392:20:2ac1:464c:a2cf::/112 app_in-net2

Error: subnet fc6a:795e:392:20:2ac1:464c:a2cf:0/112 is already used on the host or by another config

But in fact, this route is only included in fc6a:795e::/32 and does not conflict

ip -6 r|grep fc6a
fc6a:795e:392:20:9a11:464c:ea1f:0/112 dev podman1 proto kernel metric 256 pref medium
fc6a:795e:528::/48 via fe80::ff:fe30:334 dev tinc0 proto bird metric 32 pref medium
fc6a:795e:702::/48 via fe80::ff:fe30:334 dev tinc0 proto bird metric 32 pref medium
fc6a:795e::/32 dev tinc0 proto kernel metric 256 pref medium

https://github.com/containers/common/blob/bbb5c4a80e3700855554f64ed8e43b83084e0344/libnetwork/internal/util/validate.go#L31-L36 https://github.com/containers/common/blob/bbb5c4a80e3700855554f64ed8e43b83084e0344/libnetwork/internal/util/ip.go#L45-L56