-
ok, found the problem. Had a couple other things come in overnight anyhow, will make a new set later today.
No worries, thanks for the prompt response :)
-
Hi!
Can someone on 2.0.2 run this command: mpd5 -v
And post output here?Thanks a lot!
I'm getting a blank output.
-
Hi!
Sorry to bother you all, I totally forgot I asket SAME question in other forum…
Sorry again, 2.0.2 uses 5.6 version of MPD5 package... -
Tested the new build today, it's working perfectly. Looking forward to an official release!
-
NICE!!
-
Yes I meant to post about that new build last night. We had a couple issues come up (you can see the RELENG_2_0 commit log on github) that required some fixes, and I put in the limit fix for the table entries as well when I did that.
-
Thanks Jim for the unofficial release.
Btw my LCDProc won't run after upgrade from 2.0.1 to 2.0.2 but there is nothing from System Logs
-
hello,
where can i download the new 2.0.2 Image?
And can i upgrade from my new installed 2.0.1 ?
-
where can i download the new 2.0.2 Image?
And can i upgrade from my new installed 2.0.1 ?
See my link and explanation here: http://forum.pfsense.org/index.php/topic,52810.msg290463.html#msg290463
And yes you can upgrade from 2.0.1 or any older release.
-
:) ahh okay.. thanks..
-
Hi. Just a note about the new upgrade, the "WOL" seems missing from the drop down list of "Services". I noticed you updated the downloads you mentioned above today and tried it out just now. Everything else seems great just the one glitch so far. The widget on the dashboard works and shows my listed machines for "WOL" so I am guessing it is only a navigation, or webpage error. Nice job though so far. Great firewall. :)
FYI, tried default theme "pfsense_ng" and still no joy. was originally set at "the_wall" -
Nice catch, it was apparently accidentally removed in an earlier commit. I added it back.
-
-
Try here:
http://files.nyi.pfsense.org/jimp/foo/shiny/ehrmagerd/ -
There should be one more build coming later today that will hopefully be the last, but we'll need to test it of course.
I'll post here again once it's up.
-
Thanks, testing now ;)
-
Latest build is up now, hopefully the last, unless someone uncovers a show-stopper…
-
I apologize if this is off topic, but I found a very minor UI bug in 2.0.1, can someone test if it's in 2.0.2 before I report it? Don't want to waste the developer's time if it's already fixed but this week I don't have time to test it myself.
Services > DNS Forwarder > Add (+) Domain Overrides:
Name: Test
IP: 10.10.10.10
Description: (null)Click save and back on the DNS Forwarder screen there's no alert. Now delete the domain override just created and the message "The DNS forwarder configuration has been changed. You must apply the changes in order for them to take effect." is displayed. Adding the domain override also requires the changes to be applied in order to take effect, but the user is not notified.
-
I apologize if this is off topic, but I found a very minor UI bug in 2.0.1, can someone test if it's in 2.0.2 before I report it? Don't want to waste the developer's time if it's already fixed but this week I don't have time to test it myself.
Services > DNS Forwarder > Add (+) Domain Overrides:
Name: Test
IP: 10.10.10.10
Description: (null)Click save and back on the DNS Forwarder screen there's no alert. Now delete the domain override just created and the message "The DNS forwarder configuration has been changed. You must apply the changes in order for them to take effect." is displayed. Adding the domain override also requires the changes to be applied in order to take effect, but the user is not notified.
It exists in 2.0.2 also.
Adding (or editing) a domain override doesn't require "apply changes", but removing domain does.But I'm not sure it's a bug. Adding or edtiting things are less "harsh" than deleting things. IMHO.
@jimp
BTW: 2.0.2 (20121120-1234) seems to be working just fine.
I also tried "upgrading" "-1234" to "-1234" with a "firmware - manual update" of "Full Update", and it seems to
have applied just fine. Are there any drawbacks of doing such "manual update" from 2.0.2 to 2.0.2? -
No a manual update works fine. Even applying the same firmware on top of itself should be fine, we recommend that when people have mangled things now and then.
