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

    New install, can't access firewall

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 2 Posters 1.2k 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.
    • M Offline
      MilesDeep
      last edited by

      We are replacing our backup pfSense.  Installed 2.1.4.  Configured the LAN interface with the proper IP, subnet mask, and placed it on the appropriate VLAN.  I can't http or ping the new firewall.  Stumped, and this seams pretty straight forward.  Any thoughts?

      1 Reply Last reply Reply Quote 0
      • stephenw10S Online
        stephenw10 Netgate Administrator
        last edited by

        Did you change the LAN IP/subnet during the install of after you'd confirmed access to the webgui? Do you have console access?

        Steve

        1 Reply Last reply Reply Quote 0
        • M Offline
          MilesDeep
          last edited by

          There is no web access, only console.  Never web and could never ping.  No SSH either.

          Thanks for the thoughts.

          1 Reply Last reply Reply Quote 0
          • M Offline
            MilesDeep
            last edited by

            This may be an issue with VLAN tagging.  There is interface and parent interface…..

            1 Reply Last reply Reply Quote 0
            • stephenw10S Online
              stephenw10 Netgate Administrator
              last edited by

              So you did change the LAN from it's default during the initial setup?
              There should be no problem doing that but some users have seen issues. I suggest you run through the initial setup just accepting the defaults and then change it to fit your environment later.
              Could you give us some more details of your network?

              Steve

              1 Reply Last reply Reply Quote 0
              • M Offline
                MilesDeep
                last edited by

                It was an issue with parent VLANs.  I simply forgot about VLAN tagging for a bit.

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