Well, 191.255.249.72 is a machine out there trying to use your RADIUS
server. If you don't have any machines with that IP, someone out there
is hitting your server.
As I said when I replied to your direct mail the other day, dropping
duplicates is when the PM doesn't see a reply in time and it resends. So
the RADIUS server sees multiple requests for the same thing.
>One other rather odd thing, When I changed the Ip on the PM using the
>command:
>set ether0 addr 206.103.109.100 (different PM)
>Local (ether0) address changed from 206.103.109.91 to 206.103.109.100
Ok.
>At this point my telnet session was cut off. I tried to ping the
>PM and it didn't reply. I then tried to ping 206.103.109.100 and it
>replied. I was able to telnet to the server at 206.103.109.100, but
>radius was still showing the error message from 206.103.109.91. I
>did not save the settings and I did not reboot. It just changed IP
>addresses. (partially)
Changing IPs on an active unit is always messy. You need to save all and
reboot. I don't encourage messing with the settings of an interface when
you are connected over that interface if you can avoid it. ie, ether0 while
telnetted over it. If you can mess with ether0 from a console, or even a
dialin, you don't have to worry about cutting yourself off.
-MZ
-- Lucent Remote Access Division - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.