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

    Pfsense cant connect on lan

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 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.
    • J
      jonfil0130
      last edited by

      Hi, anybody can help me figure out the problem i got after setting up the pfsense box. WAN is fine. It can ping and do nslookup using public ip but the LAN is offline. Thanks

      1 Reply Last reply Reply Quote 0
      • W
        Wolf666
        last edited by

        We need more info, like topology, your connection type, current Outgoing NAT rules and firewall rules…...

        As a start check outgoing nat, check if LAN net is routed to WAN gateway (default, I assume you are on single WAN). Then check firewall rules on LAN tab, you should put a pass.

        In outbound nat, choose AON (manual), delete all rules and add:

        Do not NAT = [] (unchecked)
        Interface = [ WAN ▼]
        Protocol = [ any ▼]
        Source = [
        ] Not (unchecked)
                      Type: [ Network ▼]
                      Address: [ yourip subnet ] / [ 24 ▼]
                      Source port: [] (empty/blank)

        Not (unchecked)

                      Type = [ Any ▼]
                      Address: [
        ] / 24 ▼
                      Destination Port: [_____] (empty/blank)
        Translation: Address = [ Interface Address ]
        Description = [ LAN to WAN ]

        In Firewal rules, LAN TAB, you should add:

        Action = [ Pass ▼]
        Interface = [LAN ▼]
        TCP/IP Version = [IPv4 ▼]
        Protocol = [Any ▼]
        Source = [] Not (UNCHECKED)
                      Type: [ LAN Subnet ▼]
                      Address: [
        ] (BLANK)
        Destination = [
        ] Not (UNCHECKED)
                            Type: [ Any ▼]
                            Address: [
        __] (BLANK)
        Description = [✎ ALLOW LAN OUTBOUND]

        That's it!

        Modem Draytek Vigor 130
        pfSense 2.4 Supermicro A1SRi-2558 - 8GB ECC RAM - Intel S3500 SSD 80GB - M350 Case
        Switch Cisco SG350-10
        AP Netgear R7000 (Stock FW)
        HTPC Intel NUC5i3RYH
        NAS Synology DS1515+
        NAS Synology DS213+

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

          Hi Wolf666,

          Thanks for the very informative reply. I will give it a shot tomorrow and keep you posted. Actually, I do have a single WAN and using a model/router what i did is that i configured the modem/router to bridge then connect it to the WAN nic of pfsense server. I configured it to PPPOE and everything works fine. I connected the LAN nic to the switch to share internet connection. DHCP is running from the pfsense server. When I check the Status "Gateway" its only the WAN interface that's online and as mentioned it can ping and do nslookup. I checked the firewall under LAN and there's only 3 default rules and all of it are configured as "PASS" and for WAN there's 2 default rules which are both under "BLOCK". Maybe its something to do with the routing that's why i can't go online thru LAN. I appreciate your reply Wolf. Thanks again!

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

            I have to say I would always advise you leave outbound NAT set to automatic unless you really need to set manual rules. The suggested rule should work though.

            @jonfil0130:

            When I check the Status "Gateway" its only the WAN interface that's online

            This implies there might be more than one gateway. A common mistake is to add a gateway to the LAN interface which is almost always incorrect. Remove it if you have and then make sure the WAN gateway is set as default in System: Routing: Gateways:

            @jonfil0130:

            for WAN there's 2 default rules which are both under "BLOCK". Maybe its something to do with the routing that's why i can't go online thru LAN.

            The two rules you are seeing 'block bogons' and 'block private networks' are not a problem if your WAN interface is receiving a public IP via PPPoE. Even if it isn't it won't prevent internet access from LAN.

            Steve

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