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

    Public Subnet in LAN - not working.

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 4 Posters 1.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.
    • D Offline
      Deviant
      last edited by

      Hi all, I hope someone can help, I have trawled the interweb and bought the pf bible but I am having no luck whatsoever using public IP's on the LAN.

      Current setup.

      Gateway Router .129
      WAN of pfsense .130
      LAN of pfsense  .132

      LAN DHCP Range .133 - .139

      In each instance, including the wiki, it says all you have to do is disable Auto NAT, go Manual and delete the auto rules…

      Now I know that's way too simple but yet I am lost, can anyone advise?

      Regards,

      Dvnt.

      1 Reply Last reply Reply Quote 0
      • H Offline
        hmeister
        last edited by

        @Deviant:

        Hi all, I hope someone can help, I have trawled the interweb and bought the pf bible but I am having no luck whatsoever using public IP's on the LAN.

        Current setup.

        Gateway Router .129
        WAN of pfsense .130
        LAN of pfsense  .132

        LAN DHCP Range .133 - .139

        In each instance, including the wiki, it says all you have to do is disable Auto NAT, go Manual and delete the auto rules…

        Now I know that's way too simple but yet I am lost, can anyone advise?

        Regards,

        Dvnt.

        Can you get more info here?
        XXX.XXX.129.x?
        Or??
        Is there a reason to use public IP? Are you trying to fit pfSense into an existing network setup?
        Is this where your are going? "http://pfsense.trendchiller.com/transparent_firewall.pdf"Transparent Bridging?

        Best Regards;
        H.

        1 Reply Last reply Reply Quote 0
        • F Offline
          FJSchrankJr
          last edited by

          I just posted something similar, a guide for 2.0-RC1. That guide is for 1.2.3

          Go back to the Firewall category and look for the guide just posted today

          FJS - Embedded Systems Engineer
          Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
          ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

          1 Reply Last reply Reply Quote 0
          • D Offline
            Deviant
            last edited by

            Hi and thanks! I believe I have managed to get it working, although I went back to scratch and used the LAN interface instead of OPT1 is there a know issues with using OPT interfaces?

            Currently I am testing on PF 1.2.3 but shortly moving onto 2.0-RC2.

            Also note that in the link you posted it says to leave LAN IP blank or "none" I had to assign an IP from my subnet to the LAN which isnt ideal but it worked AOK, what did you mean by "none"?

            I have also used transparent bridging and is my current method but I would like to use the DHCP server to assign my public IP's.

            Another issue I have with the bridging method is posted here http://forum.pfsense.org/index.php/topic,37803.0.html if you could have a look and comment on my set up that would be great :)

            My IDEAL set up would be…

            GW ROUTER = xxx.xxx.89.129
            WAN = xxx.xxx.89.130

            VLAN3 = Management VLAN for wireless AP's (all in layer2 bridge mode) that all clients connect through 192.168.1.0/24
            VLAN100 = Local IP subnet/DHCP 10.0.100.0/24
            VLAN200 = Public IP subnet/DHCP xxx.xxx.89.140/27

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

              LAN and WAN cannot be the same subnet. Check the section of the book that describes means of using additional public IPs, it describes the options in detail.

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