[ previous ] [ next ] [ threads ]
 
 From:  Dirk Enrique Seiffert <ds at caribenet dot com>
 To:  m0n0wall list <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Radius Accounting
 Date:  Wed, 18 May 2005 11:19:29 -0500
We have tested several monowall versions (1.11, 1.2b5, 1.2b6, 1.2b7) in the 
hope to get radius accounting to work. As radius server we used FreeRadius 
and PyRadius. It took us a while until  we figured out that the http version 
of the captive portal is obsolete, only https will work - until 1.2b6.

1.2b6 and 1.2b7 seem not to send any Acct-Status-Type = Start packages, while 
the Acct-Status-Type = Stop look good.

Tue May 17 15:38:15 2005
        Service-Type = Login-User
        User-Name = "test"
        NAS-Identifier = "m0n0wall.local"
        NAS-Port = 0
        NAS-Port-Type = Ethernet
        Acct-Status-Type = Stop
        Acct-Authentic = RADIUS
        Acct-Session-Id = "b9cb8fa9e3762526"
        Acct-Terminate-Cause = User-Request
        Acct-Session-Time = 719
        Acct-Input-Octets = 6929909
        Acct-Input-Packets = 4822
        Acct-Output-Octets = 262148
        Acct-Output-Packets = 4367
        Called-Station-Id = "192.168.8.17"
        Calling-Station-Id = "192.168.1.2"
        Framed-IP-Address = 192.168.1.2
        NAS-IP-Address = 192.168.8.17
        Client-IP-Address = 192.168.8.17
        Acct-Unique-Session-Id = "32c2b2e07f7241ea"
        Timestamp = 1116362295

Monowall 1.2b5 sends Acct-Status-Type = Start, but no Calling Station ID. Also 
upload and download seem to be mixed up.

We are evaluating the use monowall Captive Portal with a radius-billing 
solution. This means that monowall has to disconnect when radius reports an 
account balnace in 0. Is there a way to achieve this with monowall? 

Any hint or experience is appreciated!

Best wishes

Enrique


-- 
Dirk Enrique Seiffert
CaribeNet S.A. - Cartagena - Colombia
www.caribenet.com