thanks for the reply - multiple source ports is the obvious answer which i didn't trust was actually specified in the RFCs. The reason for this is that too often i have seen requests from 1645 to 1645 and not (random-high-port to 1645) for example.
extendid ID? well some radius servers will extend the 8-bit Identifier into a "proxy-state" part of the packetm effectively extending the 8bit length. in freeradius - is that 8k requests per thread? or does the freeradius proxy not use threads to handle the proxy states - is it a central state-table? i was hoping the threads handled the proxying becasue then i can set the initial pool size and max-pool size (where each thread has space for say 500 pending proxy results). t ----------- FreeRADIUS allows 8k *active* requests to any home server. That's more than enough for major deployments. > i know that not all devices and target radius servers implement the > extended id which effectively expands the range from 256) Extended ID? What's that? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
