I just thought I would add a note here (since this thread does show up at the top of a google search) that there is now a 1.2.3-RC3 package under the regular download site linked from the pfsense homepage.

@900mhzdude:

what do you mean you still see the lock file in /tmp?
do you mean you see it in the tmp folder but is not doing any harm…or being a pain?

Sorry, been busy.  Since upgrading to 9-22 everything has been good.  No reports of login problems, no slowdowns, and I can always get to the web admin.  Looks like it's fixed.

On a side note my Ubnt PS2 just got a fix for PPPoE.  Connected right up no problem.  So both my PPPoE customers and my CP customers are happy… finally! ;-)

I guess I'm not looking for PPS capability (no serial gps) but wanted to plug up a usb model we have laying around the office and see what happens.  I was curious if anyone had done this using pfsense already and could save me some time. 
thanks,
Jim

Well, I can make some attempts to eliminating the hardware (per se) by swapping the CF card into another Alix board, and seeing if I still get the pauses there. In addition try a different CF card altogether (a real SanDisk) as opposed to the leftovers I've been using, and the ones I've gotten directly from pcengines. I seriously doubt this is the issue, though. I might believe the hardware, as I did have MASSIVE problems with 2.0, where the box would not stay up (i.e. panicked) after about 12-16 hours running…...

Package "rate" solved this for me.

I too have with a pcchips, i can´t resolve, i change for intel moterboard and ready.

Yo también tenía el mismo problema con una placa pcchips, no me informaba correctamente la geometría del disco duro, probé con otro disco y el mismo problema, estuve todo un día cambiando las opciones del bios y nada, así que, como no podía perder mas tiempo tuve que cambiar de placa por una intel, y funcionó a la perfección

Disculpen Uds pero mi ingles es muy malo
My ingles is very bad

It may be related to the changes made when attempting to fix this ticket:
http://redmine.pfsense.org/issues/show/88

Finally getting a chance to work on this again (this is a project at work, so its get time when I have time to spare :)).

Flashed the slightly reduced images onto my "2GB" cards…
Successfully!
About to overwrite the contents of disk 2 with new data. Proceed? (y/n) y
2001194496/2001194496 bytes written in total

Boot fine as well.  Thanks for taking the feedback and working with it, it is appreciated.

Some cards don't work right in auto for some reason.

As we find packages that do not work, they are tagged as such and removed from the list.

Lots of packages do work (Dashboard, blinkled, many others) but some do not.

I have been working on Avahi. The install process crashes the whole box. After a reboot it seems to work though.

If you encounter a package that doesn't work, it might be wise to open a ticket in redmine and report it.

That's what the prerelease/RC stage is all about… shaking out these bugs :)

@pakjebakmeel:

That's new. Just curious, is there a list of NanoBSD compatible packages?

Not really, as packages are found that do not work properly, they are excluded from showing up for NanoBSD.

This kind of swapping is due to the probe order being changed somehow. IIRC, FreeBSD always probes the same way, but this can be influenced based on BIOS settings.

Typically it's BIOS or hardware related, but it would likely happen regardless of the OS in your case.

Shamfully it hasn't fix it I have niced loads of tunnels for the same thing though.

87.83.24.114  86.54.251.XX  ESP  d122cb5e  aes-cbc  hmac-sha1 
87.83.24.114 86.54.251.XX ESP d122cb58 aes-cbc hmac-sha1
86.54.251.XX1 87.83.24.XX ESP 0e42e5f2 aes-cbc hmac-sha1
86.54.251.XX1 87.83.24.XX ESP 019b2195 aes-cbc hmac-sha1
86.54.251.XX1 87.83.24.XX ESP 05f7e2e1 aes-cbc hmac-sha1
86.54.251.XX1 87.83.24.XX ESP 016d002b aes-cbc hmac-sha1
86.54.251.XX1 87.83.24.XX ESP 0dcfda6a aes-cbc hmac-sha1
86.54.251.XX1 87.83.24.XX ESP 0295d20c aes-cbc hmac-sha1
86.54.251.XX 87.83.24.XX ESP  0b619838  aes-cbc  hmac-sha1

@justsomeguy6575:

I'm sorry, to be honest I didn't do a search…. I just looked at the subject of the first page of posts.  I do normally try and do a search, not sure why I didn't this time.  Anyhow I just found it strange because I have updated to several 1.2.3 releases in the past and never seen that message before.

I've been using pfsense for a while now.  One at a small office and one at home.  Absolutely love it.  I've tried many different firewall solutions like ipcop, smoothwall, monowall, and clarkconnect(seemed convenient at first but too many security problems with running a server on the same box).  This is the all around best out there.  So just want to says thanks to all the developers.

See the thread I mentioned. Gloomrider posts:

Signature check is new, correct?  This is the first time I've seen this.

Then CMB posts:

New on nanobsd, yeah. It was broken for nanobsd previously.

@fastcon68:

I really don't see this as a major issue.  I you create a standard image of say 20 GB with Ghost and serveral other disk imaging products that is going to shrink down quite a bite.  We as a group just need to pick a standard and stick to it.

RC

Or you could do a Quick Install and then copy your own image.