PfSense 2.0-Release dhcp client issue



  • Hello,

    I've attached part of my system log below, but to summarize:  It appears that the dhcp client sends renewal requests directly to the last IP that it successfully received a lease from…every minute or so for up to several hours ... before finally doing a DHCPREQUEST broadcast. It further appears that my ISP's dhcp server only responds to DHCPREQUEST broadcasts and not a direct request to it's IP address.

    I'm not sure what the correct behavior should be on either end, but is there a way to configure pfSense to always do a broadcast at renewal vs. attempting to send a request to the IP of the last dhcp server it got a lease from? Alternatively, is there a way to configure the number of direct dhcp renewal requests it should attempt before doing a broadcast? Or is everything "working as designed"?  :)

    Thanks...

    
    Oct 14 10:56:30 	dhclient[26820]: DHCPREQUEST on em2 to 10.122.176.1 port 67
    Oct 14 10:56:59 	dhclient[26820]: DHCPREQUEST on em2 to 10.122.176.1 port 67
    Oct 14 10:57:42 	dhclient[26820]: DHCPREQUEST on em2 to 10.122.176.1 port 67
    Oct 14 10:58:58 	dhclient[26820]: DHCPREQUEST on em2 to 10.122.176.1 port 67
    Oct 14 11:01:50 	dhclient[26820]: DHCPREQUEST on em2 to 10.122.176.1 port 67
    Oct 14 11:03:59 	dhclient[26820]: DHCPREQUEST on em2 to 255.255.255.255 port 67
    Oct 14 11:03:59 	dhclient[26820]: DHCPACK from 10.122.176.1
    Oct 14 11:03:59 	dhclient: RENEW
    Oct 14 11:03:59 	dhclient: Creating resolv.conf
    Oct 14 11:03:59 	dhclient[26820]: bound to xxx.xxx.xxx.xxx -- renewal in 20813 seconds.
    
    

Log in to reply