Cannot access Nokia web gui using port redirect

Hi,

I have new hardware setup like below:
Nokia 4G05-B receiver (set to bridge mode) ------> Router Cudy TR3000.
Nokia has web gui avialable at 192.168.0.1. I created an interface called nokia. I'm able open nokia web gui.
Problem has been started when I was trying redirect gui to another port. I knot it make no sense - originally wireguard zone was a source. For test I changed to lan and noticed that there is a problem with redirect itself. When I type 192.168.10.1:8100 at webbrowser I'm getting timeout.
Could someone tale a look and check this configuration? I check many times and don't see any issue why it's not working like I'm expecting.

root@OpenWrt:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.144.25.254   0.0.0.0         UG    30     0        0 eth0
10.144.25.0     0.0.0.0         255.255.255.0   U     30     0        0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 br-lan
root@OpenWrt:~# ping -c 5 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=64 time=0.803 ms
64 bytes from 192.168.0.1: seq=1 ttl=64 time=0.697 ms
64 bytes from 192.168.0.1: seq=2 ttl=64 time=0.697 ms
64 bytes from 192.168.0.1: seq=3 ttl=64 time=0.574 ms
64 bytes from 192.168.0.1: seq=4 ttl=64 time=0.615 ms

--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.574/0.677/0.803 ms

/etc/config/network

config interface 'nokia'
        option device '@wan'
        option proto 'static'
        option ipaddr '192.168.0.10'
        option netmask '255.255.255.0'

/etc/config/firewall

config redirect
        option name 'Nokia GUI'
        option src 'lan'
        option dest 'wan'
        option src_dport '8100'
        option dest_ip '192.168.0.1'
        option family 'ipv4'
        list proto 'tcp'
        list proto 'udp'
        option dest_port '80'

See my working example at the end of this post:

If that does not work for you, show the output of the following command executed on the router (or any device in your LAN where curl is available):
curl -I 192.168.10.1:8100