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

    OPT1 getting DHCP but no other connectivity

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 2 Posters 1.5k 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.
    • P Offline
      pfffsosensible
      last edited by

      Sorry for all the newb questions today…  Once I get setup I'll be more productive :)

      I've enabled OPT1 to use for my home network (vs LAN to be segregated for work).  So I set the OPT1 interface static IP to 192.168.1.1 (whereas LAN has 192.168.2.1). Both have DHCP and DHCP server successfully assigns addresses on both.  ...but devices on OPT1 don't resolve DNS or are even able to ping direct ip addresses.

      ...the reason I know there's something different about the interface is that if I swap the PC plugged into OPT1 vs LAN, the problem stays on OPT1.  The only difference in the settings is the IPv6 settings (which by default sets LAN to "track interface".  ...but I have a hard time imagining that I need IPv6 enabled to ping something.  Anyway, I disables the DHCPv6 server and I still have the same issue.

      Both interfaces say up with
      LAN    1000baseT <full-duplex>192.168.2.1
      OPT1  100baseTX <full-duplex>192.168.1.1

      I also noticed I can only access the pfsense web-gui from LAN, which is maybe by design?</full-duplex></full-duplex>

      1 Reply Last reply Reply Quote 0
      • P Offline
        phil.davis
        last edited by

        So I set the OPT1 interface static IP to 192.168.1.1 (whereas LAN has 192.168.1.1).

        I hope you have a cut-paste issue there - you can;t have LAN and OPT1 with the same IP address.

        I expect that you need to add firewall rule(s) on OPT1. Out-of-the-box LAN has a pass-all rule, but other interfaces have no pass rule and so block everything by default.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • P Offline
          pfffsosensible
          last edited by

          oops, yes. Fixed.

          …and it looks like fw rules was it - thanks for the help!!

          1 Reply Last reply Reply Quote 0
          • P Offline
            phil.davis
            last edited by

            Just a note about DHCP - when you enable DHCP on an interface, pfSense puts an (unseen) rule on the interface to allow incoming DHCP requests. So that is why DHCP works even when you have no user-added pass rule.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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