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

    No Web GUI on clean 2.3.3 install

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 802 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
      dsp3
      last edited by

      I have been fighting this all day and have read as much info here as I can, but I'm unable to find the answer, so here is my problem.

      New install with 2 NIC's. 1 on motherboard and 1 PCI-E.
      Clean install. When configuring interfaces, auto doesn't work. However, manually assigning does. I have:

      re0 -> WAN - (with correct ISP assigned DHCP IP, which is fixed 96.103.xx.xx)
      re1 -> LAN - 192.168.1.1

      WAN and LAN are different subnets!

      Client computer is assigned IP 192.168.1.100

      Go to WebGui on client: 192.168.1.1 Nothing. Timeout
      Try https://192.168.1.1 - Nada
      Tried different browsers.

      ping from client to 192.168.1.1. 100% packet loss
      ping from host to client.  100% packet loss.

      Client is connected directly to LAN NIC. No switches in between.

      Can update pfsense from console, so WAN works.

      Suggestions?

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Get a switch?
        Get a crossover cable?
        Get a working cable?
        Get a crystal ball?

        1 Reply Last reply Reply Quote 0
        • D
          dsp3
          last edited by

          @doktornotor:

          Get a switch?
          Get a crossover cable?
          Get a working cable?
          Get a crystal ball?

          Got a switch. No change
          Don't have a crossover cable, but I have a switch that works.
          Working cable? Wouldn't get an IP assigned on LAN client if cable didn't work. Swapped anyway. Same result.
          Crystal ball. Working on it.

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