106N/A<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">

106N/A

106N/A

106N/A<refentry>

106N/A

727N/A<refentryinfo>

106N/A<date>Jun 30, 2000</date>

106N/A</refentryinfo>

106N/A

106N/A<refmeta>

106N/A<refentrytitle>lwres_gnba</refentrytitle>

106N/A<manvolnum>3</manvolnum>

618N/A<refmiscinfo>BIND9</refmiscinfo>

106N/A</refmeta>

106N/A

844N/A<refnamediv>

844N/A<refname>lwres_gnbarequest_render</refname>

106N/A<refname>lwres_gnbaresponse_render</refname>

106N/A<refname>lwres_gnbarequest_parse</refname>

106N/A<refname>lwres_gnbaresponse_parse</refname>

106N/A<refname>lwres_gnbaresponse_free</refname>

106N/A<refname>lwres_gnbarequest_free</refname>

106N/A<refpurpose>lightweight resolver getnamebyaddress message handling</refpurpose>

106N/A</refnamediv>

106N/A

106N/A<refsynopsisdiv>

106N/A

181N/A<funcsynopsis>

727N/A<funcsynopsisinfo>

727N/A#include &lt;lwres/lwres.h&gt;

727N/A</funcsynopsisinfo>

106N/A

106N/A<funcprototype>

247N/A<funcdef>

247N/Alwres_result_t

247N/A<function>lwres_gnbarequest_render</function>

247N/A</funcdef>

247N/A<paramdef>lwres_context_t *<parameter>ctx</parameter></paramdef>

247N/A<paramdef>lwres_gnbarequest_t *<parameter>req</parameter></paramdef>

247N/A<paramdef>lwres_lwpacket_t *<parameter>pkt</parameter></paramdef>

106N/A<paramdef>lwres_buffer_t *<parameter>b</parameter></paramdef>

106N/A</funcprototype>

106N/A

106N/A<funcprototype>

<funcdef>

lwres_result_t

<function>lwres_gnbaresponse_render</function>

</funcdef>

<paramdef>lwres_context_t *ctx</paramdef>

<paramdef>lwres_gnbaresponse_t *req</paramdef>

<paramdef>lwres_lwpacket_t *pkt</paramdef>

<paramdef>lwres_buffer_t *b</paramdef>

</funcprototype>

<funcprototype>

<funcdef>

lwres_result_t

<function>lwres_gnbarequest_parse</function></funcdef>

<paramdef>lwres_context_t *ctx</paramdef>

<paramdef>lwres_buffer_t *b</paramdef>

<paramdef>lwres_lwpacket_t *pkt</paramdef>

<paramdef>lwres_gnbarequest_t **structp</paramdef>

</funcprototype>

<funcprototype>

<funcdef>

lwres_result_t

<function>lwres_gnbaresponse_parse</function></funcdef>

<paramdef>lwres_context_t *ctx</paramdef>

<paramdef>lwres_buffer_t *b</paramdef>

<paramdef>lwres_lwpacket_t *pkt</paramdef>

<paramdef>lwres_gnbaresponse_t **structp</paramdef>

</funcprototype>

<funcprototype>

<funcdef>

void

<function>lwres_gnbaresponse_free</function>

</funcdef>

<paramdef>lwres_context_t *ctx</paramdef>

<paramdef>lwres_gnbaresponse_t **structp</paramdef>

</funcprototype>

<funcprototype>

<funcdef>

void

<function>lwres_gnbarequest_free</function></funcdef>

<paramdef>lwres_context_t *ctx</paramdef>

<paramdef>lwres_gnbarequest_t **structp</paramdef>

</funcprototype>

</funcsynopsis>

</refsynopsisdiv>

<refsect1>

<title>DESCRIPTION</title>

<para>

These are low-level routines for creating and parsing

lightweight resolver address-to-name lookup request and

response messages.

</para>

<para>

There are four main functions for the getnamebyaddr opcode.

One render function converts a getnamebyaddr request structure &mdash;

<type>lwres_gnbarequest_t</type> &mdash;

to the lightweight resolver's canonical format.

It is complemented by a parse function that converts a packet in this

canonical format to a getnamebyaddr request structure.

Another render function converts the getnamebyaddr response structure &mdash;

<type>lwres_gnbaresponse_t</type>

to the canonical format.

This is complemented by a parse function which converts a packet in

canonical format to a getnamebyaddr response structure.

</para>

<para>

These structures are defined in

<filename>lwres/lwres.h</filename>.

They are shown below.

<programlisting>

#define LWRES_OPCODE_GETNAMEBYADDR 0x00010002U

typedef struct {

lwres_uint32_t flags;

lwres_addr_t addr;

} lwres_gnbarequest_t;

typedef struct {

lwres_uint32_t flags;

lwres_uint16_t naliases;

char *realname;

char **aliases;

lwres_uint16_t realnamelen;

lwres_uint16_t *aliaslen;

void *base;

size_t baselen;

} lwres_gnbaresponse_t;

</programlisting>

</para>

<para>

<function>lwres_gnbarequest_render()</function>

uses resolver context

<varname>ctx</varname>

to convert getnamebyaddr request structure

<varname>req</varname>

to canonical format.

The packet header structure

<varname>pkt</varname>

is initialised and transferred to

buffer

<varname>b</varname>.

The contents of

<varname>*req</varname>

are then appended to the buffer in canonical format.

<function>lwres_gnbaresponse_render()</function>

performs the same task, except it converts a getnamebyaddr response structure

<type>lwres_gnbaresponse_t</type>

to the lightweight resolver's canonical format.

</para>

<para>

<function>lwres_gnbarequest_parse()</function>

uses context

<varname>ctx</varname>

to convert the contents of packet

<varname>pkt</varname>

to a

<type>lwres_gnbarequest_t</type>

structure.

Buffer

<varname>b</varname>

provides space to be used for storing this structure.

When the function succeeds, the resulting

<type>lwres_gnbarequest_t</type>

is made available through

<varname>*structp</varname>.

<function>lwres_gnbaresponse_parse()</function>

offers the same semantics as

<function>lwres_gnbarequest_parse()</function>

except it yields a

<type>lwres_gnbaresponse_t</type>

structure.

</para>

<para>

<function>lwres_gnbaresponse_free()</function>

and

<function>lwres_gnbarequest_free()</function>

release the memory in resolver context

<varname>ctx</varname>

that was allocated to the

<type>lwres_gnbaresponse_t</type>

or

<type>lwres_gnbarequest_t</type>

structures referenced via

<varname>structp</varname>.

Any memory associated with ancillary buffers and strings for those

structures is also discarded.

</para>

</refsect1>

<refsect1>

<title>RETURN VALUES</title>

<para>

The getnamebyaddr opcode functions

<function>lwres_gnbarequest_render()</function>,

<function>lwres_gnbaresponse_render()</function>

<function>lwres_gnbarequest_parse()</function>

and

<function>lwres_gnbaresponse_parse()</function>

all return

<errorcode>LWRES_R_SUCCESS</errorcode>

on success.

They return

<errorcode>LWRES_R_NOMEMORY</errorcode>

if memory allocation fails.

<errorcode>LWRES_R_UNEXPECTEDEND</errorcode>

is returned if the available space in the buffer

<varname>b</varname>

is too small to accommodate the packet header or the

<type>lwres_gnbarequest_t</type>

and

<type>lwres_gnbaresponse_t</type>

structures.

<function>lwres_gnbarequest_parse()</function>

and

<function>lwres_gnbaresponse_parse()</function>

will return

<errorcode>LWRES_R_UNEXPECTEDEND</errorcode>

if the buffer is not empty after decoding the received packet.

These functions will return

<errorcode>LWRES_R_FAILURE</errorcode>

if

<structfield>pktflags</structfield>

in the packet header structure

<type>lwres_lwpacket_t</type>

indicate that the packet is not a response to an earlier query.

</para>

</refsect1>

<refsect1>

<title>SEE ALSO</title>

<para>

<citerefentry>

<refentrytitle>lwres_packet</refentrytitle>

<manvolnum>3</manvolnum>

</citerefentry>.

</para>

</refsect1>

</refentry>