2.0.0-pre2 has "Magic feature number one" :)
I've just committed a preliminary patch to add "magic feature #1" that I've mentioned a few times. The feature is VMPS support. :) ... listen { type = vmps ipaddr = 10.1.2.3 port = 1589 clients = vmps_clients } vmps_clients { client foo { ipaddr = 1.2.3.4 ... } } ... The preliminary functionality is there. It's not ready for production use, but it can receive VMPS packets, and then complain that it doesn't know what to do with them. The goal for 2.0.0 is to have full support for VMPS. :) Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Alan Dekok wrote:
I've just committed a preliminary patch to add "magic feature #1" that I've mentioned a few times.
The feature is VMPS support. :)
... listen { type = vmps ipaddr = 10.1.2.3 port = 1589 clients = vmps_clients }
vmps_clients { client foo { ipaddr = 1.2.3.4 ... } } ...
The preliminary functionality is there. It's not ready for production use, but it can receive VMPS packets, and then complain that it doesn't know what to do with them.
The goal for 2.0.0 is to have full support for VMPS. :)
Neat , unfortunately only Cisco switches seem to support it, and we run entirely on HP Procurves. Guess it means people will no longer have to use OpenVMPS to proxy :) -- Arran
Arran Cudbard-Bell wrote:
Neat , unfortunately only Cisco switches seem to support it, and we run entirely on HP Procurves. Guess it means people will no longer have to use OpenVMPS to proxy :)
Plus, OpenVMPS is not under active development, so there's no maintainers. It claims it's part of another project (that I won't name), but that project includes the *binary* of OpenVMPS, and not the source. GPL concerns may apply... On top of that, the project is funded by a commercial company, as a loss-leader for their commercial support, and the "community" that works on it is limited to the employees of that company. Good luck getting patches added if they conflict with the corporate agenda... Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hi,
Plus, OpenVMPS is not under active development, so there's no maintainers. It claims it's part of another project (that I won't name), but that project includes the *binary* of OpenVMPS, and not the source. GPL concerns may apply...
VMPS support in FreeRADIUS 2.0? I'm *very* happy with that idea! ;-) alan
A.L.M.Buxey@lboro.ac.uk wrote:
VMPS support in FreeRADIUS 2.0? I'm *very* happy with that idea! ;-)
Yup. It's there now. I've done some simple tests, and it works. The new config unlanguage (I'm beginning to like that word) makes testing it HUGELY easier. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hi,
A.L.M.Buxey@lboro.ac.uk wrote:
VMPS support in FreeRADIUS 2.0? I'm *very* happy with that idea! ;-)
Yup. It's there now. I've done some simple tests, and it works.
The new config unlanguage (I'm beginning to like that word) makes testing it HUGELY easier.
makes as much sense as this weird page: http://www.geocities.com/m_valuedlets/T3M.html certainly if we can examine the VMPS packets we should be able to control and handle things a little bit easier - you've probably seen those VMPS packets which arent the device connections - eg the switch checking VMPS server is alive...... alan
A.L.M.Buxey@lboro.ac.uk wrote:
makes as much sense as this weird page:
"exceeded limits"
certainly if we can examine the VMPS packets we should be able to control and handle things a little bit easier - you've probably seen those VMPS packets which arent the device connections - eg the switch checking VMPS server is alive......
Yup. See "dictionary.vqp" for the VMPS / VQP attributes. Updates as to what the heck they all mean, and sample configs are always welcome. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Alan D, Would you mind having configuration documents for 3rd party services like JRS on the FreeRADIUS wiki ? Alan B, Would JANET mind having configuration documents for JRS on the FreeRADIUS wiki ? It is meant to be a repository for everything FreeRADIUS after all ... and it's easier if all this stuff is in one place. -- Arran
Hi,
Alan D,
Would you mind having configuration documents for 3rd party services like JRS on the FreeRADIUS wiki ?
Alan B,
Would JANET mind having configuration documents for JRS on the FreeRADIUS wiki ?
It is meant to be a repository for everything FreeRADIUS after all ... and it's easier if all this stuff is in one place.
personally I would prefer such configuration to be on the JRS support / UKERNA document site. What should be on the main FR wiki is the fundamental 'how to proxy' and 'how to attribute filter' type documents. I believe that special service cases could otherwise overrun the freeradius site (as they do the freeradius users list) alan
On Mon 28 May 2007, Arran Cudbard-Bell wrote:
Alan D,
Would you mind having configuration documents for 3rd party services like JRS on the FreeRADIUS wiki ?
Alan B,
Would JANET mind having configuration documents for JRS on the FreeRADIUS wiki ?
It is meant to be a repository for everything FreeRADIUS after all ... and it's easier if all this stuff is in one place.
I certainly have no problem with anything related to AAA being in the wiki as long as anything not part of FreeRADIUS itself is clearly labeled with a description of what its for. Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Peter Nixon wrote:
On Mon 28 May 2007, Arran Cudbard-Bell wrote:
Alan D,
Would you mind having configuration documents for 3rd party services like JRS on the FreeRADIUS wiki ?
Alan B,
Would JANET mind having configuration documents for JRS on the FreeRADIUS wiki ?
It is meant to be a repository for everything FreeRADIUS after all ... and it's easier if all this stuff is in one place.
I certainly have no problem with anything related to AAA being in the wiki as long as anything not part of FreeRADIUS itself is clearly labeled with a description of what its for.
Cheers
Ok ... Theres no reason why the wiki can't cross link to the Janet Roaming Service site for configuration pages. Added basic HP configuration pages to the wiki, and cleaned up the configuration page. Looks all perty now :) Will add stuff on the nt passwords tomorrow, as I need the ldap schema definition. Fortunately the stuff that I wrote for our own wiki (PMWiki) seems to use most (not all) the formatting rules of MediaWiki.
Hi,
Would you mind having configuration documents for 3rd party services like JRS on the FreeRADIUS wiki ?
as the work item leader for eduroam in Europe, I'd say: we also wouldn't mind if you'd give permission to put all this fine documentation into the Roaming Cookbook v2 (or v3), if you don't mind... ;-) You can contact Josh Howlett from UKERNA for these matters, or me directly. Greetings, Stefan -- Stefan WINTER Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
On Mon 28 May 2007, Alan Dekok wrote:
I've just committed a preliminary patch to add "magic feature #1" that I've mentioned a few times.
Cool.... Waiting patiently for "magic feature #2" :-) -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan Dekok -
Arran Cudbard-Bell -
Peter Nixon -
Stefan Winter