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

    Feature or Bug: Wifi client obtaining DHCP address without static ARP mappings

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    1 Posts 1 Posters 802 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.
    • W
      wbedard
      last edited by

      Here's the short version.  I just upgraded my router (x86-based pc, intel wired NICs, Ralink USB WiFi NICs, Atheros internal WiFi NIC) from 2.1.5 to latest beta of 2.2 and everything seems to have gone well.  I had finished installing a new USB Wifi interface (192.168.3.0/24) and configured the standard firewall rules and the DHCP server, including adding 1 client using a static ARP entry and enabling "deny unknown clients".  I confirmed that this client could successfully connect and transfer data.  I later tried to connect another client, which was already connected to a similar interface (10.0.1.0/24) on a different router, to this new interface but forgetting to first add the new entry in the DHCP server for the new interface.  Surprisingly, the client connected just fine.  Some important additional information to know is that all of my WiFi clients already have similar static ARP mappings on the other interfaces on this router, which all work fine.  I have included the relevant excerpt from the DHCP log after the "unregistered" client got connected.  Any ideas on whether this is a feature or a bug are welcomed!

      Dec 7 15:16:21 dhcpd: DHCPACK on 192.168.3.2 to xx.xx.xx.xx.xx.xx (android-717996b4aabbcf5b) via run0_wlan0 
      Dec 7 15:16:21 dhcpd: DHCPREQUEST for 192.168.3.2 (192.168.3.1) from xx.xx.xx.xx.xx.xx (android-717996b4aabbcf5b) via run0_wlan0 
      Dec 7 15:16:21 dhcpd: DHCPACK on 192.168.3.2 to xx.xx.xx.xx.xx.xx (android-717996b4aabbcf5b) via run0_wlan0 
      Dec 7 15:16:21 dhcpd: DHCPREQUEST for 192.168.3.2 (192.168.3.1) from xx.xx.xx.xx.xx.xx (android-717996b4aabbcf5b) via run0_wlan0 
      Dec 7 15:16:21 dhcpd: DHCPOFFER on 192.168.3.2 to xx.xx.xx.xx.xx.xx (android-717996b4aabbcf5b) via run0_wlan0 
      Dec 7 15:16:20 dhcpd: DHCPDISCOVER from xx.xx.xx.xx.xx.xx via run0_wlan0 
      Dec 7 15:16:19 dhcpd: DHCPNAK on 10.0.1.12 to xx.xx.xx.xx.xx.xx via run0_wlan0 
      Dec 7 15:16:19 dhcpd: DHCPREQUEST for 10.0.1.12 from xx.xx.xx.xx.xx.xx via run0_wlan0: wrong network. 
      Dec 7 15:16:19 dhcpd: DHCPNAK on 10.0.1.12 to xx.xx.xx.xx.xx.xx via run0_wlan0 
      Dec 7 15:16:19 dhcpd: DHCPREQUEST for 10.0.1.12 from xx.xx.xx.xx.xx.xx via run0_wlan0: wrong network. 
      

      R/
      wbedard

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