Have a look in the DHCP log: From the web GUI, Status -> System logs then click on the DHCP tab. Depending on how long your system has been up and how many DHCP requests have been serviced you may see the startup messages from the DHCP daemon (dhcpd). You should see "action" records like

Jan 18 19:37:45 dhcpd: DHCPDISCOVER from 00:12:7b:46:e7:65 via vr0
Jan 18 19:37:45 dhcpd: DHCPOFFER on 192.168.211.240 to 00:12:7b:46:e7:65 via vr0
Jan 18 19:37:45 dhcpd: DHCPREQUEST for 192.168.211.240 (192.168.211.173) from 00:12:7b:46:e7:65 via vr0
Jan 18 19:37:45 dhcpd: DHCPACK on 192.168.211.240 to 00:12:7b:46:e7:65 via vr0

I believe there are enhanced dynamic dns features in pfSense 2.0 (compared with 1.2.3). Perhaps what you are looking for is already in 2.0.

(I don't have any experience of pfSense 2.0 yet).

Attempted that, did a flushdns, tried a totally different website that is blocked on my WAN IP, still no success. DNS trace shows that it is using the WAN IP for DNS queries. Any other way?
Thanks

@wallabybob:

I've had another look at this. There is a problem in your LAN firewall rules. When a system is powered up it doesn't have a IP address so the source IP address in the DHCP request will be 0.0.0.0 which is not on your LAN. Hence the DHCP request won't match your first rule.

Sorry, this shouldn't be a problem. I checked against the pfSense book last night and firewall rules to allow DHCP traffic are need on bridged interfaces so I need them on my home network where a wireless LAN is bridged with a wired LAN and I want DHCP service on both wireless and wired LANs. I need firewall rules to allow DHCP on the wireless LAN but I don't need them on the wired LAN.

Thanq you very very much. Your solution is working perfectly.

Best regards

This is not easily possible in 1.2.3, but some people have edited the DHCP server page to accommodate this (search the forum, you might find some patches)

This is already possible in 2.0, and you can set any arbitrary DHCP option number you want.

This has been asked and answered multiple times, really, some searching should have turned it up.

The alternative is to make your WIFI interface your LAN and bridge the wired OPT1 port to it instead of the other way around. It's a little trickier to configure, but you don't have to worry about what is or is not plugged in.

well inability to ping your WAN IP from outside isn't an problem per-se, since that is disabled by default.  can you post your interface config, NAT rules, etc…

Sorry for posting a link to a faulty picture.

Change source port to * and reboot

Thanks guys for the help. Seems I was clicking Lan2 net instead of any, once I did that in the firewall rule all is working now :)

I know it doesnt make much sense to do this the way I am doing it, however my reasons for doing it this way is due to expenses… I know switches are cheap, can be had for as little as $15 in some places, however I only needed one extra port, and its only for a tech bench. Previously I had been disconnecting the cat5 from my test-server to get internet to computers I am reformatting or testing for clients... doing it this way allows me my extra port without having to invest in extra hardware. The machine has 4 ethernet cards plus a wifi anyways, so I was prepared for a dual wan dual lan solution when I built the machine... was thinking ahead :)

Thanks for the feedback!

What do you want to happen? The pfSense DNS to return an internal address for company.ca? If so, on the Services -> DNS page below the three check boxes there is room to specify entries you want to override results from external DNS servers.

Unless I've missed something the behaviour you describe matches the behaviour described on the Services -> DNS page.

@basse:

I have also been in contact with my ISP several times, as I find it ridiculous that they deliver a 100/100 Mbit line to me, but cannt offer me more than 2 public IP´s. But thats how it is, they cant give me more IP´s, so I´m stuck with needing some kind of NAT-solution :(

I recently saw a projection that IP V4 address space would run out in 2011. Possibly there is some form of pressure on ISPs to keep down their requirements for new IP V4 addresses.

@basse:

@wallabybob:

Have you tried using a different type of interface (e.g. fxp, bge, …) on the WAN interface?

How do I do that? As I understand it, em0 gets it´s "name" from the type of NIC I´m using, in other words, the idea is to switch NIC?
The NIC´s are INTEL PRO/1000, so I would find it strange if thats the problem.

Maybe you had some problem specific to a particular interface type (e.g. vr) and changing to another interface type (if you had more than one on your system) might cause an interesting change in behaviour. Maybe changing the WAN interface (e.g. em0 to em1) might cause an interesting change in behaviour.

You say your ISP allocates you two public IPs. Are these on the same subnet? If so, presumably pfSense sees DHCP renewal requests from Linux box. I wonder if that might have some correlation with dhclient exiting.

Yeah, the per-host options I was talking about were the IP address, hostname, and MAC address, nothing more. However, since those are already there it shouldn't be hard to shoe-horn some more directives into that block.

Good point, Jim.  I found this unsettling when I switched from my linux-based firewall to pfsense, but it really does make more sense.

@reason:

I just added a optional wifi interface and I noticed that there is no tab under SERVICES - > DHCP Server.
There is one for LAN but not for OPT1WiFI. Is this normal? How do I configure DCHP for this wireless access point?
I am running pfSense 1.2.2 Thanks!
http://www.kernbits.com/images/pfsense/pfsense_dhcp.JPG

Problem solved:
When When an interface is in bridge mode, there is no dhcp tab for that option.

Just a quick update:

The initial driver update did not fix the problem. However, I got another driver update through Windows Update in the first week of December which resolved the problem. :)

Thanks,
Jens