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

    Multiple LAN's

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 4 Posters 2.8k 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.
    • C
      cashcomp
      last edited by

      Hey all

      i have a pfsense router in place with 4 NIC's configured as follows:

      –->ADSL---->WAN
                            |---LAN
                            |---SERVERS
                            |---CLIENT

      As it sits the internet works fine on the LAN & SERVERS subnets but i cannot for the life of me get it to work in the CLIENTS.

      additional information is as follows:

      WAN:
        Static IP from provider ...6
        gateway                  ..
      .5

      LAN:
        192.168.15.1/24 (DHCP enabled)

      SERVERS:
        Static IP from provider ..***.240/16
        Gateway left blank (technically same as above)

      CLIENTS:
        192.168.100.1/24 (DHCP enabled)
        Gateway left blank (technically should be the same as above)

      i have it set this way for my own internal business network (LAN), some servers that i have open to the world (SERVERS) and i work on additional PC's that I do not want affecting my network or servers.  the CLIENTS network assigns IP's but none of them can access anything at all.  they even have problems when asked to ping the router (192.168.100.1)

      any thoughts would be great, i know that i am missing something small here but just cannot put my finger on it.  BTW PFSENSE's ping utility will ping successfully through any interface and it is ONLY the CLIENTS NIC that is giving me grief.

      TIA
      cashcomp

      1 Reply Last reply Reply Quote 0
      • A
        aaron
        last edited by

        My initial thought, and apologies if you've already done this… but have you defined rules for traffic to pass through on the client interface?  This may be why pfSense can ping your client workstations but they can't ping back or access the WAN.

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG
          GruensFroeschli
          last edited by

          192.168.100.1/24 (DHCP enabled)
            Gateway left blank (technically should be the same as above)

          This will never work.
          Without a gateway only local traffic is possible.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by

            Please show us an "ipconfig /all" (if these are windows machines) from one of your clients and show us the firewallrules you added for your clients interface. Cabling seems to be ok as you can ping the clients from the pfSense.

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