2.0.3 Image Testing

stan-qaz

I'm currently running this (below) version, would it be useful to grab the new snapshot you are creating tonight?

2.0.3-PRERELEASE (amd64)
built on Wed Feb 13 12:44:38 EST 2013
FreeBSD 8.1-RELEASE-p13

jimp

There are some minor, but beneficial fixes. May as well get it. We're still in a holding pattern waiting on FreeBSD to release the OpenSSL SA, but we've found a couple little things here and there.

asterix

Any estimated time given by FreeBSD on the OpenSSL SA release?

jimp

None that I've seen. Last I saw was this on Feb 7 saying that the patches are in review… http://lists.freebsd.org/pipermail/freebsd-security/2013-February/006945.html

senser

How about adding manpages to nanobsd 4G images? I am a freebsd newb and I am kinda missing those when I am screwing around. I mean…

Filesystem           Size    Used   Avail Capacity  Mounted on
/dev/ufs/pfsense0    1.8G    178M    1.5G    11%    /

…free space is nice to have but this is a waste IMO. :)

jimp

Not a good topic for this thread, but it's something that someone could make a package for eventually

wallabybob

@senser:

How about adding manpages to nanobsd 4G images?

You can get FreeBSD man pages online at http://www.freebsd.org/cgi/man.cgi

senser

OK, I have created a new thread for the manpages: http://forum.pfsense.org/index.php/topic,59280.0.html

stan-qaz

It looks like there may have been a DHCP logging change with the latest 2.0.3 build and in v2.1, see:

http://forum.pfsense.org/index.php/topic,59329.msg318796.html#msg318796

Don't know if it was intentional or not but dhclient logging has recently changed.
No longer logging DHCPREQUEST DHCPACK and bound messages for DHCP renewals.
Now only logging the RENEW and Creating resolve.conf messages for DHCP renewals.

jimp

The binaries didn't change, and the config didn't change that I see. Only potential change that might affect is how it's getting called from rc.newwanip through check_reload_status but that also didn't change anything in the dhclient parameters that I see

ellors

After te firmware upgrade to 2.0.3 the systems show the message "Packages are currently being reinstalled in the background.
Do not make changes in the GUI until this is complete."
It's been there more then an hour…

ellors

Never mind… it just took to much time to end the process.

Sorry

heper

updated one the 2.0.3 production machines to the latest 2.0.3

i noticed some errors in logs, while it was updating/installing squidguard (see attached screenshot)

squidguard_error.png_thumb

slu

Some news for 2.0.3 release?

jimp

The same as before. Still waiting on FreeBSD's OpenSSL security advisory. No idea why it's taking so long for them to release it, but others have also been fairly slow on this one.

Supermule

Why not use the time to get the Snort package working to its full potential?

Its core functionality and the package is EOL.

jimp

Packages have nothing to do with a release, and we have plenty else to do. I can't fix snort, I think someone else is already working on that, please don't clutter this thread with package questions.

charlien

I was just setting up a 2.0.2 virtual machine. I'd like to go this route instead. What will I have to do as updates to 2.0.3 are released?

jimp

@charlien:

I was just setting up a 2.0.2 virtual machine. I'd like to go this route instead. What will I have to do as updates to 2.0.3 are released?

A firmware update, same as any other update.

jikjik101

carp dashboard widget doesn't refresh automatically.
if the master goes down, the widget still shows master and the slave still shows backup.
need to hit F5 to show correct status.

2.0.3 Image Testing

We use the mighty pf, we cannot be fooled.

We use the mighty pf, we cannot be fooled.