Proxy CoA packet from network control to NAS(same as CoA server) configs in case of many many NASes.
Alan DeKok
aland at deployingradius.com
Thu Jul 16 19:47:36 CEST 2015
On Jul 16, 2015, at 9:14 AM, Sergey Komarov <sergey.komaroff at gmail.com> wrote:
> Yes, I've tried to do so.
> In case I write as you said I get:
>
> Waking up in 0.4 seconds.
> (22) Received CoA-Request Id 187 from 10.1.1.1:17809 to 10.1.1.174:3799
> length 113
> (22) User-Name = "78-6c-1c-94-d2-07"
> (22) Calling-Station-Id = "78-6c-1c-94-d2-07"
> (22) Cisco-AVPair = "subscriber:command=account-reauthenticate"
> (22) NAS-IP-Address = 10.56.33.190
> (22) # Executing section recv-coa from file
> /usr/local/etc/raddb/sites-enabled/coa
> (22) recv-coa {
> (22) [suffix] = noop
> (22) update control {
> (22) Packet-Dst-IP-Address := &NAS-IP-Address -> 10.56.33.190
> (22) Packet-Dst-Port := 1700
> (22) } # update control = noop
> (22) [ok] = ok
> (22) } # recv-coa = ok
> *No such home server 10.56.33.190 port 14346*
Upgrade to 3.0.9.
http://freeradius.org/press/index.html#3.0.9
* Fix proxy to Packet-Dst-IP-Address, so that it uses the correct destination port.
Alan DeKok.
More information about the Freeradius-Users
mailing list