Differences

This shows you the differences between two versions of the page.

--- b2f:b2f [2025/03/09 17:36] – f4hof
+++ b2f:b2f [2025/03/09 17:46] (current) – [Secure Gateway Login] f4hof
@@ Line 57: / Line 57: @@
 The exchange happens after the SID has been transmitted.
-The server sends a '';PQ'' proposal with an authentication challenge, which is formatted as follow:
+The server sends a '';PQ:'' proposal with an authentication challenge, which is formatted as follow:
-<code>;PQ 99685857</code>
+<code>;PQ: 99685857</code>
 The client computes the response using the following pseudocode:
@@ Line 108: / Line 108: @@
 The result is then sent to the server using the following format:
-<code>;PR 99685857</code>
+<code>;PR: 99685857</code>
 ABNF Grammar:
 <code abnf>
-B2F_AUTH_CHALLENGE = %x3B %x50 %x51 SP 8DIGIT CR
+B2F_AUTH_CHALLENGE = %x3B %x50 %x51 %x3A SP 8DIGIT CR
-B2F_AUTH_RESPONSE  = %x3B %x50 %x52 SP 8DIGIT CR
+B2F_AUTH_RESPONSE  = %x3B %x50 %x52 %x3A SP 8DIGIT CR
 </code>
 Reference source code in [[https://github.com/nwdigitalradio/paclink-unix/blob/1df400712a985045f2fce0d582a70763c2b2ba7b/wl2k.c#L1249|paclink-unix, function compute_secure_login_response()]] and [[https://github.com/la5nta/wl2k-go/blob/master/fbb/secure.go|wl2k-go]]
+==== Secure Gateway Login ====
+When a RMS connects to a CMS, the latter sends a login challenge with '';SQ:'' proposal.
+The auth scheme works the same way the Secure login does.
+The RMS answers with a triplet composed of the secure login response, the frequency the client is binding to (10 digit integer in Hertz), and the used mode.
+ABNF Grammar:
+<code abnf>
+B2F_GW_AUTH_CHALLENGE = %x3B %x53 %x51 %x3A SP 8DIGIT CR
+B2F_GW_AUTH_RESPONSE  = %x3B %x53 %x52 %x3A SP 8DIGIT SP 10DIGIT SP VCHAR CR
+</code>
 ===== Data transfer =====