Im downloading pfSense-Full-Update-1.2.1-RC1-20080812-2113.tgz 12-Aug-2008 17:56  38M  Right now.

Hopefully this will solve my issue with CP.

Again MANY thanks!

I just booted from CD with
pfSense-20080812-0838.iso.gz from 12-Aug-2008 05:32  (1.2.1)

The Captive Portal is up and running.

753  ??  S      0:00.08 /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
  882  ??  S      0:00.06 /usr/local/sbin/lighttpd -f /var/etc/lighty-CaptivePortal.conf

Clients can connect 'as before'.

Great work - thanks  :)

Thanks, should be fixed in next snapshot

All the iso files are 40 MB, all the embedded img files are 26 MB.

It'll be in the next snapshot.

well it seems to happen when the router is up for 3+ days and the wireless is under heavy load

@jzsjr:

I have refrained from loading squidguard since having installed it with ill results earlier on in the 1.2.1 development.  It is the only package that does not say "platform: 1.2.1."  Just curious if it is working yet.
thanks,
Jim

For 1.2.1 not adapted, but in near 1-2 weeks will fixed.

if you look in Status -> System logs, you may see the alert logged there if it hasn't been too long. Without that alert, there isn't anything here we can look into.

odd, I've cleared various logs countless times and never had a problem with them not coming back. Just did it again on a couple installs, the logs come back fine.

Can you provide a specific, repeatable way to replicate this?

1.2x is bug fixes only, no feature changes. DNS-O-Matic is already supported in 1.3.

If you have a R200 that's running fine on 1.2, I would leave it on 1.2. I would upgrade RC to 1.2-release though. I haven't previously heard of any R200s that run 1.2, must be the RAID that only works in newer FreeBSD versions.

Under the settings for the system log, turn off 'log packets handled by the default rule'.
Then if you still want logging for everything else that's blocked, go to the firewall rules for the WAN interface and create a rule that explicitly blocks everything except udp 67/68 and check the 'log packets that are handled by this rule' option.
Then you could create another rule to block udp 67/68 that doesn't have that option activated.

@sullrich:

We already sync'd btx.S a couple months back.  Unfortunately we are out of time to do such a major change this late in the release cycle.  I have added this patch to 1.3 Alphas however.

Thanks Scott.  I got a USB CD drive to use for the install, so it's not an issue for me anymore - I just wanted to report the issue.

thanks worked perfectly

Please read this tread a few threads down;

Console Upgrade from 1.2 Release Embeded -> 1.2.1 BETA Embeded [Now Working]

http://forum.pfsense.org/index.php/topic,10214.0.html

Try using the Full update file from the console?  Does it work better on upgrades?

The answer is yes by the way!

You might as well stop compiling the embedded update files for a while until you get time to fix them because they just don't work.

same problem, but i fixed it, i tried again using ltest.tgz figuring maybe it was updated but it wasn't, u have to use the latest one from the list

I've seen that order before.  The SVG viewer basically has a z-order greater to our menus.  I believe this was with the SVG plugin.

Fixed!!

I've been away or too busy to test incremental versions, but today I updated to I assume 1.2.1-RC1-20080804-1805 (I used Auto Update) and now the menu spacing/size seems to be fixed too!!

Excellent work!!  :D