2.0.3 Image Testing
-
@heper:
Could this be related to this ?
http://redmine.pfsense.org/issues/2155EDIT:
that appears to be the exact issue yes.It's not the exact issue, it is related tho. Vouchers work for around 1 minute, then they get "disconnected". I think the initial voucher-authentication works fine. the re-authentication (every minute) however, is also applied to vouchers and send to Radius/AD. Radius is unfamiliar with the voucher-code-user and sends "disconnect"for whatever reason last weeks snapshot didn't have the issue, but perhaps it just didn't send auth requests every minute, and the new builds do ?
-
@heper:
Could this be related to this ?
http://redmine.pfsense.org/issues/2155EDIT:
that appears to be the exact issue yes.It's not the exact issue, it is related tho. Vouchers work for around 1 minute, then they get "disconnected". I think the initial voucher-authentication works fine. the re-authentication (every minute) however, is also applied to vouchers and send to Radius/AD. Radius is unfamiliar with the voucher-code-user and sends "disconnect"for whatever reason last weeks snapshot didn't have the issue, but perhaps it just didn't send auth requests every minute, and the new builds do ?
For curiosity I opened this bug on redmine when there was only pfsense 2.0.0 available if I remember correct. So this bug must have been gone and now is there again !?
Perhaps this is a sideeffect of something else. -
i've just noticed something very similar is happening with "Use RADIUS Session-Timeout attributes"
Vouchers being checked against radius timeout, resulting in disconnect
-
The MPD issue I am having has to do with the auto reconnect (dial on demand mode). I have found the only way I can get my ppp to reconnect is if I check it and set idle to 0. I think it was like this in the previous releases.
The directions for the dial on demand mode are misleading. They say not to check this box if you want your connection to be up all the time.
-
anyone can confirm if the CP radius things can still be fixed for 2.0.3 or will it have to wait for 2.1/2.2 ?
-
2.0.3 will fix only regressions between 2.0.1 and 2.0.2, and a few minor fixes that have little chance of creating fallout. The above voucher+RADIUS issue won't.
-
I am currently using the nanobsd 2.0.2 4G version. Can I use the upgrade file to only update one of the two slices?
-
I am currently using the nanobsd 2.0.2 4G version. Can I use the upgrade file to only update one of the two slices?
Update files only update one NanoBSD slice. That's how they've always worked. You can boot back to the other slice if needed.
-
great, I didn't know that. Not a whole lot of commits to the 2.0 release branch for some time now.
when I install a prerelease - how would i update to 2.0.3 once it's released? would I have to reinstall? Thx -
Regular firmware update like any other. If your auto update url is pointed to the 'stable' updates, you'll get it when it's released.
-
I've updated! The only issue for me was a long delay at boottime because my packages didn't reinstall. Or did they? Directly after the update i accidently loaded my old slice and all my packages got reinstalled into that one. Then, next reboot, i booted into the "new" slice and the firewall took ages to load and all packages were missing. I manually the packages and all is good now. It seems strange though that the package update was triggered when I was booting the old slice (I have updated running from slice number two, maybe thats related).
just to clarify, here are my messy upgrade steps:
i was running slice 2 when i started the update.
on reboot i chose to boot slice 2 ouch* and it reinstalled all packages
reboot into slice1: no packages -
FWIW, I upgraded to the latest image (13 Feb 1243), but I'm still having the problem that I initially reported here:
http://forum.pfsense.org/index.php/topic,57258.0.html
That thread eventually got hijacked to be a different issue (but also related to DHCP), but the original problem still remains. This is a regression since pfsense 2.0.1.
-
That thread didn't get hijacked, it was the main issue. The interface going down/up wasn't properly relaunching dhclient, and that should be fixed now. Several others with that same issue confirmed it was fixed for them. If there is a separate issue, then you can keep posting in that thread to continue investigating, or start a new one. The symptoms will be (at least slightly) different now, and it warrants further diagnosis.
-
php: /system_advanced_sysctl.php: The command '/sbin/sysctl hw.syscons.kbd_reboot="0"' returned exit code '1', the output was 'sysctl: unknown oid 'hw.syscons.kbd_reboot''
smallish glitch in current 2.0.3 pre. That variable is gone I guess?
-
That tunable is only valid on a full install w/vga, or nano+vga
It wouldn't be present on an embedded kernel or regular nanobsd.
-
Proxy Squid: Realtime stat (sqstat) doesn't auto refresh.
-
Packages are not relevant to 2.0.x image testing. That would be a subject for the packages board.
-
Planning to upgrade from 2.0.1 to try and improve MTU control on PPP.
Is it worth going to 2.0.2 or straight to 2.0.3? I guess second question is how close is 2.0.3 to being finalized - days/weeks/months?
Thanks
-
2.0.3 is better than 2.0.2 at the moment.
It would be out already, but we're waiting on FreeBSD to release a security announcement on OpenSSL that we need to account for. -
2.0.3 is better than 2.0.2 at the moment.
It would be out already, but we're waiting on FreeBSD to release a security announcement on OpenSSL that we need to account for.You guys ROCK!
