Problem with Port forwarding on a non RFC compatible Network

[Guest]

[sandmann]

Hi to all,

I have a problem with Port forwarding on a non RFC compatible Network structure. I have this problem with Endian Community 3.0.0 and 3.0.5.
The problem is, that forwarding to the final server is not working. When I connect the server directly with the router, the traffic on Port 8000

will be forwarded correctly, but not after the Endian.
I have entered the values on Port forwarding and incomming traffic.

Could it be that the Endian has a problem with non RFC compatible Networks?

Shortform of configuration:
DSL Internet on a Router (internal Firewall and NAT. No difference if active or inactive)
--- until this point I can connect the Server, but it should be after the Endian. Most access is internal.
Network tunnel with a "public" IP to the Endian
Endian Firewall and a internal Network, also with a "public" IP. Transpartent Proxy, no difference if active or inactive)

Incomming Traffic from RED on Port 8000 routed to internal IP on Port 8000.
Port forwarding of port 8000 from all RED IPS to internal IP on Port 8000, no NAT on this rule.

"public" IP means that there are no IPs used in the kind of 192.168.100.. We don't use the IPs who are marked in the RFC as internal private IP.

We use something different like 37.67.97..

We haven't had any problem in the past 10 years, until this new Port forwarding.

Any idea how to solve this?


Thank you for help in advance.

sandmann