Specify the range accordingly. You don't specify a subnet as range but a starting and end IP for the range.

thanks rsw686

The 2 Speedstream 6520s with Firmware Part #:004-E752-AEP Config Part #:003-6045-G0G and the pfsense box were powered down. The SS6520s were then powered up. After the Power, Ethernet, DSL and Internet lights on the SS6520s were illuminated pfsense was powered up. Neither SS6520 registered the pfsense dhclient Hostname. MAC address registered. Both Static and Dynamic addresses were tested on the SS6520s. For your reference the pfsense box has 4    ENL832-TX-RENT PCI ethernet adapters using the RL driver.

This snapshot is already some weeks old. Please upgrade.

The issue being that we cannot process dhcp reconfigurations that fast. At least not every 30 seconds. Try to up the lease time to at least 5 minutes in the dsl modem. That way it should behave a bit better.

Nevermind  ;D Found the answer right here when I searched using some other keywords. http://forum.pfsense.org/index.php/topic,2296.0.html

Hi, You need to get into your modem (via web browser prob, read the docs for the modem) and change it to "bridge mode" then set your pfsense box to dial out via ppoe. I'm new here too but thats my setup

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!