(RADIATOR) Testing Radius traffic

[Claudio Lapidus]

Hello all,

Now this may sound a little crazy, but...

We're finishing a development for a billing application. In order to
ascertain how resilient it is to network faults, we're trying to setup a
test scenario with known failure rates at the Radius packet transmission
stages. The basic idea is to setup a PreClientHook that drops a configured
percentage of the incoming packets, something like

sub
{
    my $p = ${$_[0]};
    my $r = rand;

    if ($r < 0.3) {    # discards 30% of incoming traffic
        #
        # discard packet here, perhaps log it
        #
    }
}

so the question is how to instruct the hook to discard the packet
completely, preventing further processing?

Second one: to implement the same 'induced error' for the reply side, I
think PostAuthHook is perhaps the proper place, to simulate the case where
the response get lost after the transaction was correctly registered at the
server side. The point here is if it is possible to intercept the reply in
some way, before it gets transmitted.

As a side note, I try to use these hooks in order to alter the server
configuration at the least possible degree. I'm aware that it may be simpler
to alter the packet in some way as to force a particular handler, etc., but
I'd prefer to simply discard the whole packet altogether.

Comments?
cl.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.