Packet identifier number

[retailnext]

Packet identifier number

[psanford]

The identifier field for a radius packet is only 1 byte. See https://tools.ietf.org/html/rfc2865 section 3 for details:

"The Identifier field is one octet, and aids in matching requests
and replies. The RADIUS server can detect a duplicate request if
it has the same client source IP address and source UDP port and
Identifier within a short span of time."

The identifier only needs to be unique for a specific ip:port pair. If you need to handle more than 255 concurrent in flight requests from a single device you can use multiple ports.

[sizovilya]

@psanford thank you for response.
I use next schema:
UI(gw) --> Node.js --> Remote Radius Server.
I think, if node.js server will receive any parallel requests from UI and will send this requests to remote radius, im not have guarantee for right response ordering to clients, right ? Client B, by default, can get UDP packet which intended for Client A, right ? Is it not realized on system\package level and i must realize it myself, right ? Or with 'identifier' parameter it works automatically ?

[psanford]

I don't think I have enough information to answer your question. Are you using node-radius as a client, a
server or both?

[sizovilya]

@psanford only as a client.

[psanford]

One simple solution would be to use a different udp port (making a new udp socket object) for each request. On the udp socket you can call .bind(0) which will bind to a random available port. Then you don't need to track the packets by the identifier field since you know that each socket will only be used to send 1 packet.

[sizovilya]

@psanford
I think it very fast, but not good solution, because all ports should be opened.
Okey, i understand. I need simple requests query mechanism.

Thank you !