Hi, > > But then the client won't get the acks and retransmit. If I understood > > correctly, then the problem is the packets *are* acked but not logged. > > Maybe my whole understanding of UDP is flawed, I thought the whole > point of using UDP instead of TCP is not to have ACKS and retransmits?
at the service level - the software has do deal with problems instead of the TCPIP stack. however, as Alan said. in single thread mode, you only have one process dealing with requests.....so one single open connection to SQL, one single sesion to LDAP etc etc (whatever you use) - eg even a local file with PERL. with multithread mode, you have many threads - all of which can be hitting your SQL or LDAP at same time...or trying to write to the same file in a PERL module....so you have to look at the speed/ability of your backend....the jump from a single query ata time to concurrent queries may have tipped your balance alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
