FWIW it seems to be the same problem with a snapshot from the last few days.

thank you for your time and help  ;D

It's normal on many systems for nothing to be logged there other than at boot time. The syslogd line is normal, that's supposed to show up when you clear the logs. I just cleared the logs, and saved and applied changes on a load balancer entry to force it to poll, and it did log its polls. Your system probably isn't running anything that will log there with any frequency.

Seth changed the text on this to reflect what it really does.

The 6.3-based 1.2 has upgrade issues apparently, the official 1.2 release does not.

This is no different than 1.2.  Nothing new here.

Good work! Yes it's now working with the new update or reboot, I don't really know! Thanks for your good work! Regards

This is normal for snapshots as the /etc/version is different from what we check.

@databeestje: I just attempted a fix in CVS, can you please try the next 1.2.1 snapshot build? Thanks. Hi Seth, Yup - looking good (with Sun Aug 17 23:20:33 EDT 2008).  I got it configured to use the CARP IP now.  Thank you! I didn't test the failover of IPsec, but I didn't have problems with that in the past (or do anything special) on my custom nanobsd based platform. - ask

@cmb: that should work fine. Hmn - no go. In the logs it reports success for the servers in the pool, but requests to port 80 on the Virtual Server IP are timing out (1.2.1 snapshot from Aug 12).  It seems to do that no matter which network I take the IP for the Virtual Server from.  Yes, I did open a firewall rule on WAN for the VS IP. ask

I have opened a ticket on 2008/08/07….. http://cvstrac.pfsense.com/tktview?tn=1797,33

Thank you, I can ping from the wan and  access the port too. Kenny

I read that it is unmaintained. If that means nothing will be done about issues then it (and similarly fated) packages should be pulled from 1.2.1 IMHO. ryts

Squid (package 2.6.21) GUI: Proxy server: Cache management Memory replacement policy : any option selected here won't stick in config "The memory replacement policy determines which objects are purged from memory when space is needed. The default policy for memory replacement is GDSF." Other options not be saved in the /usr/local/etc/squid/squid.conf (stays heap GDSF) # Allow local network(s) on interface(s) acl localnet src  192.168.0.0/255.255.255.0 uri_whitespace strip cache_dir aufs /var/squid/cache 1000 16 256 cache_mem 128 MB maximum_object_size 16384 KB minimum_object_size 0 KB cache_replacement_policy heap LFUDA memory_replacement_policy heap GDSF <-----!!!! offline_mode off cache_swap_low 90 cache_swap_high 95 # No redirector configured

:o Noooooooooo!  :'( I can't write my router off just yet, I've only just finished building it. Joke's aside, if 'patches' are released for FreeBSD 7 will the latest ones be incorporated in to 1.2.1-Release? or is the version of 7 you start with the version of 7 you go to press with? i.e. will the version of freeBSD 7 that comes with 1.2.1 be the same as the one that comes with 1.3. Regards EDIT: PS, would the D-link driver going AWOL also lock-up my on-board 1Gb Realtek?

Run "rm /boot/kernel/pfsense_kernel.txt" and you'll have the kernel selection box back. I very seriously doubt if it's SMP vs. uniproc kernel related.

Yeah it should be.  Not much has changede in CP except for Mark Cranes speedup tweaks for Lighttpd.

Please email me a copy of /tmp/rules.debug to sullrich@gmail.com

thanks, this is fixed now.

See http://forum.pfsense.org/index.php/topic,10915.0.html Probably the same issue. Nick.