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

    Subnet 192.168.0.0/20(DHCP 192.168.0.x has internet but Static 192.168.1.x dont)

    Scheduled Pinned Locked Moved General pfSense Questions
    23 Posts 7 Posters 4.7k 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.
    • V
      vkad
      last edited by

      @johnpoz:

      "I know, I have enabled the firewall rule  in System -> Advanced "Bypass firewall rules for traffic on the same interface""

      What what possible reason would you do that?

      "I am not using /24 anywhere. All my devices are on /20 subnet"

      WHY??? You clearly do not have 4,000 some devices do you??

      As to devices in your /20 not getting internet access that you set as static.  Can they ping pfsense IP 192.168.0.1?  What are you lan rules?  What is your outbound nat?  Did you mess with them from automatic? And maybe you set them to manual or something then changed your mask?  So its only outbound natting portion of your /20

      Just at a loss to the point of using a /20 for a network with a handful of devices on it?  Using a network that is way bigger than required is just pointless.. While sure it will work, it makes no sense to do such a thing.  Shoot even a /24 is way to big for most home networks.  But it makes for easy human understanding of what the network actually is from address space range.  And gives you plenty of space to work with if you want to put some devices in different ranges of the address space.  Using an odd mask leads to mistakes as well.

      You have mentioned using 192.168.0 and 192.168.1 then why would you not just use a /23?

      If its a static IP in 192.168.0.1-192.168.0.255 then able to ping pfsense/internet works.

      All other ranges cant ping pfsense/no internet. They do show in ARP table randomly. If I change their IP to the 192.168.0.1 range they suddenly work fine.

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

        If you cannot ping the pfSense LAN then either there is a firewall rule blocking it (check the logs, try adding an allow all rule as a test) or a bad route/subnet somewhere.

        Is it possible you're using 192.168.1.0/24 on the WAN side?

        Is your 10GbE switch layer 2 only?

        Can we see some screenshots?

        A packet capture on LAN whilst trying to ping from something in 192.168.1.X would show if pings are arriving and if pfSense is able to respond.

        Steve

        1 Reply Last reply Reply Quote 0
        • SammyWooS
          SammyWoo
          last edited by

          VKAD, u are making yourself crazy doing something unusual, do u REALLY need 4096 hosts?

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