/* SPDX-License-Identifier: LGPL-2.1 */ /* * * Protocol Data Unit definitions for RFC 1001/1002 support * * Copyright (c) International Business Machines Corp., 2004 * Author(s): Steve French ([email protected]) * */ /* NB: unlike smb/cifs packets, the RFC1002 structures are big endian */ /* RFC 1002 session packet types */ #define RFC1002_SESSION_MESSAGE … #define RFC1002_SESSION_REQUEST … #define RFC1002_POSITIVE_SESSION_RESPONSE … #define RFC1002_NEGATIVE_SESSION_RESPONSE … #define RFC1002_RETARGET_SESSION_RESPONSE … #define RFC1002_SESSION_KEEP_ALIVE … /* RFC 1002 flags (only one defined */ #define RFC1002_LENGTH_EXTEND … struct rfc1002_session_packet { … } __attribute__((packed)); /* Negative Session Response error codes */ #define RFC1002_NOT_LISTENING_CALLED … #define RFC1002_NOT_LISTENING_CALLING … #define RFC1002_NOT_PRESENT … #define RFC1002_INSUFFICIENT_RESOURCE … #define RFC1002_UNSPECIFIED_ERROR … /* RFC 1002 Datagram service packets are not defined here as they are not needed for the network filesystem client unless we plan on implementing broadcast resolution of the server ip address (from server netbios name). Currently server names are resolved only via DNS (tcp name) or ip address or an /etc/hosts equivalent mapping to ip address.*/ #define DEFAULT_CIFS_CALLED_NAME …