-------------| -> accounting request -> |-------| -------> |-------|
| Portmaster | |Radius1| |Radius2|
|------------| <- accounting reply <- |-------| <------- |-------|
Here is my current implementation (Radius1 is my hacked bouncing server):
1. Portmaster sends a request to Radius1. Radius1 logs the request, and
bounces the packet to Radius2. It does not reply to the accounting
request.
2. Radius2 receives the bounced request, logs it, and replies to it.
This reply goes to Radius1. Radius1 now bounces the accounting reply back
to the Portmaster so that it knows to stop sending the request.
Obviously, there are some problems with this implementation, one of which
being Radius1 may sometimes have duplicate records logged...
Another problem is that Radius1 has no real way of knowing which
Portmaster the request came from in the first place (right now I have it
hardcoded since its only being used by one portmaster). One solution I
thought of might be to add another data field indicating the originating
NAS, or perhaps there is already one??
------------------
Jordan Baker
Interhop Network Services Inc.
416.494.1603