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

    1:1 NAT working for one but not for another

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 819 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.
    • A
      alltime
      last edited by

      We have two websites set-up on our network:

      • Local website set-up on 209.59.59.194 goes to 192.168.1.4

      • Local website set-up on 209.59.59.196 goes to 192.168.3.4

      209.59.59.194 routes correctly while 209.59.59.195 does not route anywhere despite being the same set-up, but different network. I'm not quite sure what else could be checked here. I've attached our firewall rules, as you can see nothing is special.

      Note that: 209.59.59.194 is our main IP for accessing the web however our ISP has given us a bulk of addresses so 209.59.59.195 is ours also and is not used.  Also, both websites work internally using the internal IP addresses.

      WAN = LIME
      LAN = WIRELESS (192.168.1.1) and LAN (192.168.3.1)

      NAT:
      IP's are changed for security purposes

      Firewall Rules (WAN)

      Firewall Rules (WIRELESS)

      Firewall Rules (LAN)

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        You wrote .195 but have 1:1 on .196, maybe typo there? Otherwise, you're likely missing a virtual IP on the public IP that doesn't work.

        1 Reply Last reply Reply Quote 0
        • A
          alltime
          last edited by

          @cmb:

          You wrote .195 but have 1:1 on .196, maybe typo there? Otherwise, you're likely missing a virtual IP on the public IP that doesn't work.

          That was a typo, I went ahead and corrected it.

          Well why do you think that 209.59.59.194 worked? After adding the 209.59.59.196 virtual IP, still no luck.

          Virtual IP's:

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            .194 works because it's your WAN IP, hence already answering ARP. Packet capture on WAN, filter on the IP that's not working, what's that look like?

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