> I suspect the problem is in the radius configuration not the port master
> and the clients file was updated with various combinations to no avail.
> Could some one point out what I am missing . . . . .
AFAIK, the radius server binds to all IPs on the machine, so there is no
need for a configuration change.
It's more likely that the radius server is using the wrong return address
to talk to the NAS. The NAS then ignores the response and issues another
request for authentication, resulting in a "dropping duplicate request"
message.
I would change the primary config on your ethernet interface to be the
*new* IP and reconfigure all of the NAS to point to that new IP. Don't
put the old on on there until you're sure the new one works. One you get
the new one working, *then* add the old one. Do *not* put the old
deprecated IP in the NAS anywhere.
Hopefully this will solve, or put you on the road to solving, your
problem.
Chad Scott | chad@txdirect.net
Network Operations | Voice 210-308-9800 x206
Internet Direct, Incorporated | FAX 210-308-9240
=========================================================
Finger chad@txdirect.net for PGP Public Key
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.