ovpn_opcode_compose(9)
β¨ NAME β¨
okay so bestie, welcome to ovpn_opcode_compose(9) from the Kernel API Manual π this one is literally about combining an OP code, a key ID, and a peer ID into wire format. slay.
π SYNOPSIS π
u32 ovpn_opcode_compose (u8 opcode , u8 key_id , u32 peer_id );
no cap, that's the whole signature π«Ά
πΈ ARGUMENTS πΈ
opcodeβ the OP code β¨key_idβ the key ID πpeer_idβ the peer ID π―
π¦ RETURN π¦
it gives you back a 4 bytes integer obtained by combining all the input values following the OpenVPN wire format. then you can write that integer to the packet header. periodt π
π SEE ALSO π
- Kernel file
./drivers/net/ovpn/proto.h ovpn_opcode_from_skb(9)ovpn_peer_id_from_skb(9)ovpn_key_id_from_skb(9)
π bestie, that's the whole vibe:opcode+key_id+peer_idgo in, a wire-formatu32comes out, and it's ready for the packet header. iconic.
mwah π this little page lives under ./drivers/net/ovpn, the date on the footer is October 2026, and the manual tag is ovpn_opcode_compose(9) β catch you in the group chat πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms