I am currently runnig slackware 12.0 with chillispot installed on it acting as a web captive portal for wireless clients. I get the concept of why you do this, so you can control who has access to your wireless network. I am having trouble understanding how chillispot is actually comunicating with the external radius server. I believe that the radiusclient.conf file is how chillispot is communicating to the external radius server. Does the radius server also have a radius client directory? I believe that this is done by tunneling using tun 0 to make a virtual tunnel between chillispot and external radius server. Is the right way of thinking how chillisot works. I keep reading chillispot website but I feel I am missing something. Any help would be great
vadder

Communication between Radius servers and clients is done by means of packets (actually text file starting with 'Acct-Session-Id="4/1/7/2.647_030CCA7E"\nFramed-Protocol...etc"). These communication files are called accounting packets with names like start, interim update and stop. It is quite irrelevant what kind of applications or scripts act as clients, as long as the communication is intact.

If you need this for authentication with some ISP, then you should request their documentation about this whole process.

Linux Archive

That helps. But not what I was looking for. I have a server set up with slackware 12.1 as my o.s. and chillispot is also installed. I know this server communicates the external free radius server. What I wanted to know is what in chillispot or slackware to go to this external free radius server. There is a directory in slackware called radiusclient and a conf file in that directory called radiusclient.conf, is this file actually telling chillispot to go to the external radius server? Or is this file for actually something else? This file looks like the all the default settings are set, I didn't change anything in this file. The chillispot server goes through the tun0 interface, which is a virtual tunnel, right? My free radius server is also running slackware 12.1 and I have a web server on my radius server.

I do not have any experience with chillispot, so that limits the amount of info that I can contribute. But even chillispot should have some technical documentation.

The only requirement for any software to act as a Radius client is to communicate properly, according the standard. Other then that every client software is free to handle it's configuration and setup at free will - there are no standards for that. I guess that's the reason why response is so scarce on this thread. You will need to find someone specifically with chillispot experience.