Some Questions About Client Authorize about fsd-doc

[aleccai8]

And the @s the num 3 or 4 i think is a pbh and decode it can get petch bank heading

[norrisng]

You don't have to implement the challenge-response authentication (I'm assuming you're talking about the $ZC/$ZR stuff?). That's just what VATSIM implemented to shut out clients it hasn't authorized. Notice how IVAO doesn't have this mechanism.

You could just have your implementation accept the connection as long as the login credentials are correct.

[norrisng]

And regarding @S, are you referring to (num1) and (num2)? There's no num3/4.

[aleccai8]

@s:(callsign):(squawk):(rating):(lat):(lon):(alt):(groundspeed):(num1):(num2)

sorry about that i think the num1 the pbh and num2 is flag(in open sourse fsd)but i dont know what its work

[norrisng]

Hmm, good point.....it would make sense for the pitch/bank/heading data to be encoded inside a @N/S packet, since it doesn't seem to appear anywhere else.

I'll have to investigate further once I have the time to poke around in a sim while connected though. I can't quite figure out how P/B/H are encoded in (num1) from the Wireshark traces I have with me at the moment.

By "flag", I'm assuming you're referring to the <identflag> field for PD (pilotdata)? I think that's referring to the @N/S thing (and I don't know what it's supposed to mean either). The original FSD documentation's PD packet is essentially identical to VATSIM/IVAO's implementation, except for the PD at the front, and the (num1/2) fields.

[phoudoin]

(num1) is indeed encoded P/B/H
(num2) is difference between AGL and AMSL altitudes