Not processing accounting packet

[Alan DeKok]

Tyller D wrote:
> The process I'm using is as follows. User connects to landing page,
> landing page sends access-request to server with users details.
> FreeRADIUS then sends a COA to the NAS to change the state and apply
> attributes. However when FreeRADIUS gets the accounting-start packet, it
> does nothing with it. Can someone please tell me how I can log this
> normally in radacct table? In my accounting section i have accounting {
> sql }

  So... you butchered the configuration files, and now are wondering why
it doesn't work.

> rad_recv: Accounting-Request packet from host 172.16.255.35 port 20000,
> id=200, length=244
>         Acct-Status-Type = Start
>         Acct-Multi-Session-Id = "SESS-464-72c952-395089-4201e"
>         Acct-Session-Id = "SESS-464-72c952-395089-4201e"
>         User-Name = "10269783"
>         Event-Timestamp = "May  1 2013 09:58:34 SAST"
>         Trapeze-VLAN-Name = "DataA"
>         Calling-Station-Id = "04-54-53-85-CA-82"
>         NAS-Port-Id = "AP13/2"
>         Called-Station-Id = "AC-4B-C8-02-23-41:BTC HOTSPOT - FAIRGROUND"
>         Trapeze-Attr-19 = 0x69706164
>         Trapeze-Attr-21 = 0x696f73
>         NAS-Port = 464
>         Framed-IP-Address = 172.16.100.18
>         NAS-Port-Type = Wireless-802.11
>         NAS-IP-Address = 172.16.255.35
>         NAS-Identifier = "XON"
>         Acct-Delay-Time = 0
>   WARNING: Empty preacct section.  Using default return values.
>   WARNING: Empty accounting section.  Using default return values.

  Maybe that's a hint.

  The entire point of the debug output is to READ IT.  It's not rocket
science.  There's a bunch of stuff, followed by

	WARNING ARE YOU SURE THIS IS RIGHT

  Which may be a message you want to read and think about.

  My suggestion is this:

1) don't butcher the default configurations.  It's clear you don't know
what they do, but you destroyed them anyways

2) do use the default examples, with only minor edits.  Use the method
suggested in "man radiusd".  It's really very simple

3) read the debug output.  Look for WARNING or ERROR.  It's that easy

  Alan DeKok.