Yes, I read it and followed the instructions: added update coa statement in my default config. update coa { User-Name = "%{User-Name}" Acct-Session-Id = "%{Acct-Session-Id}" NAS-IP-Address = "%{NAS-IP-Address}" } Based on the following docs, it should sends COA to my NAS-IP but it doesn't: # The default destination of a CoA packet is the NAS (or client) # the sent the original Access-Request or Accounting-Request. See # raddb/clients.conf for a "coa_server" configuration that ties # a client to a specific home server, or to a home server pool.
Date: Wed, 19 Oct 2011 22:42:38 +0200 From: aland@deployingradius.com To: freeradius-users@lists.freeradius.org Subject: Re: setup freeradius to generateng COA
Alex rsm wrote:
FreeRadius not originating COA message due to the following error in the debug:
rad_recv: Access-Request packet from host 10.10.10.1 port 35664, id=254, length=43 User-Name = "test" User-Password = "abc123" # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default .... .... Sending Access-Accept of id 254 to 10.10.10.1 port 35664 WARNING: Unknown destination 10.10.10.1:3799 for CoA request. Do CoA Fail handler here
Is there any place I need to configure the COA destination?
Yes. Read raddb/sites-available/originate-coa
This is documented.
I said that in my previous message. Did you read it? If you did, you already know how to solve the problem. If you didn't read it, you're being rude by ignoring the people who try to help you.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html