enable "nat reflection" at system>advanced in the webgui. This way all portforwarded services will be available by the public IP too. Alternatively you could set up a split DNS szenario that resolves the internal IP of the server for LAN clients.

Resolved.  Several issues I've had were all related to this one problem.

http://forum.pfsense.org/index.php?topic=1582.msg9276#msg9276

Just tried it again, it set the range I told it to.

Hi Hoba. I had also tried this configuration earlier and this makes resolution work nicely but it does not REGISTER the client with the DC (ie. so that the server can resolve the client on the other end.) The only way this happens is by putting the DC as the first DNS which defeats the purpose. Did I miss something?

Services -> DNS Forwarder -> Save

To the original poster:  I am sure you know the rules of running -HEAD.  We are terminating this thread now.

And of course, it still won't make 1.0 regardless of how it's implemented ;)

–Bill

Add DNS entries at services>dns forwarder at the bottom. You also might want to check "Register DHCP leases in DNS forwarder" to make the dynamic Clients resolvable.
And btw, the DNS forwarder does caching too.

No.  It needs upstream routers to resolve from which is obtained either via DHCP or by setting the primary and secondary name servers in system -> general settings.

Unfortunately all interfaces of a bridge have to be up for the other interfaces to work. This is a known limitation.

Ticket filed.  Thanks.

Ah, corrected a typo, the interface IP is now specified as desired above.

Ok, thanks… I'm gonna find a client too it.. - saw it on their www - but thought i could use the built-in  ;)

Anders Hansen

I can confirm this. Beta-3 did not work with MX and wildcard settings, Beta-4 is doing just fine.

Thanks a lot.

Yeah, that is true.  Kinda a catch-22 in that regard, I guess.

Solved:
http://forum.pfsense.org/index.php?topic=677.msg6547#msg6547

Just your system, reinstall.

@Sharaz:

how can i assign more than 1 search domain via DHCP to clients?

I dont think thats possible with the current standard for DHCP.

Depending on your client Microsoft have an article here about a possible work-around:

http://support.microsoft.com/kb/275553/en-us

If the repeater clones his mac for all clients connected to it it can break things anyway. However I don't have a wrt54g to test anyway  ;) but there were a lot of discussions at the m0n0 list concerning that device and problems with captive portal with several different firmwares. If you really want to shut that down you have to change your wireless setup to prevent this. The pfSense only can see a macadress and an IP. If something of this or even both is faked how should it tell which one is the original and which one is the fake? Your problem is a wireless authentication/association problem, not a pfSense problem or at least nothing that can be fixed/workaround from the pfSense side in this setup.