sorry for the delay in writing back Ye hit the nail on the head i removed 50 address at the start of the range and can now use them for static addresses Thanks a million for all ye're help

I've been so busy I haven't had time to get back to this. I spent a LOT of time I didn't have dealing with this, then, about two days ago, I tried to go back to the original system for DNS/DHCP and suddenly none of the computers could communicate at all – not even by IP address! I pulled all the CAT5 from the main switch, except for the connection between my iMac and my firewall and they started talking and DNS was working.  Then I added one more computer, it worked, and I added the others in steps and now it's working. Do systems in a LAN talk with each other or cache information that others can get?  Because now it's working perfectly, but it took pulling almost every system off the LAN to make it work.

you need to install the tinyDNS package for pf to be a dns server in the way you want.

I've done it in pfSense 2 Beta4. Just in short: First, it's not send vendor-class-identifier but send dhcp-class-identifier. This is different from other dhcp clients, but using dhcp-class-identifier does send option-60. You may also need other options. Just compare dhcp requests with a sniffer… To get it persitent, you need to modify the /etc/inc/interfaces.inc file. If you only have one external interface you need to find the place where it writes the dhclient_wan.conf file. (this differs from version to version!) Here you should find the lines that write:         $dhclientconf .= <<<eod<br>interface "{$wanif}" { timeout 60; retry 1; select-timeout 0; initial-interval 1;</eod<br> You may add any line you like there. If you have, like me, one WAN interface for internet and another going to the IPTV network and you only want the extra dhcp options on that one, you need to add some intelligence with something like: if ($wanif == "re2") { ... (your modified setup) else { ... (a copy of the original setup) } You will make any modifications at your own risk! Make backups! One last thing, this modification will not survive an pfSense update!

Ah.  I did not specify www as the host.  Works now!  Thank you!

Thank you very much sir, I am in your gratitude. That worked beautifully, You can consider this post closed.

YOU DID IT!!! I had never configured a NAT rule, so I never checked them.  However, it appears that the firewall had configured a NAT rule for external management.  I deleted that rule, and IT WORKS!!!! Thanks for taking the time and expending your neurons to help me.

Anyone have a copy of dhclient from 8.0 that they'd be willing to send me? Thanks in advance, and much kudos to cb831! edit: I got impatient so I downloaded the 220MB iso to extract the 77K file ;) It appears to be working, I'm now getting: Aug 16 17:30:35 dhclient[63382]: bound to 99.99.207.xxx – renewal in 300 seconds. Aug 16 17:30:35 dhclient[63382]: DHCPACK from 99.99.206.xxx Aug 16 17:30:35 dhclient[63382]: DHCPREQUEST on vlan0 to 10.0.0.1 port 67 Instead of: Aug 16 17:11:03 dhclient[18353]: bound to 99.99.207.xxx – renewal in 300 seconds. Aug 16 17:11:03 dhclient[18353]: DHCPACK from 99.99.206.xxx Aug 16 17:11:03 dhclient[18353]: SENDING DIRECT Aug 16 17:11:03 dhclient[18353]: DHCPREQUEST on vlan0 to 10.0.0.1 port 67 Hopefully it won't be dropping now.

also, bug i have with 1.2.3 that almost after every apply on DHCP server one interface freezes (it just do not pass network traffic), is gone with 2.0… or at least i didnt have problem yet

Well, I did a clean install of 2.0 and it does seem to work, although the manual entries in the config.xml for full-duplex and 100baseTX still seem to be required to get the system to boot normally.  No shell script needed though. Thanks!

I know this is an old thread but here is a rudimentary way to see the number of active leases. grep -c "binding state active" /var/dhcpd/var/db/dhcpd.leases That should output the number of leases at active status.

Hi, thankyou for unlock topic. Hi infratek, did you resolve? I've resolved overriding domains in "Services -> Dns Forwarder" for domains managed by TinyDns. The section is "Below you can override an entire domain by specifying an authoritative dns server to be queried for that domain". I've insert 127.0.0.1 inside field "IP address of the authoritative DNS server for this domain". I know it is not the best solution, but it works and I don't find nothing better than this. So this is my configuration in order to have a single machine with authoritative dns and dns forwarder: "General Setup -> Dns Servers": configure external dns ips "Services -> Dns Forwarder": enable dns forwarder and configure forwarded hosts and forwarder domains (the ones managed by TinyDns): Configure "IP address of the authoritative DNS server for this domain" to 127.0.0.1 "Dns Servers -> Settings": configure Binding IP Address to 127.0.0.1 and enable dns forwarder "Dns Servers -> Add/Edit record": configure zones The only thing that doesn't work is dns resolution for CNAME records. I hope this will be usefull for other users. Thankyou, emanuele

@jimp: Not a stupid question, just an FAQ without an answer other than "when it's ready" :-) Getting closer every day, but not quite there. ….. i see the FAQ now...... when it's ready is very vage.....But i will wait

So… when I didn't find anywhere in the webgui to put dhcp options (option x "y";) I took some time and added it to my 1.2.3-RELEASE. I needed "root-path". Well I completed it, and I'm happy with the outcome, but I wish I had searched this forums some more, since this is apparently already in 2.0. doh Anyway, if anyone would like the /usr/local/www/services_dhcp.php & /etc/inc/services.inc files I will post them. (only minor changes to services.inc -file, line 284-288) if (isset($dhcpifconf['dhcp-option'])) { foreach($dhcpifconf['dhcp-option'] as $key => $dhcpoption) { if ($dhcpoption != "") $dhcpdconf .= " option $key "$dhcpoption";\n"; } } Screens: [image: dhcp1.png] [image: dhcp2.png] [image: dhcp3.png] Files: removed edit: fixed links edit2: removed links, found some bugs in the code i made. go get pfS 2.0

sorry forgot to mention there is a switch after the server, both network connected to the switch.  what confuses me the client was able to connect all the time to this network, when she started to face this problem, i thought maybe she updated her windows 7 and the driver wasn't good to connect to my AP11b access points so i formated her net-book with fresh installation of win7 but no luck. i also have another client just got herself a new net-book with windows 7 installed not able to connect to 11b so i had to give her a usb wireless so she managed to connect now.