FTP via WAN IP from local/internal clients

[Scacht]

Hi all,

I'm smashing my head against the wall and I'm sure I'm missing something simple.  I setup ftpproxy and I want to be able to FTP into a local server via local clients using the WAN interface, so I can use my domains without any fancy DNS work.  I can FTP in from outside the LAN easily, and everything works, but when I try a client on the local network, hangs on "Connection established, waiting for welcome message". 

I setup the FTP proxy using the defaults suggested and have the following rules:

Under WAN:

NAT:

I can see traffic passing:

I'm sure it's something super simple I've overlooked.  Thoughts?

[Napsterbater]

Use hostoveride via the DNS server to resolve a domain name to the Local IP.

[Greelan]

Enable NAT reflection?

[Scacht]

Use hostoveride via the DNS server to resolve a domain name to the Local IP.

I wanted to avoid it, but that's probably the best solution at this point.  Added an override and everything worked immediately inside and outside the network. 

Enable NAT reflection?

Already have, and tried several variants of the NAT settings.  Currently all 3 NAT reflections are enabled. 

What's frustrating is literally all of my other remote services work except accessing (via WAN IP/DNS) SSH and FTP locally.  My nginx reverse proxy has 0 issues.  I've probably been looking at it too long.

[Greelan]

What interfaces is SSH listening on?

[Napsterbater]

Use hostoveride via the DNS server to resolve a domain name to the Local IP.

I wanted to avoid it, but that's probably the best solution at this point.  Added an override and everything worked immediately inside and outside the network.

Why? Its the best way, why bounce traffic off the router unnecessarily (if on the same subnet), or why use hacks (NAT rewrites and mangels packets, it's a hack, especially hairpin/loopback/reflection)

Host overrides are akin (and basically) split horizon DNS.