4

We need a router to translate a TCP port for a connection between an inside device and an outside server.

The outside server (1.1.1.2) will establish a connection to the inside device (10.0.0.10) on TCP port 123, but the inside device is listening on port 234. The router will need to forward inbound traffic destined for 10.0.0.10 port 123 to 10.0.0.10 port 234.

I have found very simple instructions for doing this here, but when I try this I get duplicate IP address errors and the router seems to take over the inside device's IP address. (A "show ip arp" will show the router's MAC address for the inside device.)

ip nat inside source static tcp 10.0.0.10 234 10.0.0.10 123

What could I be doing wrong? The instructions are from 2006. Has Cisco changed NAT since then?

Thanks!

  • Are you able to post more of your router config (sanitized)? Or at least the interface configs? – some_guy_long_gone Aug 13 '14 at 14:08
  • That's how it's always worked. When an address is used for PAT, the router "owns" it. And you cannot mix one-to-one NAT with PAT -- it might take the config, but it isn't going to work like you expect. – Ricky Beam Aug 13 '14 at 19:34
  • @Ricky I'm new at this, and maybe I didn't clearly describe my scenerio, but that Cisco document linked to above exactly describes our situation. I believe that somewhere between 2006, when the document was created, and now Cisco changed the way one-to-one NAT worked requiring the "no-alias" option to work as originally described in the document. – Stephen Craven Aug 14 '14 at 19:09
4

To prevent the router from assuming the IP address you want to port forward from, I discovered that you must add the "no-alias" option at the end.

ip nat inside source static tcp 10.0.0.10 234 10.0.0.10 123 no-alias

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.