I didn't follow any of the procedures relating to bounties before starting to work on this, and it would probably be rather out of order for me to expect any payment for the work I did to implement this.
That would largely be setting up SecurID or Wikid. How far along is your current SecurID or Wikid setup? I've setup SecurID before, if you're doing it from scratch it's pretty involved. If it's already all configured and in place and just a matter of adding RADIUS, that's 2-4 hours roughly and reasonable for that. Haven't setup Wikid though I suspect it's probably about the same.
What's the current state of your SecurID/Wikid setup? Would it be one or both?
I paid the bounty as a project donation, which is what I though I was supposed to do. Indeed, I was told specifically to do that on another bounty. I am very sorry for the misunderstanding and will be sure to clarify that point next time. It is a great project, and I was happy to help financially.
As a practical matter, how else would it get paid when so many people contributed to the eventual solution?
That is, as I understand it, how things have been done lately as an "escrow" sort of deal and then cmb or someone else with access to that can distribute it.
As to who gets what, that is up to you, depending on however you see fit to allocate. :-)
This likely is the cause of/solution to the problem. I just checked my loader.conf, almost empty in my 1.2/6.3 pfSense build. Perhaps the older 1.2 Release had the offending line. I'll try adding the new lines later, but as stated before we were already at moving along pretty well. Thanks for the details chudy.
Sorry, meant no offense. Was just trying to figure out where this went, as the thread is a bit confusing. It says it was added to release, but doesn't appear in recent snapshots. I was just speculating as to why it looked like there had been multiple people working on this. Again, sorry that my wild speculation was off-base.
Re-reading it does say clearly that the bounty was claimed and the changes were added to head.
I personally would find it useful though if it supported more OLSR options such as HELLO/MID/HNA/TC values, MPR coverage and hysteresis… or at the very least, if it could somehow not overwrite custom configuration changes to such settings.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.