@mgiammarco:

… or if I have to copy them by hand.

You could always backup the "DHCP Server" area on the "Diagnostics: Backup/restore" page, modify the "Failover peer IP", then restore that into the failover pfSense.

I have DHCP enabled on my LAN interface, OPT1 and OPT3 (the latter a wireless interface).

DHCP assigns addresses from the correct range on all these interfaces.

I'm running pfSense 1.2.3-RC2 built on Tue Jun 16 04:58:42 EDT 2009

What version are you running?

On my pfSense box the dhcpd configuration file (/var/dhcpd/etc/dhcpd.conf) specifies addresses based on subnets rather than interfaces so, if your box follows the same pattern, its hard to see how dhcpd could get confused as to which addresses apply to which interface.

Do you have any static DHCP assignments? (Possible duplicated static assignments?)

Have you checked that the DHCP address assignments are actually made by the server you expect?

I have the same problem. At a hindsight, it seems to be related to the access points that I have connected on the LAN side and the DHCP starts working again once I disconnect them - but that doesn't make any sense - how can a client prevent a DHCP server from working? Someone setting up their own DHCP server?

Any pointers?

You probably just need to run dhclient again if the second attempt really does pull the proper addresses.

You can try going to Status > Interfaces, then click Release, then Renew.

tinydns is authoritative only, you want dnscache (though they're both part of the same project). I find that djb's stuff is just plain weird though and tried it, but wouldn't use it myself. I'd just go with BIND, though it'll be a bit more resource hungry.

Or just use 4.2.2.1…

@kpa:

The "Enable registration of DHCP client names in DNS"  feature works only with the built in DNS forwarder (dnsmasq) AFAIK so it can't be used to register the hostnames in an external DNS server.

I don't think this is correct.  The "Enable registration of DHCP client names in DNS." option is a flag which enables the "ddns-update-style interim" configuration option for the DHCP server.  See /var/dhcpd/etc/dhcpd.conf.

The "Register DHCP leases in DNS forwarder" is a separate option that tells dnsmasq to parse the DHCPD leases file and add assigned leases to the dnsmasq database.

The two options are completely independent.  (This is for 1.2.2.)

I have not attempted to use the "Enable registration of DHCP client names in DNS." option, so can not comment on whether or not it actually works.

http://forum.pfsense.org/index.php/topic,11159.0.html
You mean create dsnmasq configuration like above link?
I use this configuration with 1.2.3RC2 as well. Now I don't need to change the startup process order.
I did change the two inc files in "/etc/inc".
"system.inc" to add Opendns to the dns nameservers in "/var/etc/resolv.conf"

"pfsense-utils.inc" to point to "/var/etc/resolv.conf"
(or else the dashboard will point to /etc/resolv.conf (symb.link to /var/etc/resolve.dnsmasq –> 127.0.0.1) ).

function get_dns_servers() { $dns_servers = array(); $dns = `cat /var/etc/resolv.conf`;        /**** CHANGED to /var ****/

I need to do this each time I install a newer full update build of the pfsense 1.2.3RC2 release

Thank you both for the reply,

I configured it now manually as a different radius client, this also works for now.
I'll wait for the stable 2.0 release and see then if I can get it to communicate with the controller.

It's a Ruckus 7942. It detects the controller normally by broadcast (on the same subnet)

A plan B is the 43 option (this is undocumented, their support staff sent me information about it)
It supports DNS, but you need to buy the flexmaster software, but that would be a substitute for the controller, so a waste of money, and you'd need a server running for it.

greets

Mike

Ask Paetec to config their Adtran router to bridge mode.  Then set the WAN to a static public IP address that they wil provide.

On my home LAN I have every system assigned an IP address by DHCP on pfSense.

A number of my systems are assigned the same address every time by tieing their MAC address to an IP address in the DHCP Server configuration.

You haven't said why you want to have the Linux systems with static addresses so I can't address that. On those systems with static IP address (as seen by the system) you need to specify by the gateway and the DNS server. If you use DHCP this stuff can be changed in one place (the DHCP server) rather than on multiple systems.

System > General Setup
Uncheck "Allow DNS server list to be overridden by DHCP/PPP on WAN"

As long as that is checked, the DNS servers received by PPPoE will be used by the router. If that is unchecked, then the values you type in will be used.

pfSense is a firewall. There can sometimes be good reason to place tight restrictions on traffic passed.

Depending on your environment, "work" might mean more than "pass any traffic", it might mean "block certain types of unexpected traffic".

Hi, thanks for replying.

Since then I discovered that the new 10.6 version of Mac OS X has the exact same behaviour
I did try to set up the network settings manually but unfortunately the issue still exists.

I found this thread explaining that the base of the problem is the ".local" tld used in our LAN. It is used by the "Bonjour" protocol.

I am going to change my LAN tld into something not used by some fancy protocol (like ".lan" or something)

I keep in touch.

So is there a way to hand code this in the config?

Well i wouldn't consider a forum as a form of documentation…

@deanflyer: If there is something you think needs documentation:
http://doc.pfsense.com

You can apply for an account on the wiki by sending an email to one of the devs, or send the content of what you wanted added to someone with an account.
(devs or me).

http://faq.pfsense.com
–> http://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks%3F