Radius

Advisory: Use of Status-Server (Jul 2015)

Wednesday, March 31, 2021 - 22:22

Status-Server (RADIUS Code Type 12 packet) uses RFC 5997 - http://www.ietf.org/rfc/rfc5997.txt - to deliver a method of one RADIUS server or client to know the status of an upstream or downstream server.

Status-Server

alan buxey

31 March 2021 at 10:23pm

Radius

eduroam

best practice

status server

This advisory has moved to: https://community.jisc.ac.uk/library/network-and-technology-service-docs/advisory-use-status-server-jul-2015

Chargeable User Identity for eduroam: with FreeRADIUS implementation guide

Edward Wincott

Monday, October 29, 2012 - 15:42

CUI

Chargeable-User-Identity

Author: Scott Armitage Updated 10/06/2019

Summary of wireless projects in the Janet community December 2010

Anonymous

Thursday, February 2, 2012 - 09:40

eduroam visualisation tool

projects

su1x

temporary eduroam hotspots

wireless

Introduction

RADIUS attribute filtering with Microsoft IAS and NPS

Anonymous

Wednesday, November 16, 2011 - 15:52

Reviewed 12/06/2019 Why do we need to configure attribute filtering? RADIUS packets contain various "attributes" which can be generated by the network access server (eg. AP or switch) and at RADIUS servers that handle the packets during authentication and accounting exchanges. Certain attributes play a key role in the process of correct assignment of the user to an appropriate VLAN. Depending on the manufacturer of the equipment, these can be RFC-defined attributes or vendor-specific ones.