WOW… What at turd!
-
^ agreed, if he really did what he says he did in a production environment, I would have fired him. I've never seen any of my employees act so stupidly, even with home networks. You don't drop brand new software on a production machine with no snapshots/backups or spare images around, especially when you're apparently too cheap for commercial support, double-especially with zero testing in your environment first
-
+1
-
I had no issue with the upgrade. I wiped and did a fresh install and restored using my 2.2.6 backup and all works like a charm.
-
the upgrade from 2.2.6 > 2.3-release also worked without any issues for me. the only package i had installed was mailreport. upgraded and back online in less than 5 minutes. great job, guys (and gals)!
-
Don't take this the wrong way, but considering you couldn't even find the 2.2.4 ISO's in a directory that had about 5 of them, perhaps you should consider a new career outside of IT? Sounds like it might be a little too challenging for you
A couple of things to consider. This did not happen on a "production" system, it happened at home, but that does not make it less important for those using it. Secondly, most of the code I've developed over the last 10 years actually lives embedded in over 50% of all cablemodems in use today. I've actually got some code in pfSense, not a ton but a few fixes and improvements here and there. So, no, I'm not an "IT" guy, nor would I ever consider a career in IT, the pay is too low.
Mea culpa. I wish I had taken a deep breath and calmed down before dashing off that original post, starting this shit storm of pontification. Lesson learned….
-
Mea culpa. I wish I had taken a deep breath and calmed down before dashing off that original post, starting this shit storm of pontification. Lesson learned….
-
You have to wonder why are they on 2.2.4? and not 2.2.6 if they are so worried about updating?
Here's the thing. 2.2.5 didn't work well for me. No problem, just restore the full backup of 2.2.4 using the built-in capability that's been available since what seems like forever.
After reading the release notes for 2.3, where there was no mention of this deleted functionality, I figured the same approach would be fine with at most half an hour of down time. The rest is history….
-
2.3 killed two of my wifi routers. WTF!
Can't connect to anything on port 80. 443 works fine.
Good thing I'm running on a SAN, just reverted back to a snapshot.
-
Upgraded to 2.3. lost dns resolution… can't restore full backup.
Way to go guys... not!
Locking thread, it's pointless. Multiple people tried to help here, PEBKAC
-
Yeah this thread is completely unproductive. If OP had started answering questions, I would have made sure his problem was addressed a lot faster than the hours he was screwing with it. I did free phone and screen share sessions with a couple people yesterday who were having issues, I would have done same with OP if he had any interest in actually trying to troubleshoot the problem.
If you're having an issue post-upgrade, start a new thread describing what you're seeing. Or pop into our IRC channel, ##pfsense on Freenode, for potentially more immediate help. I'm watching there and helping in such cases as well. If you're a support customer, please start a support case - we don't dock incidents for cases that are the result of a software problem.
