A pfSense roadmap
-
-
I might consider it - I have time now. I used to be pretty good at it, relatively speaking (-;
-
It would be great to see Apinger's issues called out with a action plan sooner vs later as I have provider issues and graphs that are unusable in helping to get these issues fixed
-
It would be great to see Apinger's issues called out with a action plan sooner vs later as I have provider issues and graphs that are unusable in helping to get these issues fixed
There's always cacti, etc. pfSense doesn't have to do everything. (Not that I don't want apinger fixed/replaced, but if it's broken get another tool.)
-
It would be great to see Apinger's issues called out with a action plan sooner vs later as I have provider issues and graphs that are unusable in helping to get these issues fixed
apinger needs a re-write. It's garbage code.
-
Wow!
There is just something magical reading the project map for 3.0 while feasting on a Cadbury's almonds and raisin chocolate bar.
But…any consideration for the Wireless ISP guys? No MPLS implementation? No MIPS hardware as yet? Can these be options for consideration for small ISP types?
-
Fortran IV - holes in punched cards can be seen. And the 6 position is marked usual. ;)
Python? Programming with spaces? Loss/extra space and the program behaves unpredictably? Forget copy/paste, move pieces of code, and so on?
Great… :( -
Wow!
There is just something magical reading the project map for 3.0 while feasting on a Cadbury's almonds and raisin chocolate bar.
But…any consideration for the Wireless ISP guys? No MPLS implementation? No MIPS hardware as yet? Can these be options for consideration for small ISP types?
Did I say there would not be MPLS, or GRE support?
No, I did not. It's a path, jtls.
In any case, 2.x is always an option on existing hardware.
-
Fortran IV - holes in punched cards can be seen. And the 6 position is marked usual. ;)
Python? Programming with spaces? Loss/extra space and the program behaves unpredictably? Forget copy/paste, move pieces of code, and so on?
Great… :(If it forces us to maintain proper style and spacing, it's not a bad thing.
-
Fortran IV - holes in punched cards can be seen. And the 6 position is marked usual. ;)
Python? Programming with spaces? Loss/extra space and the program behaves unpredictably? Forget copy/paste, move pieces of code, and so on?
Great… :(If it forces us to maintain proper style and spacing, it's not a bad thing.
python is a lot like lisp without the parenthesis. Once you figure that out, it gets easy.
-
@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…
