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

    Pfsense IP cant reach Internal network IPs

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    7 Posts 5 Posters 2.0k 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
      donchico
      last edited by

      Hi I have been trying to figure this out I hope experts here, can help me

      I have a fresh install through a quick install setup of pfsense 2.2.6 and here is the Infra >>

      modem>>pfsense 2.2.6  LAN (10.1.10.1/24 static) WAN (DHCP) >>switch>>windows server 2012 R2 DHCP/AD/DNS(10.1.10.2/24) >> Clients (10.1.10.100-200/24)

      It seems pfsense 10.1.10.1 IP is not in the ARP -a and when i try to ping any ip in the network like the 10.1.10.2 (WS2012 DHCP) or a client its not reaching it, Im recieving a request time out.

      and when I open 10.1.10.1 in the browser its not reaching the ip.

      ![ping 1.jpg](/public/imported_attachments/1/ping 1.jpg)
      ![ping 1.jpg_thumb](/public/imported_attachments/1/ping 1.jpg_thumb)

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

        any help is appreciated

        1 Reply Last reply Reply Quote 0
        • C
          coxhaus
          last edited by

          You need separate domains.  Either separate networks or separate VLANs per network.  And since they are layer 3 you routing between them.

          1 Reply Last reply Reply Quote 0
          • jahonixJ
            jahonix
            last edited by

            @donchico:

            modem>>pfsense 2.2.6  LAN (10.1.10.1/24 static) WAN (DHCP) >>switch>>windows server 2012 R2 DHCP/AD/DNS(10.1.10.2/24) >> Clients (10.1.10.100-200/24)

            You have the ports on your pfSense reversed.
            WAN is what goes to your modem, LAN connects to the internal switch.

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

              I think the problem is the Network Card Mine is D-Link DGE-528T network card.

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Doesn't look like hardware.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • M
                  muswellhillbilly
                  last edited by

                  As Jahonix mentioned, are you sure you have your network cards plugged into the correct networks? Swap the cables over and see if that helps.

                  Also, you don't mention what DHCP address you're getting on your WAN connection. Is the PFS picking up an address correctly on the WAN? And if so, is the WAN network address range similar/the same as your LAN address range?

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