WOW… What at turd!
-
Yes, agreed. Still, down for three hours now and no light in sight…. What would be a better name for such a problematic release?
-
Perhaps since you're incapable of troubleshooting if you'd answer the questions of those who are capable you'd get somewhere.
-
Based on today's posts I'm not alone. In the past one could expect to upgrade to a final release without too much need to debug, and if not satisfied could easily revert. Doesn't seem to be the case this time around.
-
Reinstall the version you came from and upload the config you saved before upgrading. Takes about 5 minutes.
-
I just updated to the release and it was as simple as click click.. If you had a problem, why don't you just download an ISO be it current or older and install clean… That you have been down for 3 hours, and all you have done is complain..
-
bit of a douchy post. no technical info, just trolling
you obviously have no intention on getting it fixed
-
I see exactly 0 other posts with broken DNS. Outside of hardware-specific issues, of which there haven't been many, I don't see any others with a complete failure.
We were serving as much as 1 update per second at peak earlier, and still 250-500 Mbps sustained now, about 20 updates every minute are happening right now. This is the highest rate of upgrades of any release we've ever done, and very few significant problem reports.
Obviously you have something wrong. But if you're unwilling to do any troubleshooting, we can't help.
-
Sure, "re-install the version I came from, and restore the config". My first thought. Can't seem to locate 2.2.4 ISO in the archives though.
-
-
Yes, agreed. Still, down for three hours now and no light in sight…. What would be a better name for such a problematic release?
maybe its a problematic user, not release?!? :o
-
Clearly some layer 8 issues for sure here..
-
This guy seems to be trolling you guys, i would just ignore him. He didnt even try and troubleshoot the issue.
Personally, I did come to the forums to see the horror stories as i never trust any pfsense release in the first month or so, double on huge branch releases!
But this was just crap. its barely a problem. so boo! i give it a 1/10 in terms of interesting issues.
-
7 out of 7 upgrades with no problems. Zilch. Nada.
-
Ok, here's some details:
Fresh install for 2.3 the restore config backup (fairly complex config with three 2 VLANS and trafic shaping)
Using unbound: No dsn resolution at all!
Using dnsmask: Partially working, can browse web sites that support IPV6. IPV4 sites, not all! (very strange).Nothing notable in system logs.
Fresh install for 2.2.4 the restore same config backup.
All is well using unbound. Have not tried dnsmask… I'm done
-
The whole world revolves around one person. "I"!
-
Thanks to all of you fanboys for all the helpfull sarcasm. I stand by my original comment. Over and out.
-
Thanks to all of you fanboys for all the helpful sarcasm. I stand by my original comment. Over and out.
First of all, Why would you update to 2.3 if you depend on this setup? I mean on every upgrade there are going to be issues PERIOD. look at windows 8 windows 10, ios 8 ios9 i can keep going on and on the point is if you depend on the setup DONT F*** UPGRADE….PERIOD. Now if you want to help the community make a mini LAB so if you screw it wont matter and ask for help and look for bugs. Second dont be all "sarcastic"
Way to go guys… not!
Thats not right…the software is free the help is free...so dont expect sometimes the best out of people..I know sometimes they can just put a "look at the wiki" or laugh at you just because they can but either way around 90 percent they are very helpful. And third of all you should ALWAYS explain not just
WOW… What at turd!
this is not a gossip site…
-
Thanks to all of you fanboys for all the helpfull sarcasm. I stand by my original comment. Over and out.
Wouldn't consider myself a fan boy. But don't take my word for it, look at my negative karma.
I call it like I see it and frequently butt heads with the devs and even cmb. But the tact in this thread from the very opening post was/is totally unwarranted. Even to me. And then to be uncooperative in trying to resolve the issue puts it that much more over the top.
Hope you find a router that works perfectly for you all the time and every time. Especially through major upgrades. It is to be expect that of the tens of thousands of installations on wide variety of hardware and network implementations there are going to be some situations where there are issues. Especially with a major upgrade.
-
Well I kind of am a Fan boy and had an issue upgrading, no problem come to the forums go to install and upgrade section second solution fixed it for me. cake.
thanks for the new release guys, I really appreciate that you have remand kind and professional, this guys is a troll.
-
I call it like I see it.
So do I.
@NOYB:But the tact in this thread from the very opening post was/is totally unwarranted.
I agree, and for that I apologize. I was really pissed and I'll explain why.
@NOYB:And then to be uncooperative in trying to resolve the issue puts it that much more over the top.
Uncooperative? When everyone is screaming at you, resolving the issue translates to get this thing back online ASAP.
@NOYB:Hope you find a router that works perfectly for you all the time and every time.
pfSense 2.2.4 has run flawlessly since June 2015 without a single reboot. That comes pretty damned close to 'all the time, every time.'
@NOYB:Especially through major upgrades.
Usually a 'major' upgrades would be going from 2.x.x to 3.x.x, at least that's normally how versioning is done. 2.2.4 to 2.3… not so major.
@NOYB:It is to be expect that of the tens of thousands of installations on wide variety of hardware and network implementations there are going to be some situations where there are issues.
Yep. I must have that one in million system/config where the upgrade really went south. But IPV6 working, and not IPV4, with no unusual log entries… that's a strange one.
This is what really burns:
I've done many pfSense upgrades in the past and have come to certain expectations. Yes, there are sometimes a couple of things to adjust to restore full function. If not, one could always rely on a full backup restore fallback. Not this time. There was absolutely no mention in the release notes that the full restore capability had been removed from 2.3, a pretty important omission. Had there been, this mess wouldn't have happened. I understand the notes have been updated... too late in this case.
One develops certain processes based on long term exposure and trust in a product. This one kind of blew all that away.
