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

    DHCP .. behaving weirdly with VLANs (bug?)

    DHCP and DNS
    3
    4
    742
    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.
    • G
      gonzague
      last edited by

      Hi,
      I have only noticed this since I use 2.2.1-RELEASE but it was maybe happening before :
      If one of my devices get an IP from pfsense, for example on VLAN3 I have the 192.168.3.0/24 range .. then a device on vlan 3 gets 192.168.3.28

      Well when this device connects to VLAN1 which offers 192.168.100.0/24 .. it keeps the 192.168.3.X IP … I've seen this behaviour repeating on an iPhone, a virtual machine .. etc .. and it seems like a bug to me

      Anyone else it is happening to ?

      thanks!

      Gonzague

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

        It's not a bug.  It works fine.  Your VLANs aren't configured how you think they're configured.

        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)

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          When dhcpd gets a lease request for the wrong subnet, it'll send a NAK, and the client will request a new IP. If you're not getting a NAK for the 192.168.3.x IP in that scenario, it's because of a VLAN config problem that sends the DHCP requests via the wrong VLAN. If the DHCP server is actually renewing the 192.168.3.x lease, the DHCP request came in on the interface/VLAN of the 192.168.3.x network and not the 192.168.100.x network.

          1 Reply Last reply Reply Quote 0
          • G
            gonzague
            last edited by

            Ok thanks guys ! will investigate further :(

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