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

    Unexplained Behavior on a Network Interface 192.168.1.2

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 3 Posters 296 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.
    • A
      azizth
      last edited by

      In a hotel's network setup with pfSense as the firewall and Unifi for networking equipment, I am facing a puzzling issue with the Administration network.

      Here is the configuration of my pfSense firewall with six network interfaces:

      • 192.168.1.0/24 - Administration
      • 172.16.0.1/24 - Management
      • 172.16.144.1/22 - Guest

      The Admin interface of pfSense is set to 192.168.1.2.

      Although the Admin interface is configured with an any-to-any rule in the firewall, it is impossible to ping it from within the Administration network (even from the pfSense interface itself). However, it is pingable from the other networks.

      Moreover, PCs in the Administration network, when configured with DHCP, have no access to the network. When their IPs are set manually, they can access the internet via 192.168.1.2, but they still cannot ping the Admin interface — not even with a traceroute.

      I tried assigning the Administration network to a different network card, deleting the configuration, and starting from scratch. Still, the issue persists. This behavior is inexplicable to me, especially since all other networks are functioning correctly without any problems.

      Could you please help me resolve this?

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

        Check the dhcp leases. Make sure it's actually pfSense handing out the leases. A rogue dhcp server might explain this.

        Try a pcap on the admin interface while you're trying to ping it. Make sure the pings actually arrive.

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @azizth
          last edited by

          @azizth said in Unexplained Behavior on a Network Interface 192.168.1.2:

          Moreover, PCs in the Administration network, when configured with DHCP, have no access to the network

          The show use and yourself why ?!!

          ipconfig /all
          

          and you see everything about the lease : the IP, the gateway which must be 192.168.1.2, the DNS that must be 192.168.1.2 etc.

          Just for my own curiosity why 192.168.1.2 and not 192.168.1.1 ?
          192.168.1.1 has been tested by millions, and doesn't need any thoughts.
          Changing it to 192.168.1.2 is like opening a can of worms, which isn't a big deal, but look again, you can't see the bottom of the can.

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

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