> But the radius request has been exposed in 4.4 :-) What?!
*Checks documentation* But the docs don't mention it. Do they? *Checks source code* Oooooooooo, but there it is in sub->radius_parser ... Looks like I have some work to do! Would it be bad form to ask for a radius example? ... You know, if it specifically mentioned the Called-Station-Id attribute, that would be pretty freaking awesome ... just saying ... Jake Sallee Godfather of Bandwidth System Engineer University of Mary Hardin-Baylor WWW.UMHB.EDU 900 College St. Belton, Texas 76513 Fone: 254-295-4658 Phax: 254-295-4221 ________________________________ From: Fabrice Durand [fdut...@inverse.ca] Sent: Thursday, September 11, 2014 4:01 PM To: packetfence-devel@lists.sourceforge.net Subject: Re: [PacketFence-devel] Extending the new vlan filter feature But the radius request has been exposed in 4.4 :-) On 11 septembre 2014 16:33:02 EDT, "Sallee, Jake" <jake.sal...@umhb.edu> wrote: Greetings Developer Gurus: I approach the Throne of The Developers with a humble idea, perhaps it is even a good one : ) I love the new vlan filter feature, however I do no think I can make use of it quite yet. There is still one data structure that this feature seemingly does not have access to that keeps me from using it (unless I am quite missing something). If we could expose the information inside the RADIUS request to the vlan filter then I could finally remove the custom code from my deployment and make my upgrade process much simpler as well as alleviate a lot of the fear I have with moving to different versions of PF. There is A LOT of information in the RADIUS request and combining that info with the flexibility the vlan filter gives us would make PF almost completely runtime programmable (with respect to vlans at least). For my environment specifically, I have some custom code that reads the Called-Station-ID from my RADIUS request and modifies the returned vlan based on that attribute. If the vlan filter could see the information in the RADIUS request I could just write a simple filter for that info and not have to worry about the maintainability of custom code in future versions of PF. I hope what I am trying to say is understandable, its been a crazy day, if I failed to explain properly please let me know. Jake Sallee Godfather of Bandwidth System Engineer University of Mary Hardin-Baylor WWW.UMHB.EDU 900 College St. Belton, Texas 76513 Fone: 254-295-4658 Phax: 254-295-4221 ________________________________ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ________________________________ PacketFence-devel mailing list PacketFence-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-devel -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-devel mailing list PacketFence-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-devel
