A fix for this is in commit re1f27ca. The next snapshot should be OK.

Correct, yellow is < 5 minutes change.

This is fixed. It turned out that our racoon port was building without the admin socket.

A better question is when will 1.23 be released for good.  I need to deploy a couple embedded firewalls in the field and I'm just waiting now.

Fixed in pfSense-1.2.3-20090328-0054.img.gz

Thanks!  :)

Just a few niggles,

1.) Loose the jiggly buttons  - I hate them.
2.) Cant seem to add a range of addresses to the whitelist i.e. 81.103.221.0/24 I had to add each ISP server manually some 18 servers.
3.) Why don't things that have been auto white-listed appear in the Spamd White list?
4.) Would be nice to tick a box so that the Spamd database would just show ALL the GREY items I range from 13 to 35 at any one time but every time I'm over 25 I have to adjust the filer limit.
5.) Date and time stamp the Spamd database, I still to this day don't know if it runs top to bottom, or bottom to top.

I was always led to believe spamd listens on 127.0.0.1 so should work on multi wan but if I do a shields up port scan https://www.grc.com/x/ne.dll?bh0bkyd2 port 25 is only open on the wan, maybe its just not opening up port 25 on the other interfaces.

I does kind of work and is a worthy addition to pfsense.

Cheers

Press enter to access the shell. In /etc/rc line 43, change the line from:

if [ "$hideplatform" = "true" ];

to

if [ "$hideplatform" = "true" ]; then

Trace file can be opened in WireShark (you can only attached certain file types)
Trace was taken from an XP SP3 client with no client firewall attached.
The capture looks good.  The domain suffix is seen and from my understanding is needed to register the client name in the forwarder.  U also can see the DHCP lease that contains the client name:

lease 192.168.20.198 {
  starts 3 2009/03/25 11:35:37;
  ends 3 2009/03/25 13:35:37;
  binding state active;
  next binding state free;
  hardware ethernet 00:0c:29:21:8f:20;
  uid "\001\000\014)!\217 ";
  client-hostname "WinXPPro";

Thanks

This could be a side effect of a long-standing bug that happens sometimes, leading to empty and undeleteable openvpn server and client definitions.

If you view the OpenVPN config, and see an empty line that just says "No" under disabled, and as the e/x at the end, that's probably the case. I hit this the other day but haven't investigated it further.

Hello there !
These are good news to hear!
I was looking for the exact same thing..
Do you think i should go for a v.2 prerelease, use the last 1.2.3 prelease or use the prelease Slam mentioned with the above modifications?
(1.2.3-PRERELEASE-TESTING-VERSION built on Mon Jan 26 16:38:45 EST 2009)?

Do you think that it would work if i configure the wan interfaces as pppoe with static ip's?

Hi
Gui back with pfSense-Full-Update-1.2.3-20090320-0534

True, I just upgraded and everything is fine now.

Cheers

yah, that would be awesome…..is it possible to compile custom kernels for pfsense like you do with freebsd or am i totally at the devs mercy?

Looks like this is something specific to your machine…

I've installed 1.2.3 and 2.0 Alpha on several different machines including VMWare Server 2.0 and ESX 3i and not had issues like that...

Thank you very much cmb.