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

    Additional WAN IP rules problem

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 3.8k 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.
    • B
      bernikm
      last edited by

      Hi

      Running pfSense 1.2.3 with WAN interface 212.30.75.1 and LAN interface 192.168.0.0/16 I created NAT Port-Forward rule to access WEB server from outside

      WAN  TCP/UDP  80 (HTTP)  192.168.10.13  (ext.: 212.30.75.1)  80 (HTTP)

      and Firewall WAN rule
      TCP/UDP  *  *  192.168.10.13  80 (HTTP)  *

      All is working perfectly. Now ISP give us additional 3 IPS in the same subnet as our existing IP on WAN interface:
      so I created: 3 Virtual IPs (Proxy ARP)
      212.30.75.2/32  P ARP
      212.30.75.3/32  P ARP
      213.30.75.4/32  P ARP

      3 additional NAT Port-Forward rules:
      WAN  TCP/UDP  80 (HTTP)  192.168.10.14  (ext.: 212.30.75.2)  80 (HTTP)     
      WAN  TCP/UDP  80 (HTTP)  192.168.10.15  (ext.: 212.30.75.3)  80 (HTTP)     
      WAN  TCP/UDP  80 (HTTP)  192.168.10.16  (ext.: 212.30.75.4)  80 (HTTP)

      3 additional Firewall WAN rules:
      TCP/UDP  *  *  192.168.10.14  80 (HTTP)  *         
      TCP/UDP  *  *  192.168.10.15  80 (HTTP)  *         
      TCP/UDP  *  *  192.168.10.16  80 (HTTP)  *

      The problem is, that from time to time some Virtual IP are not responding from Internet, it just doesn't porwards request to internal IP, but after a while it starts working. It's strange, because this happens without any intervention, even if we restarted pfSense it still doesn't answer to some of the Virtual IP (WAN interface IP and randomly some of the Virtual IP are always working), it only happens to randomly selceted Virtual IP from time to time.
      Have we misconfigured anything on pfSense, or any ideas why is this happening? Do we need to configure it any other way (it's just ordinary port-forwarding).
      Any help will be gladely appriciated.
      Regards,
      Miha

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