Alan, See my virtual server rif listen conf: server rif { listen { ipaddr = * port = 3812 type = auth } ..... ...... } If I try that, there is the same problem. log: rlm_sql (sql): Adding client 192.168.50.190 (AP07) to rif clients list rlm_sql (192.168.50.190): Client "AP07" (sql) added Listening on auth address * port 1812 as server default Listening on auth address * port 3812 as server rif Listening on status address * port 18121 as server status Listening on auth address 127.0.0.1 port 18120 as server inner-tunnel Ready to process requests Ignoring request to auth address * port 1812 as server default from unknown client 172.29.50.190 port 1645 proto udp Ready to process requests My nas is configured to send request to rif ( port 3812 ) If I don't use nas table but clients.conf, it works. Thanks. nicolas.clo@ricoh-industrie.fr wrote:
No sorry, it doesn't work
Yes, it does.
|7192.168.50.190|AP07|cisco|NULL|Password|rif|NULL|RADIUS Client
Public IP... going to virtual server "rif"
Listening on auth address * port 1812 as server default Listening on auth address 127.0.0.1 port 3812 as server rif
Virtual server "rif" is listening only on a local IP.
*Ignoring request to auth address * port 1812 as server default from unknown client 192.168.50.190 port 1645 proto udp*
The packet is being sent to address "*", not 127.0.0.1. So it won't ever be sent to the virtual server. I meant what I said in my previous message... clients are tied to a "listen" section, OR global. In this case, they're tied to the "listen" section which is listening on 127.0.0.1, port 3812. So packets sent to ANOTHER destination IP will never match that client. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html