Searched full:rfc1048 (Results 1 – 18 of 18) sorted by relevance
4 * Bootstrap Protocol (BOOTP). RFC951 and RFC1048.65 * Vendor magic cookie (v_magic) for RFC104872 * RFC1048 tag values used to specify what information is being supplied in
258 * memory buffer indirectly pointed to by "dest". "tag" is the RFC1048 tag266 * conformance to RFC1048.301 * be in RFC1048 format. It is inserted using a first-fit algorithm which
306 .Em rfc1048428 DARPA Internet Request For Comments RFC951, RFC1048, RFC1084, Assigned Numbers
272 Add generic tags. Fix byte order of rfc1048 data.277 Added vendor information to conform to RFC1048.
29 RFC1048. We've also improved the host lookup algorithm and added some
146 * hold future RFC1048 vendor data until bootpd is updated to understand it.
87 * Vendor magic cookie (v_magic) for RFC1048
29 * See [SRI-NIC]<RFC>RFC1048.TXT for vendor-information extensions.963 /* RFC1048 conformant bootp client */ in handle_request()966 report(LOG_INFO, "sending reply (with RFC1048 options)"); in handle_request()1212 * Insert the RFC1048 vendor data for the host pointed to by "hp" into the
11 # in addition to the RFC1048 format. Leaving out DEBUG saves little.
256 fprintf(fp, "rfc1048:"); in dump_host()
271 * Vendor magic cookies for CMU and RFC10481211 * Load RFC1048 generic information directly into a memory buffer.
54 .%O RFC1048
116 * Vendor magic cookies for CMU and RFC1048
36 * Bootstrap Protocol (BOOTP). RFC951 and RFC1048.83 * Vendor magic cookie (v_magic) for RFC104888 * RFC1048 tag values used to specify what information is being supplied in407 /* RFC1048 tags */595 ND_PRINT("\n\t Vendor-rfc1048 Extensions"); in rfc1048_print()
205 hn:ht=1:vm=rfc1048:\\
236 * and the more modern, BOOTP way. (RFC951, RFC1048)
326 if (!strcasecmp(atom + 1, "lways-reply-rfc1048")) in intern()
1188 *vendp++ = 99; /* RFC1048 cookie */ in bootpc_compose_query()