hi
that's difficult to answer precisely without having more details. if i understood correctly, _you_ will be authentifying your users. so, the exact amount of data merely depends on the authentication method chosen for user authentication between you and your user and on the number and type of the authorization tokens included in your answer (radius-attributes). depending on the authentication method, it can be just one Access-Request - Access-Accept exchange involving 1 UDP packet in each direction. however, other authentication methods (and it's not the question of user-name or password length) could require further challenges sent by your server and the number of exchanges can practically rise up to 5-6 and more (i.e. 5-6 UDP packets in each direction). also the packet length would change depending on the kind of challenges and responses sent. now, depending on the authorization tokes included, some of the packets sent by your server will be bigger or smaller, too. i don't know which parameters have to be included according to your politics. what i'm trying to say, is that the best man to answer this question is you. decide, what exactly you want to do, which limitation and rights you want to grant and how you want to authentify. then, grab the radius base RFC and count the bytes (analytic approach). alternatively, try a test authentication and record the data exchanged on the interface (simulative approach). regards, artur -- Artur Hecker artur[at]hecker.info - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
