Freeradius 3.0.16 behind NAT
Hello, i am running freeradius 3.0.16 on Redhat 7.1 behind NAT, i have two servers keepalived + ipvsadm ande two servers freerdius, on keepalived iam using NAT when i test an accounting from a NAS i send request to the VIP but i get response directly from the radius server so recieved packet comes with source IP of freerdaius server and not the VIP, the nas rejected the packet: radclient: Received reply to request we did not send. (id=185 socket 3) the problem is i have the same architecture with freerdaius 3.0.4 and radclient same version and the NAS accepted the packet inspite source IP is for freeradius server and is not the VIP is there any difference between the two version on checking source IP packet? i would like the nas to ignore checking the source IP address of the packet is thsre any solution? Thanks in advance Mettichi Bassem
On May 2, 2018, at 11:03 AM, Bassem Mettichi <mettichi@gmail.com> wrote:
i am running freeradius 3.0.16 on Redhat 7.1 behind NAT, i have two servers keepalived + ipvsadm ande two servers freerdius, on keepalived iam using NAT
when i test an accounting from a NAS i send request to the VIP but i get response directly from the radius server so recieved packet comes with source IP of freerdaius server and not the VIP, the nas rejected the packet:
radclient: Received reply to request we did not send. (id=185 socket 3)
This question has been asked and answered on the list before. Please read the list archives.
the problem is i have the same architecture with freerdaius 3.0.4 and radclient same version and the NAS accepted the packet inspite source IP is for freeradius server and is not the VIP
No, it does not do that.
is there any difference between the two version on checking source IP packet?
No.
i would like the nas to ignore checking the source IP address of the packet is thsre any solution?
Fix your network. As you were told before. Alan DeKok.
participants (2)
-
Alan DeKok -
Bassem Mettichi