A pfSense roadmap
-
@gonzopancho:
The next PC Engines board has a Jaguar (so: AES-NI) 2 or 4 core CPU, 2 or 4GB RAM (ECC on the 4GB model) and (wait for it), Intel NICs (I imagine these will be i217/218 class.)
Intel NIC's? That is awesome, where did you see this?
-
[…]and the program behaves unpredictably?[…]
Forgot something:
Unpredictable behavior will most likely be caught by the copious amount of unit tests we'll surely be adding during the rewrite.
-
@gonzopancho:
The next PC Engines board has a Jaguar (so: AES-NI) 2 or 4 core CPU, 2 or 4GB RAM (ECC on the 4GB model) and (wait for it), Intel NICs (I imagine these will be i217/218 class.)
Intel NIC's? That is awesome, where did you see this?
Pascal told Chrs months ago.
-
Sounds like nice hardware. These will work well when its 32C outside, hotter inside and no airconditioning? (Its a serious question)
-
I don't design the PC Engines boards.
The RCC-VE & RCC-DF will.
-
Totally
@gonzopancho:
apinger needs a re-write. It's garbage code.
-
rewrite can't happen soon enough dual wan failover is what brought me to Pfsense on my connections it no longer works
-
@gonzopancho:
…The next PC Engines board has a Jaguar (so: AES-NI) 2 or 4 core CPU, 2 or 4GB RAM (ECC on the 4GB model) and (wait for it), Intel NICs (I imagine these will be i217/218 class.)
Do we have anywhere we can get more info on this? Sounds like it's worth waiting for before my next upgrade!
Thanks,
Supe -
They expect the new board mid-2015 and it's also expected to deliver full gigabit transport with pfSense… (called 'em and asked).
-
Blocks declared using whitespace!!! Gotta be the dumbest idea ever…
-
Blocks declared using whitespace!!! Gotta be the dumbest idea ever…
I'll take that over an unreadable perl script with no whitespace any day of the week. :-)
See above, re: coding style.
-
Also: http://www.secnetix.de/olli/Python/block_indentation.hawk
-
Also: http://www.secnetix.de/olli/Python/block_indentation.hawk
Mice were crying, injected, but continued to eat a cactus. ;D
50% of the source code holds significant whitespaces. Tabs canceled because for 20 years and have not decided what to do with them.
-
Blocks declared using whitespace!!! Gotta be the dumbest idea ever…
I'll take that over an unreadable perl script with no whitespace any day of the week. :-)
See above, re: coding style.
Well, yes, it is an advantage Perl. Read compressed JS is also impossible, but one press of the button in the editor and we can see the code in your favorite style to us. Just Perl and the vast majority of system programming languages so may, not only C-like, but Python - no. ;)
-
Because you can't mangle python into an unreadable mess in quite the same way, so it's not necessary. :)
-
That's what I watch a lot of programs available in Python byte-compiled code. Suddenly anyone in any wrong editor will open. :D
-
Wot?
I design the API in the lift line.
-
You've clearly put a great deal of thought into the roadmap, and I'm impressed.The recently announced Intel Xeon SOC will be very interesting with v3.
One thought/suggestion regarding packages- have you thought about enforcing a rule that requires all third party packages to have a separate jail? Freenas does this now, and it improves the security and stability of the platform. It will make creating packages a bit more work, but with COW ZFS you won't waste disk.
(You are migrating to root on ZFS I hope).
-
You've clearly put a great deal of thought into the roadmap, and I'm impressed.The recently announced Intel Xeon SOC will be very interesting with v3.
One thought/suggestion regarding packages- have you thought about enforcing a rule that requires all third party packages to have a separate jail? Freenas does this now, and it improves the security and stability of the platform. It will make creating packages a bit more work, but with COW ZFS you won't waste disk.
(You are migrating to root on ZFS I hope).
Yes, we knew about Broadwell-DE (the codename for Xeon D), and kept it in-mind while evaluating our options. We have a future product based on BDE in development.
root on ZFS: perhaps even for embedded. The issue here is that ZFS eats ram for breakfast, and lower-end systems don't necessarily have same to spare.
We're quite aware of what the guys at iXsystems are doing with FreeNAS and PC-BSD. First step here is to get to 'pkg(ng)' on pfSense.
-
@gonzopancho:
Yes, we knew about Broadwell-DE (the codename for Xeon D), and kept it in-mind while evaluating our options. We have a future product based on BDE in development.
root on ZFS: perhaps even for embedded. The issue here is that ZFS eats ram for breakfast, and lower-end systems don't necessarily have same to spare.
We're quite aware of what the guys at iXsystems are doing with FreeNAS and PC-BSD. First step here is to get to 'pkg(ng)' on pfSense.
ZFS only really eats RAM when deduplication is used. The COW capability of ZFS combined with Jails is light years ahead of Docker et. al.
I agree that getting pkg working is the first step, and I love that you're getting rid of PHP!
