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

    2 wireless ap's, 2 physical interfaces, DHCP assignment conflicts

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 3 Posters 444 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.
    • E
      Ev4nsp479
      last edited by

      I have one wireless AP on my LAN interface setup and running just fine. I have DHCP mappings and specific rules set for things mapped on my LAN (192.168.1.etc.) I have a spare wireless AP and spare physical interfaces (I have a 4port intel nic, a two port intel nic, and 2 single intel nics) on my pfsense box to use so why not. So, I thought i would setup another guest network on one of the open interfaces and set the interface to Guest (192.168.3.etc.). DHCP server running on both and for the most part working ok. An issue i have noticed is when i connect my laptop on the new guest wifi network that it sometimes assigns my DHCP static mapped LAN address (192.168.1.30), and sometimes it assigns it a Guest network address (192.168.3.x). ill attach some screen shots to each interface DHCP page .

      I would like any device that connects to the guest wifi network AP to get a guest ip (192.168.3.x), and if connected to the lan wifi AP to get a lan ip (192.168.1.x). is there something i'm forgetting (besides proper grammer) or are the static mappings throwing things off? again, there doesnt seem to be a rhyme or reason why sometimes on the guest network i still get a lan IP assigned and other times i get a guest ip assigned for the same device even thought the networks are on separate physical interfaces/networks. the devices are working correctly (per my designated interface firewall rules), it's the ip assignment that is unpredictable. Thanks in advance!
      Screenshot_2019-03-24 Services DHCP Server LAN1 - pfSense localdomain.png
      Screenshot_2019-03-24 Services DHCP Server LAN2 - pfSense localdomain.png
      Screenshot_2019-03-24 Services DHCP Server GUEST1 - pfSense localdomain.png
      Screenshot_2019-03-24 Services DHCP Server GUEST2 - pfSense localdomain.png

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

        Sounds like your network is not properly-isolated at Layer 2.

        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)

        E 1 Reply Last reply Reply Quote 0
        • E
          Ev4nsp479 @Derelict
          last edited by

          @Derelict
          Yes! That was it. Totally overlooked a few connections. Thank you kind sir

          1 Reply Last reply Reply Quote 1
          • JKnottJ
            JKnott @Ev4nsp479
            last edited by

            @Ev4nsp479

            Any reason you're hiding the MAC addresses? They're irrelevant beyond the local LAN.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

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