2.0.3 Image Testing

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.

jimp

@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.

It never did. That's not a bug. (It's a feature request, and doesn't belong in this thread)

jikjik101

I see. Thanks for the info.

myke

Hi everyone,

I upgrade to 2.0.3 pre Release because the captive portal issues on 2.0.2

It works fine for me but i see something strange on Traffic Graph.

The traffic graph showing outside IP Addresses on Lan Interface like is talking on this thread http://forum.pfsense.org/index.php/topic,59714.30.html

Is it already a fix or it will be fix on a 2.0.3 Final ?

Thanks.

Best regards.
Myke

ingmthompson

@myke:

Hi everyone,

I upgrade to 2.0.3 pre Release because the captive portal issues on 2.0.2

It works fine for me but i see something strange on Traffic Graph.

The traffic graph showing outside IP Addresses on Lan Interface like is talking on this thread http://forum.pfsense.org/index.php/topic,59714.30.html

Is it already a fix or it will be fix on a 2.0.3 Final ?

Thanks.

Best regards.
Myke

I can confirm this behaviour, running the 13th March build. In addition to being able to see publicly routable IPs in the table under Status > Traffic Graph > LAN (which is definitely not right) I can also see the WAN interface IP showing up in both the LAN and WAN tables. I've not previously observed this behaviour, ergo it seems odd to me, and is probably related to the originally highlighted issue. Has anyone filed a bug report yet? Maybe if we work fast enough, we can get this fixed in time for 2.0.3-RELEASE.

jimp

I'm out of town for the weekend so I can't properly check on that, but I think someone else had another thread going for the same problem on 2.1. You can go ahead and open up a ticket on http://redmine.pfsense.org/

phil.davis

Here is the cross-reference to the thread for the 2.1 changes to the rate utility (source of the traffic graph bandwidth by IP data): http://forum.pfsense.org/index.php/topic,59714.30.html - that work seems to have all been done in the mainline, not the branch used for 2.0.3
I think things started with this commit: https://github.com/pfsense/pfsense-tools/commit/d09e8fddd50e95f731f7cef8d1db92ba1b4f2398 - to pfsense-tools which made the rate utility spit out data for external IPs as well as local ones. Then various enhancements were done in pfsense repo to the traffic graph GUI to allow filtering the data so users can choose what is displayed.
But all those were done against the master branches. So I don't see how that has leaked into 2.0.3, which would build from the RELENG_2_0 branch.

jimp

The rate binary is built the same on both branches. If the binary changes require changes to the GUI then they'll need to be done on RELENG_2_0 as well, hence needing a bug report on redmine.pfsense.org.

MaxHeadroom

Hi

just a question; isn't the patch allready out till 16 days?

http://svnweb.freebsd.org/base/stable/8/crypto/openssl/NEWS?view=markup

Major changes between OpenSSL 0.9.8x and OpenSSL 0.9.8y: Fix for SSL/TLS/DTLS CBC plaintext recovery attack CVE-2013-0169

or am i wrong ?

best regards

max