Empty dhcpd.log



  • 
    8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #1: Thu Nov 18 23:20:46 EST 2010     sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386
    
    

    Dhcpd don't log in dhcpd.log/system.log client request.



  • Probably dhcpd doesn't see the request (blocked by firewall? check firewall log; connectivity problem?)

    Packet capture can be useful to verify DHCP request is getting to your pfSense system.



  • Please clarify "empty dhcpd.log". Does that mean it contains nothing at all OR that it doesn't contain any DHCP request information?

    How are you examining the dhcpd log? web GUI? Shell command? If shell command, what command?



  • @wallabybob:

    Please clarify "empty dhcpd.log". Does that mean it contains nothing at all OR that it doesn't contain any DHCP request information?

    How are you examining the dhcpd log? web GUI? Shell command? If shell command, what command?

    
     tcpdump -vneti re0 port 68
    tcpdump: listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
    00:15:f2:a7:45:4d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
        0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:f2:a7:45:4d, length 300, xid 0xc60d8a5c, Flags [none]
    	  Client-Ethernet-Address 00:15:f2:a7:45:4d [|bootp]
    00:1c:c0:c4:da:44 > 00:15:f2:a7:45:4d, ethertype IPv4 (0x0800), length 344: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 330)
        192.168.0.254.67 > 192.168.0.10.68: BOOTP/DHCP, Reply, length 302, xid 0xc60d8a5c, Flags [none]
    	  Your-IP 192.168.0.10
    	  Client-Ethernet-Address 00:15:f2:a7:45:4d [|bootp]
    
    
    
    clog -f dhcpd.log
    NOTHING
    
    ls -la
    total 1934
    drwxr-xr-x   2 root  wheel     512 Nov 19 18:58 .
    drwxr-xr-x  26 root  wheel     512 Nov 19 05:51 ..
    -rw-------   1 root  wheel   65535 Nov 22 16:33 apinger.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 dhcpd.log
    -rw-r--r--   1 root  wheel    7751 Nov 19 18:57 dmesg.boot
    -rw-------   1 root  wheel  512144 Nov 23 01:04 filter.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 ipsec.log
    -rw-------   1 root  wheel   50688 Nov 19 18:57 l2tps.log
    -rw-r--r--   1 root  wheel      28 Nov 23 00:59 lastlog
    -rw-r--r--   1 root  wheel    7541 Nov 23 00:08 lighttpd.error.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 lighttpd.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 ntpd.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 openvpn.log
    -rw-------   1 root  wheel   50688 Nov 19 18:57 poes.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 portalauth.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 ppp.log
    -rw-------   1 root  wheel   50688 Nov 19 18:58 pptps.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 relayd.log
    -rw-------   1 root  wheel   65535 Nov 19 18:57 slbd.log
    -rw-------   1 root  wheel  512144 Nov 23 01:03 system.log
    -rw-------   1 root  wheel     328 Nov 19 18:58 userlog
    -rw-------   1 root  wheel   65535 Nov 19 18:57 vpn.log
    
    arp -a 
    ? (192.168.0.8) at 00:13:a9:5f:d8:82 on re0 expires in 1200 seconds [ethernet]
    ? (192.168.0.10) at 00:15:f2:a7:45:4d on re0 expires in 950 seconds [ethernet]
    ? (192.168.0.253) at 00:0c:42:3a:d7:52 on re0 expires in 1162 seconds [ethernet]
    
    


  • Looks like a bug. That interaction should have produced a couple of dhcpd log entries.



  • I can confirm that. DHCP-log is empty. Seen with Web-IF.



  • Same here ….



  • igor and Macom2007 : What pfSense builds are you using?



  • mine's empty too (web interface system log/ dhcpd log). But I'm still on Nov 21 02:37:38 EST 2010 .
    Will upgrade tomorrow.



  • At the moment its Nov, 22 i386 release. I'm updating daily. Its now a while but i didn't look every day on it. Hope that helps.


  • Rebel Alliance Developer Netgate

    Empty here too, though the config file has the proper syslog facility set, and syslog.conf is looking for the right syslog facility as well.



  • Fixed in 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #1: Sat Dec  4 01:43:08 EST 2010  :D

    
    clog -f dhcpd.log
    Dec  5 08:40:08  dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
    Dec  5 08:40:08  dhcpd: Copyright 2004-2010 Internet Systems Consortium.
    Dec  5 08:40:08  dhcpd: All rights reserved.
    Dec  5 08:40:08  dhcpd: For info, please visit https://www.isc.org/software/dhcp/
    Dec  5 08:40:08  dhcpd: Wrote 0 deleted host decls to leases file.
    Dec  5 08:40:08  dhcpd: Wrote 0 new dynamic host decls to leases file.
    Dec  5 08:40:08  dhcpd: Wrote 5 leases to leases file.
    Dec  5 08:40:08  dhcpd: Listening on BPF/re0/00:1c:c0:c4:da:44/192.168.0.0/24
    Dec  5 08:40:08  dhcpd: Sending on   BPF/re0/00:1c:c0:c4:da:44/192.168.0.0/24
    Dec  5 08:40:08  dhcpd: Sending on   Socket/fallback/fallback-net
    Dec  5 08:41:15  dhcpd: DHCPREQUEST for 192.168.0.10 from 00:15:f2:a7:45:4d via re0
    Dec  5 08:41:15  dhcpd: DHCPACK on 192.168.0.10 to 00:15:f2:a7:45:4d via re0
    
    

Log in to reply