New device doesnt get a DHCP offer



  • I see the packets coming in from the device. (Insteon Hub) but the hub never gets a DHCP address.  when I take it to work it gets one quickly.  i also have 50+- devices in my home that get DHCP quickly.  just this device so far is unable

    am I missing something on the pfsense side?

    [2.4.2-RELEASE][root@firewall.com]/root: tcpdump port 67 or port 68 -e -n
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on vmx0, link-type EN10MB (Ethernet), capture size 262144 bytes
    10:40:47.466650 00:0e:f3:39:f4:5c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0e:f3:39:f4:5c, length 300
    10:40:49.467025 00:0e:f3:39:f4:5c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0e:f3:39:f4:5c, length 300
    10:40:51.467434 00:0e:f3:39:f4:5c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0e:f3:39:f4:5c, length 300
    10:40:53.467728 00:0e:f3:39:f4:5c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0e:f3:39:f4:5c, length 300
    10:40:55.468221 00:0e:f3:39:f4:5c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0e:f3:39:f4:5c, length 300



  • 1. Am thinking too small a lease pool size. 
    2. Never heard of, but is it possible 2.4.2 unable to deal with legacy (too old) DHCP request?
    3. Check correct mask, I assume standard /24?
    4. Try to plug in another, NEW, device OTHER THAN the Insteon.



  • I finally figured it out.  the vlan tagging on my switch was pushing this device to the External interface that didnt have dhcp server configured.  when I changed the switch to the internal VLAN it all worked..  vlans=magic  :)


Log in to reply