(RADIATOR) Wireless Duplicates

[Frank Danielson]

Hi Andrew

If you look at the manual and find the section that covers the DupInterval
(it's section 6.5.4 in my manual) it explains Radiator's duplicate detection
mechanism. It looks like your access point is sending a request that is not
being answered by your Radiator instance and is then resending the request.
I'd try to find out why the requests are not being answered.

-Frank

-----Original Message-----
From: Andrew [mailto:andrewb at acenet.net.au]
Sent: Sunday, December 19, 2004 8:49 PM
To: radiator at open.com.au
Subject: (RADIATOR) Wireless Duplicates


Hi,

I am running Radiator 3.11. It has been running perfectly since upgrading
from 3.9, but out of the blue I got the below error in my logfile. Once this
error occurs, nobody is able to authenticate. 
Restarting the service via a HUP resolves the issue but I am just wondering
what is actually causing the issue, can anybody explain?
I am running authentication by file (no DB). So I can't figure out how
Radiator knows a request is a duplicate?

INFO: Duplicate request id 0 received from x.x.x.x(1494): ignored

The errors usually occur in this fashion;
The IP address is always the access point. The request Id cycles in the
order 0,0,1,1,2,2,3,3. The number in brackets increments by 1 with each
cycle. 

Thanks!

-- Andrew


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.