Re: byte ordering

Hi,

You shouldn't care about endianess. The real question is: host based
ordered or network based ordered ?

As we try to be coherent, all the parameters _should_ be passed being
host ordered. Then, if it is requiered, it is converted to network
order in the builder.

In the past, we made mistakes about the byte ordering. I hope we have
fix most of them, but unfortunately ... So if you notice a bug, let us
know.

	Fred Raynal

On Fri, Jun 25, 2004 at 01:31:35PM +0530, [email protected] wrote:
> 
> Hi,
> 
>    thanks Fred for the checksum answer. another doubt : libnet_build_ipv4
> help says theres a restriction on ulon src_addr and ulong dst_addr provided
> to it as parameters, they have to be little endian, does this limitation
> hold for libnet 1.1.2.1 also. I ask this as there are other fields where no
> such requirement is given for example in libnet_build_tcp atleast in the
> help its not given that seq_no, ack_no, src_port or dst_potr __have__ to be
> specified little endian ..
> 
> So what strategy shld a libnet user adopt, do libnet functions expect all
> multibyte numbers to be little endian ??
> 
> thanks
> Amit
> "DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
> (HSS) and is intended solely for the use of the individual to whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than for what it is
> intended. If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. HSS accepts no responsibility for
> loss or damage arising from the use of the information transmitted by this
> email including damage from virus."
>