Really big problem to go to 2.2.2 from 2.2.1
-
So why do y'all have your serial port enabled if you are not using it. …
It's the same sort of philosophy as with security. Only what is needed is permitted, stored/kept, provided, etc.
First thing I did when initially setting up my pfSense machine was go into the BOIS and turn off everything not being used. .
Are you f*ing kidding me buddy? Did you crack open the machine and pull out the data cable from the cdrom drive too? Don't forget to remove the video card! Why, don't you know that every single 1337 h4x0r in the world USES A MONITOR to hack things!!! Why do they even install serial ports and video cards in machines? They are just asking for trouble. Its reckless insecurity!
Oh and make sure to disable the USB and PS2 ports. Never know when some rogue keyboard will fly into them and FUCK_SHIT_UP. You will also need to create your BIOS password by randomly mashing on the keyboard. Its not secure unless it takes a CMOS wipe to access the machine.. AMIRITE!!!
Last tip, grind down the serial port headers with an angle grinder after you turn them off. CANT BE TOO CAREFUL!!!
-
Who said anything about security or hacking? Similar to others seemingly trying to change the subject to making about something else like energy savings etc.
Apparently not many people comprehend KISS. I feel like Walter White trying to explain chemistry to Jesse Pinkman. KISS doesn't mean to get rid of something that is needed, used, etc. That obviously would be anti-KISS.
Oh by the way. Yes, removed the CD-ROM, and HDD, there where no cables to be removed though. The video card is integrated, and beside it is being used. So that would not qualify as KISS. If the BIOS permits it the PS2 port is disabled since it is not being used for anything. The USB ports are being used. So again that would not be a KISS candidate.
Regarding grinding down serial port headers. Now you're just being idiotic. That's okay though, it's your right (maybe, depending on where you are/live). OS can not detect "port headers" (connectors). Poke fun if like but I didn't spend hours troubleshooting a failed upgrade due to a serial port issue on a system that has no need for a serial port. Many here did.
-
Another thread gone haywire :D
Disabling serial console in bios gone to grinding of serial port console along with graphics and sound cards…..
Yippiiiie!
-
Thanks Supermule. I needed that laugh. +1 karma for you.
-
I just pulled 2GB of RAM out of my box since it seemed to not be in use (Kidding).
-
I think I will take the cases off all my boards, cases don't seem to be used either :P
-
I just pulled 2GB of RAM out of my box since it seemed to not be in use (Kidding).
Another good one. LOL +1 karma for you too.
Although… The more there is the greater odds of a failure... If it's really not needed and never will be. There's really no point in it being there. No upside to it, only down side. Though I admit my system has 2 x 1GB modules and only using about 20% according to the dashboard (memory usage + tmp and var ramdisks).
But if I pull out the extra module I'll probably lose it. And then some day need it for some reason. Think I'll just continue living dangerously.
-
I think I will take the cases off all my boards, cases don't seem to be used either :P
You're reaching. But I'll be generous and give you one too for effort.
Actually cases are used. They are part of the thermal control system.
-
I think I will take the cases off all my boards, cases don't seem to be used either :P
You're reaching. But I'll be generous and give you one too for effort.
Actually cases are used. They are part of the thermal control system.
That's true - specially on my APU systems. Permission given to smite me for my silly idea.
-
Missed the point of my post entirely. Don't disable the serial port in the BIOS. Enable the serial console as a secondary console. You never know when it might be useful.
Locking the thread since it seems to have lost its usefulness.
As a reminder for those finding this thread who missed it earlier, the workaround and fix may be found at https://doc.pfsense.org/index.php/Upgrade_Guide#pfSense_2.2.2_Upgrade_Notes
-
For the first time ever, we went ahead and updated the 2.2.2 full update files (only thing affected) to include only this change:
https://github.com/pfsense/pfsense/commit/cc1f655f8e88ccda837e21d0646bbc71781198b9So no one will need to do any of the work arounds anymore.
