How can I achieve a remote connection to a client from a container, without using network_mode: host?

[Onotot]

Hello. I'm encountering an issue with FRP(Fast Reverse Proxy) for remote router connections. I can only establish a connection when the container's network mode is set to host. This is not a suitable configuration for me, as I need to utilize a custom network.

[Container]
ContainerName=frp
Image=ghcr.io/fatedier/frps:v0.65.0
PublishPort=7000:7000
PublishPort=127.0.0.1:10022:10022
Network=host
Volume=/home/user/frps/frps.toml:/etc/frp/frps.toml
Exec=-c /etc/frp/frps.toml
AutoUpdate=registry
[Unit]
Description=FRPS Container
# After=frps.socket
# Wants=frps.socket

[Service]
Restart=always

[Install]
WantedBy=default.target

FRP Server Config:

bindPort=7000
proxyBindAddr="127.0.0.1"

FRP Client Config:

config init
	option stdout '1'
	option stderr '1'
	option user 'root'
	option group 'root'
	option respawn '1'

config conf 'common'
	option server_addr 'remote_addr'
	option server_port '7000'
	option log_level 'trace'
	option token 'token'
	option tls_enable 'true'

config conf 'ssh'
	option type 'tcp'
	option local_ip '192.168.1.1'
	option local_port '22'
	option remote_port '10022'
	option name 'ssh'

The logs indicate a successful connection between the client and server:

client login info: ip [router_ip]
16:03.156 [I] [proxy/tcp.go:82] [dbd0b998412b8f79] [ssh] tcp proxy listen port [10022]
16:03.157 [I] [server/control.go:399] [dbd0b998412b8f79] new proxy [ssh] type [tcp] success

Upon successful connection, I enter the command ssh -p 10022 [email protected] and gain access to the router.

But this is only functional when using network_mode: host. When I switch to a custom network or different modes, like network: pasta, SSH fails to connect.

Connection closed by 127.0.0.1 port 10022
# or
Connection reset by 127.0.0.1 port 10022

My initial thought was that the problem lay with the client's IP, that it was being swapped out for Podman's internal IP. But upon checking, this wasn't the case.

Is it possible to solve this task while preserving the client's IP and using a custom network, or not? Activation via socket for frp is not working.