Plenty of reasons - but one you won't have control over even in CoA is
that it could be proxied.
The NAS-IPAddress is used in the CoA request packet to tell the NAS
which client should receive the packet.
Marlon Duksa wrote:
Hi everyone -
Can anyone think of a reason why the NAS-IP and the s
--On 01 April 2010 09:39 -0700 Marlon Duksa wrote:
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
If the NAS-IP is configurable in the NAS, then the NAS-IP can be set to
the IP address other than the src-ip of the NAS
Marlon Duksa wrote:
> Can anyone think of a reason why the NAS-IP and the scr-IP of the
> access-req packet should not be the same?
Many. There is *no* requirement in RADIUS that they be identical.
When a packet is proxied, the NAS-IP-Address stays the same, but the
source IP changes.
Ala
On 04/01/2010 05:39 PM, Marlon Duksa wrote:
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
If the NAS-IP is configurable in the NAS, then the NAS-IP can be set to
the IP address other than the src-ip of the NAS that is us
> Hi everyone -
> Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
One of NAS is on the other side of a load balancer, source IP is not the
same as NAS-IP.
John
This message is confidential to Prodea Systems, Inc unless otherwise in
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the access-req
packet should not be the same?
If the NAS-IP is configurable in the NAS, then the NAS-IP can be set to the
IP address other than the src-ip of the NAS that is used in reqular
FreeRadius accounting/authorizat
6 matches
Mail list logo
