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

Block private network except…..

Scheduled Pinned Locked Moved Firewalling
4 Posts 2 Posters 3.4k 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.
  • R
    rexster
    last edited by Jun 21, 2006, 3:33 AM

    i have adsl modem router with internal ip 10.0.0.2
    say, my pfsense's wan have 10.0.0.3 (both private network)

    so, i want to activate this block private network,
    with one exception, if source from gateway (10.0.0.2)

    i try to create a rule to allow connection from 10.0.0.2,
    but, the rule is on the bottom and i cannot move it to the top.

    so, any easy way i can do this?

    tia
    rex

    http://www.GoBlogLah.com

    1 Reply Last reply Reply Quote 0
    • H
      hoba
      last edited by Jun 21, 2006, 4:19 AM

      To move a rule singleclick on it (there will be a check in the box in front of the row and the line will be highlighted yellow). Then click the [<] icon right of the line with the rule the highlighted rule should be put above. You also might need to disable "block private networks at wan" at interfaces>wan to make this work.

      Btw, what kind of connections do you expect to originate from your modem back to your LAN?

      1 Reply Last reply Reply Quote 0
      • R
        rexster
        last edited by Jun 21, 2006, 4:25 AM

        yes i know how to move rules.
        but, these special rules created by pfsense itself cannot moved anywhere.

        i want to do port forwarding.
        i expect connection like this:
        wan>>modem>>pfsense>>server

        http://www.GoBlogLah.com

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by Jun 21, 2006, 4:27 AM

          Portforwarded connections will still originate from the public IP of the host that is sending the request. Connections are only natted outbound (internal IP of server is replaced with WAN IP of the natting device). No need for this rule.

          1 Reply Last reply Reply Quote 0
          1 out of 4
          • First post
            1/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received