Try to masquerade traffic coming from your LAN and going to 192.168.2.15. Currently 192.168.2.15 is responding directly to user, while user waits response from router.
Search the forum for “hairpin NAT”. Recent posts about that term will be telling people telling other people to search for “hairpin NAT”, threads further back contain working configurations.
eish fewi, you’re too fast. I was just about to post here that I’ve updated an old thread about NAT loopback
Today is actually the first time that I’ve seen/heard about “hairpin NAT”. Previously I’ve seen people calling it: “NAT loopback” / “Reverse NAT” / “PAT”
Yeah, there’s lots of different terms for it. Coming from Cisco I call it hairpin NAT. They named it after the voice world where hairpinning a call refers to directing a call back out the way it came in. When you draw that out on a piece of paper as far as flow goes it looks U-shaped, like a hairpin.