Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Redirect Internal IP to another Internal IP

    Scheduled Pinned Locked Moved General pfSense Questions
    9 Posts 3 Posters 774 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fazambuja
      last edited by

      We are updating our network with pfsense and will use a new IP range (10.10.10.xxx); the old range, 192.168.1.xxx, will not be used.

      However, we have software that is hard coded to reach a specific internal IP 192.168.1.20 (server address).

      How can I redirect the traffic from 192.168.1.20 to 10.10.10.20(the new address of the server)?

      I got it using NAT 1:1, but this seems to be made for external IP and not an Internal one like I'm using.

      Thanks

      johnpozJ 1 Reply Last reply Reply Quote 1
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Is it not working with the 1:1 NAT rule?

        You can use a port forward but you would also need to use an outbound NAT rule to avoid asymmetric routing if it's on the same interface.

        Steve

        F 1 Reply Last reply Reply Quote 0
        • F
          fazambuja @stephenw10
          last edited by fazambuja

          @stephenw10 said in Redirect Internal IP to another Internal IP:

          port forward but you would also need to use an outbound NAT rule to avoid asymmetric routing if it's on the same interface.

          It works with 1:1; I will check the outbound rule. Should I remove the 1:1 rule, then?

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @fazambuja
            last edited by

            @fazambuja There is no possible way to get this hard coded IP changed in the software?

            Hard coding IPs has always been a bad idea.. If it was some fqdn you pointed to, then IP changes become no big deal, just change the dns to point to the new IP.

            If you have software that is using hard coded IPs, and not possible to change - why the desire to move to a 10 network? Can you just not setup pfsense and use the same 192.168.1 network? That would make your life simpler ;)

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            F 1 Reply Last reply Reply Quote 0
            • F
              fazambuja @johnpoz
              last edited by

              @johnpoz You are right. I will use the old IP range to avoid problems. I just wanted to check if it was something more straightforward.

              Thanks

              johnpozJ 1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator @fazambuja
                last edited by

                @fazambuja while what your asking can be done, it for sure complexes the setup quite a bit.

                Unless there is some specific reason to really change your network IP scheme to something other than the 192.168.1 I would leave it on that at least until such time that you retire that software or have a easy way to change the hard coded IP, best would be changing it to fqdn.

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 1
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  I mean I might argue that using 192.168.1.X is generally a bad idea if you ever want to connect to other private networks...

                  johnpozJ F 2 Replies Last reply Reply Quote 1
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator @stephenw10
                    last edited by

                    @stephenw10 Which is why asked what was the reasoning for switching, maybe that was the reason? But seems maybe not?

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 2
                    • F
                      fazambuja @stephenw10
                      last edited by

                      @stephenw10 I used it just as an example.

                      1 Reply Last reply Reply Quote 1
                      • First post
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.