2.0.3 Image Testing

jimp

We're preparing 2.0.3 release in the very near future to address issues in 2.0.2, and it would be best if it got as much testing as possible.

The snapshots for 2.0.3 are live here:
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_RELENG_2_0/

If you uncover any issues, let us know. Thanks!

[Edit: April 8, 2013]: The latest images have an updated version of OpenSSL, and can use as much testing as possible. Install testing, feature testing, etc.

2.0.3 Updates/Changes:
http://doc.pfsense.org/index.php/2.0.3_New_Features_and_Changes

Supermule

heper

Great job folks!

i've updated 2 schools thus far and all is well :)

one side note tho:
i have some schools that are still running the deprecated ospf instead of quagga …
ever since updating to 2.0.2 a month ago (and now 2.0.3), i regulary see the errors show up as seen in screenshot.
the errors do not seem to break anything essential because routes are being propagated as expected.

Kind regards,

Jeroen

ospfd.png_thumb

jimp

Switch to quagga. :-)

OpenOSPFD will often try to add and/or remove routes multiple times. Which works on OpenBSD, but not on FreeBSD, which is one of the reasons we chose to move away from it.

vito

I have it installed
Looks good so far.

heper

got an error on console when i use option 5 (reboot)
reboot procedes fine none the less.

see attached screenshot.

occurs on an ESXI5 VM with 3x e1000 nics assigned, nothing else configured.

bad_fd_number.png_thumb

jimp

That one is harmless, just a byproduct of how the shutdown sequence happens. We fixed it on 2.1 though, I can't recall why the fix wasn't pulled back. It's just cosmetic though so don't worry too much about it.

jikjik101

can't restore config.

Tried full and partial restore.

The following input errors were detected:

The configuration could not be restored.

It's kinda weird. I can see the changes to config after upload. But after reboot, the changes are gone.
Maybe there is something wrong with my config file.

stephenw10

What version was the config file generated by?

Steve

jikjik101

same 2.0.3.

i copied the dhcp server from other box, i am sure i can do that before.
the two boxes have same number of interfaces.

anyway, maybe there was something wrong with my xml editor.
or it was not saved properly the .xml file, instead it was .txt file.

Slam

jikjik101: I saw your post last night just before I planned a clean reinstall of pfSense and thought I'd try the auto config restore from USB

http://doc.pfsense.org/index.php/Automatically_Restore_During_Install

It worked fine except my package reinstalls were bungled, but apart from that it restored all my settings.

jimp

I just ran two tests on the latest snapshot:

1. I edited the config down to just the DHCP section ( <dhcpd>[…]</dhcpd> ) made some obvious changes and then restored that using the DHCP Server section selection. It worked.
2. I restored the original full config from before I made the DHCP edits, and it rebooted and came up with the right config.

No problems that I can see.

Perhaps you fed it the full config and chose only a specific section? That doesn't work on 2.0.x. If you restore a single section you have to edit the file so it only contains that single section. That does work on 2.1 though.

heper

saw something in system log that seems a bit odd.
it doesn't seem to cause many problems, but i figured i'd better post it in case it is something to be worried about.

see screenshot

enjoy :)

lighttpd_ssl_error.png_thumb

jimp

Not really worth worrying about. We started putting the lighttpd logs into syslog now, those kinds of errors are normal from time to time people just never saw them before.

Lighty will log an SSL error like that if a client connects that doesn't do SSL, or resets the connection, etc. Could be any of a few things that result in that error, but it's not usually worth digging at since it's more of a browser-vs-web server issue.

Xon

@jimp:

Switch to quagga. :-)

OpenOSPFD will often try to add and/or remove routes multiple times. Which works on OpenBSD, but not on FreeBSD, which is one of the reasons we chose to move away from it.

Last time I tried to install quagga, it nuked the OpenBGPD bgpd binary. I know the quagga package has a warning about interaction with OpenOSPFD, but it would be nice for that to be updated to include OpenBGPD too.

A warning that OpenBGPD and RIP routed dont play nicely together would be a nice to have.

jimp

@Xon:

@jimp:

Switch to quagga. :-)

OpenOSPFD will often try to add and/or remove routes multiple times. Which works on OpenBSD, but not on FreeBSD, which is one of the reasons we chose to move away from it.

Last time I tried to install quagga, it nuked the OpenBGPD bgpd binary. I know the quagga package has a warning about interaction with OpenOSPFD, but it would be nice for that to be updated to include OpenBGPD too.

A warning that OpenBGPD and RIP routed dont play nicely together would be a nice to have.

I added a note to the pkg descriptions, but that is really an issue for the package repo that doesn't have anything to do with 2.0.3 images.

jimp

A new set of images went up a bit ago that has a completely recompiled set of ports, so it would help if everyone could give everything a good shake-down again to make sure nothing regressed.

webdawg

Does this have any fixes for the mpd/ppp client? I am having a problem with the UML260 USB modem that I never had with any previous releases.

jimp

Not that I recall specifically.

http://doc.pfsense.org/index.php/2.0.3_New_Features_and_Changes
https://github.com/bsdperimeter/pfsense/commits/RELENG_2_0

heper

I've just noticed a possible captive portal issue.
i can't say if this existed in previous releases because it's my first time using Captive Portal with vouchers + win2008r2 radius for user auth.

situation:
Wednesday last week i've implemented a school-wide CP+voucher+AD auth. (I've installed the pre-release because there were CP issues on 2.0.2)
All appears to be working well.

I can connect a client(laptop/smartphone) using vouchers or AD-login
I disconnect this client
After a while (couple of minutes) the client disappears from the CP-status-GUI

the issue is this:
The idle timeout field is set to 10minutes
For whatever reason, it appears that (some) idle client-sessions don't get removed, and stay "active" until I restart the CP service.
On monday i first noticed this, restarted CP. Today i checked again and there were 60+ "active" sessions that were started more then 24h's earlier.

idle timeout field in the cp gui is not (allways)respected. Today (2013-02-07) i've seen "active" sessions that got started this monday (2013-02-04).

I've tried the GUI option to use the idle-timeout from radius server … This makes the CP unusable with vouchers. It appears that when said CP tries to auth vouchers to the AD?

Hope someone can clarify this. This could be a configuration issue, but as basic functionality appears to be working, my gut tells me it's something else.

Kind regards,

Jeroen