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

    Pfsense 1.2 RC3 install woes (wan problem)

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    7 Posts 3 Posters 2.5k 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.
    • J
      jan.gestre
      last edited by

      Hi Guys,

      It's been a while since I got my hands wet with pfsense and I thought it would be a walk in the park after a year of absence using it but apparently not, I'm bumping into some road blocks that's been difficult for me to get over. Currently we are using a proprietary firewall appliance that already reached EOL vendor support and we would like to replace it by implementing pfsense in all of our offices. I'm using the 1.2 RC3 release in my HP Compaq D220 MT (3 nics) and our isp provided us with 124.107.xx.xx/29 ip block. I was amazed that the WAN interface got an ip address from the modem, apparently it's also a dhcp server, I also configured the LAN and DMZ interface. When the WAN interface is using a dhcp assigned public ip address from the modem/gateway, there's no problem, LAN clients have internet connection but when I set the WAN interface to static ip address, problems set in. LAN clients don't have internet connection, I also checked if the switch where the modem/gateway and WAN interface is connected is the culprit but it isn't because when I connected a windows client and assigned it a public ip, it can connect to the internet just fine. I'm totally clueless as to what's causing the problem, any of you guys experienced this? What would be the workaround if any?

      TIA

      1 Reply Last reply Reply Quote 0
      • GruensFroeschliG
        GruensFroeschli
        last edited by

        Did you set a DNS servers manually after you've set the static public IP?

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • J
          jle2005
          last edited by

          When you setup the WAN interface with Static IP, you need to put in the right CIDR Mask Bits.

          For example: your WAN IP is 10.10.1.1 and the Subnet Mask 255.255.255.0 then your CIDR Mask Bits is 24.

          1 Reply Last reply Reply Quote 0
          • J
            jan.gestre
            last edited by

            @GruensFroeschli:

            Did you set a DNS servers manually after you've set the static public IP?

            Hi GruensFroeschli,

            Yes, I did set the DNS servers manually after changing the IP address to static, I even ran the setup wizard to no avail, still have the same problem. One weird thing I also noticed is that when I installed the 3rd nic (I'm still using the DHCP assigned public IP during first install) after a restart, the console generated "No Route to host messages" and I have no internet connection anymore. What do you think is causing this?

            TIA,

            Jan

            1 Reply Last reply Reply Quote 0
            • J
              jan.gestre
              last edited by

              @jle2005:

              When you setup the WAN interface with Static IP, you need to put in the right CIDR Mask Bits.

              For example: your WAN IP is 10.10.1.1 and the Subnet Mask 255.255.255.0 then your CIDR Mask Bits is 24.

              My public IP is 124.107.xx.xx and the subnet mask is 255.255.255.248, I think at first I've used the /32 because it's a single IP, is this correct? I also think that I tried using /29 as CIDR and also did not work, I'm not sure though if I really did the latter.

              1 Reply Last reply Reply Quote 0
              • J
                jle2005
                last edited by

                No, if your subnet mask is 255.255.255.248 then you should use /29. You should also check the Gateway and DNS for the right IP setting.

                1 Reply Last reply Reply Quote 0
                • J
                  jan.gestre
                  last edited by

                  @jle2005:

                  No, if your subnet mask is 255.255.255.248 then you should use /29. You should also check the Gateway and DNS for the right IP setting.

                  My mindset was I'm configuring the NAT that is why the /32 netmask, anyways, it's now working when set to /29.  So simple yet overlooked. Thanks.

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