Store Access-Request packet information in database
Phil Mayers
p.mayers at imperial.ac.uk
Mon Oct 11 12:59:51 CEST 2010
On 11/10/10 11:22, c.schwarz at funknetz.at wrote:
> Hi,
>
> I would like to achieve some kind of a tracking system for 802.11
> wireless clients, therefore every login attempt should be accepted and
> the necessary information (e.g. nas-ip-address, calling-station-id)
> should be stored in an extra database table.
>
> Example output:
> rad_recv: Access-Request packet from host 192.168.30.216 port 43128,
> id=5, length=200
> NAS-Port-Type = Wireless-802.11
> Calling-Station-Id = "00:1A:73:59:25:4B"
> Called-Station-Id = "hotspot1"
> NAS-Port-Id = "wlan1"
> User-Name = "christoph"
> NAS-Port = 2152726535
> Acct-Session-Id = "80500007"
> Framed-IP-Address = 10.50.0.254
> Mikrotik-Host-IP = 10.50.0.254
> CHAP-Challenge = 0x12321805f00ad380736bd946aefe0389
> CHAP-Password = 0x1153fcb1c99609b962baa8042aca266905
> Service-Type = Login-User
> WISPr-Logoff-URL = "http://10.50.0.1/logout"
> NAS-Identifier = "test-loop21"
> NAS-IP-Address = 192.168.30.216
>
> Does anybody have an idea how to store this kind of information when
> freeradius receives an access-request packet?
Yes. Use the "sql" module.
This is well documented. Have you read any of the docs?
More information about the Freeradius-Users
mailing list