Portforward WAN -> OpenWrt -> S2S Fritzbox

Hello Trendy,
i did rebuild the old version now:
storj container running on docker, wireguard on debian.
storj node asks per DNS us2.storj.io. resolve works.

ping from openwrt (wg-server) to debian (wg-client) is working (wireshark i-face wg-papa).

25010 packets do not reach wg-client (no entry in wireshark i-face wg-papa on debian).
i can see them from wan via fritzbox to openwrt (server) via wireshark.

Config from OpenWRT:

config redirect
option dest 'wireguard'
option target 'DNAT'
option name 'storj TCP und UDP'
option src 'wan'
option src_dport '25010'
option dest_ip '192.168.1.100' > (wg-client)
option dest_port '25010'

config rule
option src 'wan'
option dest_port '25010'
option target 'ACCEPT'
option name 'Allow-storj-TCP-UDP'

Good morning Trendy,
tried another setup without additional wireguard.

dad-fritz -> dad-openwrt -> debian-apc -> docker ports published to host.
deleted traffic rules, changed port forwardfrom wg-tunnel to forward to debian.
and it works. atleast a bit. storj can be connected from external.

one last problem:
storj-node sees the openwrt-ip instead of the external ip and external port.
wireshark-openwrt shows (for example):
Source: 158.140.235.61 port: 43872 <- fritzbox forward keeps source IP.
Destination: 192.168.1.50 port: 25010

wireshark on debian:
Source: openwrt-ip
Destination: debian port 25010
how to keep source ip on port forwarding ?

config redirect
option target 'DNAT'
option name 'storj TCP und UDP'
option src 'wan'
option src_dport '25010'
option dest_port '25010'
option dest 'wan'
option dest_ip '192.168.2.100'
option reflection_src 'external'

Hello Trendy,
one variant seems to work now:

Docker Storj -> Docker WG -> OpenWRT as router).
my problem was: port mapping inside linked container does not work....
tried default ports and voila... it works.

still one question: keep source ip on forwarded traffic.