Now that I actually went and looked at the log, yeah mine is doing the same. Uptime is 13 days 11:15 hours on 1.0.1-SNAPSHOT-11-25-2006. Yeah I know that snapshot is older, but I don't think things changed with DHCP logging. Anyways the last entrys in my log are Jan 3 15:20:27 dhcpd: DHCPACK on 10.10.1.140 to 00:0c:29:6b:d5:da via fxp1 Jan 3 15:20:27 dhcpd: DHCPREQUEST for 10.10.1.140 from 00:0c:29:6b:d5:da via fxp1 Jan 3 15:13:49 dhcpd: DHCPACK on 10.10.1.150 to 00:0c:6e:40:53:5d via fxp1 Jan 3 15:13:49 dhcpd: DHCPREQUEST for 10.10.1.150 from 00:0c:6e:40:53:5d via fxp1 Jan 3 15:04:02 dhcpd: DHCPACK on 10.10.1.143 to 00:13:ce:42:69:ac (gil) via fxp1 So its Jan 15th 11:26 right now. That means that the box was started on Jan 2 right around this time. So DHCP logging worked for 1 day.

Hm, all boxes are ping-able via hostname from both linux and windows but neither are going to pfSense's web interface by typing https://pfSense (or whatever I named it  ;) )…wonder what I'm doing wrong....i'll keep dinking around with it. I'm glad to have the hostnames pingable however...thanks for the help!

anything else i can check?

The dns forwarder can't make use of loadbalancing. it always will use the main wan. this means if wan is down the dns forwarder won't be able to resolve dns anymore. you can solve this by adding a static route to one of the used dns-servers/32 via the opt-wan.

hopefully these steps will work for the DHS client too. i having the same trouble. *edit nope it doesn't update_file.sh /etc/inc/dyndns.class update_file.sh: Command not found. 4 18:28:22 php: /services_dyndns.php: Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Current Service: dhs Jan 4 18:28:22 php: /services_dyndns.php: DynDns: DynDns _checkStatus() starting. Jan 4 18:28:22 php: /services_dyndns.php: Curl errror occured: Couldn't resolve host '{$server}{$port}' Jan 4 18:28:22 php: /services_dyndns.php: DynDns: DynDns _update() starting. Jan 4 18:28:22 php: /services_dyndns.php: DynDns: cacheIP != wan_ip. Updating. Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Cached IP: 0.0.0.0 Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Current WAN IP: *.*.*.* Jan 4 18:28:22 php: /services_dyndns.php: DynDns: _detectChange() starting. Jan 4 18:28:22 php: /services_dyndns.php: DynDns: updatedns() starting Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Running updatedns()

Hi Would be great to see support for custom options. We also need some (e.g. slp-directory-agent). Our company may also provide a bounty for this feature. Regards, Reto

Add the item in the <system>xml subset.  Not sure about the filename.</system>

That sounds very useful indeed. I appreciate your quick response. Thank you!

Thanks  :)

If it happens again I'll let you know what is in the log files.  Thanks!

ok, thanks ! i still have a problem with the WAN link, it droppes the IP and and doesnt renew it  :( but i have read that it is a common problem for some people.

Doing a powercycle will dump systemlogs. Also without knowing in which state the system is now (no IP at WAN for example) it's hard to troubleshoot.

until now i did not have a single problem with that dns-forwarder and believe me: it is used like hell here :-) i have 500 clients behind out own 2 DNS-Servers and both of them use pfSenses DNS forwarder as the next DNS-hop… it runs... no crashs... use it and have fun !!!  :D

Just for reference, further investigation shows that the PC in question can connect quite normally and then loses its connection after a few minutes. Reboots at that time don't get an IP address, but if the PC is left for a while and then rebooted it'll work for a bit before losing connection again. This is a bit different to what I was led to understand was the case originally… Seems to me this is actually a hardware fault (probably heat induced) and it's just coincidence that the DHCP log stopped for some reason.

Nope..it doesn't work…seems that it has already cached the ip and doesn't even connect to no-ip to update it..is any way to delete the cached ip from pfsense so it can connect to no-ip and update it??

I will get this committed. I have done testing and there should be no bugs. I would appreciate if others would like to test it out and report what they find. To install exectue the following via the webgui command prompt. fetch -o - "http://wgnrs.dynalias.com:81/pfsense/devel/dhcpstatic.tar.gz" | tar xfz - -C / If your running this on an embedded box pull up the serial console or ssh into the box. Select option 8 shell and execute the following. /etc/rc.conf_mount_rw fetch -o - "http://wgnrs.dynalias.com:81/pfsense/devel/dhcpstatic.tar.gz" | tar xfz - -C / /etc/rc.conf_mount_ro Afterwards go to the services->dns forwarder page and check "Register DHCP static mappings in DNS forwarder". Click save. Then go to the services->dhcp server page and fill in the hostnames. Apply the changes and your good to go.

it is true that I have a wireless WDS network using linksys and buffalo routers. but this problem happens when i use access point in client mode with or without WDS. anyway ddwrt firmware works perfectly with pfsense

If you lose the WAN IP and use natreflection to access the DMZ it won't work anymore as you lost the IP that gets reflected. You maybe even lose DNS to resolve the WAN IP first if it is a dyndns account. That makes sense. I'm still thinking something with your WAN is wrong or maybe even with your ISP.