Talk:RADIUS

message: I've removed most of the external links, as they're just links to individual software packages. sjorford →•← 15:35, 15 Apr 2005 (UTC)
thread_title:  External links 

message: The extenal links were there for ages...It is important to link the best RADIUS servers on the market,
example IAS for Microsoft, FreeRADIUS and other.
This is important due to the fact that when you search Google about 'radius server' this page is in a high position and shold list/talk about RADIUS solutions.
Change the name to Radius Servers.
:Why is it important? Wikipedia is an encyclopedia. That means we have an article explaining what RADIUS is, how it works with other technologies and so on. But we're not a shopping catalogue or a review of individual products. The high Google ranking for the page shouldn't affect the content at all.
:I've no objection to external links, but they have to add something that enhances the encyclopedia article. I've left one link in because it has extra information in about radius servers in general, but the other links don't have that as far as I can see, they just act as advertising. sjorford →•← 08:43, 23 Apr 2005 (UTC)
replies: text: RADIUS Servers are only one half of the solution.  It's better to describe the protocol than just one endpoint.  kgrr talk 17:27, 15 April 2009 (UTC)
thread_title:  Importance of External links - Now it is RADIUS Servers

message: Instead of fighting, why don't we put the list of RADIUS software on a separate page, like List_of_GIS_software ? Then both can be happy.
bluezy
:I like this proposal.  Lists of things are meant to be self-organizing through categories.  kgrr talk 17:26, 15 April 2009 (UTC)
thread_title:  Proposal 

message: Why is this article using the TCP/IP protocol model? Virtually every discussion about networking uses the OSI model. Using a nonstandard model to disccus which layer RADIUS operates at just adds confusion.   — Preceding unsigned comment added by Edtrob (talk • contribs) 01:26, 29 October 2014 (UTC)
replies: text: It's an application layer protocol.  kgrr talk 17:16, 15 April 2009 (UTC)
thread_title:  IP Protocol table 

message: Is it just me, or does the following not make sense:
Although RADIUS was not initially intended to be a wireless security authentication method, it improves the WEP encryption key standard, in conjunction with other security methods such as EAP-PEAP.
RADIUS does not "improve" on WEP; although auth credentials can be transmitted from the NAS/AP to the auth server using RADIUS, the underlying WEP security is still as vulnerable as it otherwise would be. 
Can we delete?
Evilal 00:10, 9 June 2007 (UTC)
thread_title:  Wireless section? 

message: It's always baffled me why RADIUS uses UDP and not TCP. UDP seems much better suited for streaming applications where the loss of a few packets is tolerable. A perfect example is streaming live video. But as a developer I can't see how these principals apply to what we're trying to achieve with the RADIUS protocol. Surely the overhead of TCP wouldn't have any scalability or performance issues on fast networks and modern hardware? Someone please enlighten me why they chose UDP for RADIUS. Straussian 15:26, 2 December 2007 (UTC)
replies: text: See section 2.4 of RFC 2865.  kgrr talk 17:19, 15 April 2009 (UTC)
thread_title:  Question - why UDP? 

message: RADIUS is designed to scale to large-scale deployments with dozens, maybe hundreds of BASs all talking occasionally to a couple of central servers. Given the underlying reliability of modern networks, the overhead of maintaining hundreds of open TCP connections would have been overkill. The alternative (open a connection each time a packet needs to be sent) would also have been inefficient (no point in performing a 3-way handshake for the sake of a single accounting update). On balance, UDP is probably the best choice.
Remember that RADIUS has built-in acknowledgement/retransmission mechanisms to cope with the occasional lost packet.
For a more flexible and robust protocol, see http://en.wikipedia.org/wiki/DIAMETER.
Evilal 08:52, 4 December 2007 (UTC)
thread_title:  Why UDP? -- Answer 

message: Commited some new text at the start to try and speak to what RADIUS is/does for those who don't have much knowledge of it and its associated soup of TLAs. Think it would be good to axe/move some of the existing text especially the paragraphs including and immediatly following 'Many networks services ('
Some ideas for new sections:
One focusing on each of the popular RADIUS auth protocols PAP,CHAP,MSCHAP,EAP..etc centralizing some scattered information.
A second on popular backend databases SQL, password files, LDAP..etc...in the spirit of whatever common practices there are for managing accounts.
Finally security focused protocol criticisms such as use of MD5/secret key lengths/"Just use IPSec" a security/mitigation section might be helpful.
WaffleMonster (talk) 08:33, 15 December 2007 (UTC)
replies: text: Some of these sections may have some merit.  I will be bold and add them this week.   kgrr talk 17:20, 15 April 2009 (UTC)
thread_title:  Bulk Changes 

message: Over the next few days, I will spend some time to cleanup this article.  I am planning on adding three figures.  One showing a block diagram of RADIUS in an enterprise where dialup, VPN and Wi-Fi all use the same RADIUS server, a typical protocol stack and a block diagram of a roaming scenario where there is a proxy RADIUS server communicating with a remote RADIUS server connected by a PKI tunnel.  I also will add a section on tools used to trouble-shoot RADIUS.  kgrr talk 15:46, 15 April 2009 (UTC)
thread_title:  Cleanup 

message: I believe AAA is just a name of a working group, which is a legitimate TLA. For the rest TLA-technobabble should be avoided as culturally inappropriate for enlightened technicians, the effort to find and use real descriptive terms instead of obscurantisms is an indication of a technical maturity of the speaker. In my opinion, that is. Rursus dixit. (mbork3!) 08:55, 13 January 2012 (UTC)
replies: text: You can find an explanation in the introduction part. Killer queen1 (talk) 21:45, 16 January 2012 (UTC)
thread_title: AAA?

message: The section on AAA using RADIUS refers to RAS as the requesting server initially, but then changes to NAS as the server being responded to, and then refers again to RAS. Are these interchangeable?  — Preceding unsigned comment added by Anuragbatra (talk • contribs) 22:48, 11 May 2012 (UTC)
thread_title:  AAA - Section refers to NAS and RAS interchangeably 

message: Aren't there too many capitalised words in this article?
For example,
"Proxy Chaining", "Authentication, Authorization, and Accounting", "Access Reject", 
"Access Challenge", "Access Accept", and "RADIUS Codes".
--Mortense (talk) 11:06, 8 November 2019 (UTC)
thread_title:  Capitalisation