Sponsored Content
Full Discussion: Endian issues in TCP/IP
Top Forums UNIX for Advanced & Expert Users Endian issues in TCP/IP Post 16429 by Perderabo on Friday 1st of March 2002 09:24:26 AM
Old 03-01-2002
Your question is very confusing. I don't know if you are trying to port software or write a TCP/IP program.

Endian-ness is decided by the hardware not the the software. If an OS wants to use integer arithmetic, it must go along with what the hardware designers did. A very few cpu's are, um, bi-endian, but most have a preference.

HP hardware is big-endian.

TCP/IP does not even assume that computers have 8 bit bytes, which is why it calls 8 bits an "octet". 32 bit and 16 bit quantities travel over the network in big endian form. But portable programs access them via macros defined in the include file arpa/inet.h. The macros are ntohl, ntohs, htonl, htons. They stand for stuff like "network to host short". With big endian computers, these macros are null. But you should still use them. That way your code works on other computers. Only the macros need to be rewritten.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX endian again

Hi all I know AIX is big-endian machine.But does it read bytes in normal way from LSB. Does it happen in some machine that at multi-byte integer level it is Little-endian and while reading a single byte it is Big-Endian. This is urgent Thanks in advance. (3 Replies)
Discussion started by: Shobhit
3 Replies

2. Programming

Big and Little Endian

We are developing an application using TLI for network communication.The Server Code is developed in Sun and client in SCO unix. When we route data from Client to Server we encrypt the data using DES algotithm utility.The problem we are facing that Sun uses Big Endian methodology to store data in... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies

3. UNIX for Advanced & Expert Users

Endian Conversion

Hi everybody, I met this week a problem. For now, we used TRU64 system based on alpha. Now, we're installing UP-UX systems (on Itanium). And we have problem with our files. Indeed, we use file with COMP-3, COMP-5 data. These files are used on both platforms. (we use also TXT files which... (1 Reply)
Discussion started by: bigmike59270
1 Replies

4. UNIX for Dummies Questions & Answers

Little Endiean and Big Endian

Dear Friends, I have one question in my mind. That question is "how to detect whether the system is little endiean or big endian" Processing the bit position is the difference between this endians. But I could not understand how to find the pariticular sytem works... (3 Replies)
Discussion started by: Nirmal Babu
3 Replies

5. UNIX and Linux Applications

Migrating Oracle from Big Endian to Little Endian Platorm

Hi, We are trying to migrate an oracle database from Sun Solaris (SunOS 5.9 Generic_118558-28 sun4u sparc SUNW,Ultra-60) to Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux which is basically a Big Endian to Little Endian conversion. We shutdown... (3 Replies)
Discussion started by: luft
3 Replies

6. Solaris

question about the little-endian in sparc

hi folks, in the sparc v9 manul , it says it is possible to access the memory data in little-endian mode, but there is only privilaged instruction that could set the PSTATE ( the cle bit ) regist. if I'm in the user mode , is it possible for me to access the data in little-endian mode? (10 Replies)
Discussion started by: zerocool_08
10 Replies

7. BSD

FreeBSD AMD NFS over TCP issues

Hi! I have a major issue with FreeBSD 7.1 i386. We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp. Now I cant mount homedirs since NFS/AMD seem to fallback to udp :( Trying to force it with amd options nfs_proto=tcp and so on. ... (0 Replies)
Discussion started by: Esaia
0 Replies

8. Solaris

Too much TCP retransmitted and TCP duplicate on server Oracle Solaris 10

I have problem with oracle solaris 10 running on oracle sparc T4-2 server. Os information: 5.10 Generic_150400-03 sun4v sparc sun4v Output from tcpstat.d script TCP bytes: out outRetrans in inDup inUnorder 6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies

9. UNIX and Linux Applications

Endian vs pfsense??

Hi Endian firewall free version if we do compare pfsense For a LAN network with active user 1000 Which do you recommend Share (0 Replies)
Discussion started by: mnnn
0 Replies
ENDIAN(3)						     Linux Programmer's Manual							 ENDIAN(3)

NAME
htobe16, htole16, be16toh, le16toh, htobe32, htole32, be32toh, le32toh, htobe64, htole64, be64toh, le64toh - convert values between host and big-/little-endian byte order SYNOPSIS
#define _BSD_SOURCE /* See feature_test_macros(7) */ #include <endian.h> uint16_t htobe16(uint16_t host_16bits); uint16_t htole16(uint16_t host_16bits); uint16_t be16toh(uint16_t big_endian_16bits); uint16_t le16toh(uint16_t little_endian_16bits); uint32_t htobe32(uint32_t host_32bits); uint32_t htole32(uint32_t host_32bits); uint32_t be32toh(uint32_t big_endian_32bits); uint32_t le32toh(uint32_t little_endian_32bits); uint64_t htobe64(uint64_t host_64bits); uint64_t htole64(uint64_t host_64bits); uint64_t be64toh(uint64_t big_endian_64bits); uint64_t le64toh(uint64_t little_endian_64bits); DESCRIPTION
These functions convert the byte encoding of integer values from the byte order that the current CPU (the "host") uses, to and from little- endian and big-endian byte order. The number, nn, in the name of each function indicates the size of integer handled by the function, either 16, 32, or 64 bits. The functions with names of the form "htobenn" convert from host byte order to big-endian order. The functions with names of the form "htolenn" convert from host byte order to little-endian order. The functions with names of the form "benntoh" convert from big-endian order to host byte order. The functions with names of the form "lenntoh" convert from little-endian order to host byte order. VERSIONS
These functions were added to glibc in version 2.9. CONFORMING TO
These functions are nonstandard. Similar functions are present on the BSDs, where the required header file is <sys/endian.h> instead of <endian.h>. Unfortunately, NetBSD, FreeBSD, and glibc haven't followed the original OpenBSD naming convention for these functions, whereby the nn component always appears at the end of the function name (thus, for example, in NetBSD, FreeBSD, and glibc, the equivalent of OpenB- SDs "betoh32" is "be32toh"). NOTES
These functions are similar to the older byteorder(3) family of functions. For example, be32toh() is identical to ntohl(). The advantage of the byteorder(3) functions is that they are standard functions available on all UNIX systems. On the other hand, the fact that they were designed for use in the context of TCP/IP means that they lack the 64-bit and little-endian variants described in this page. EXAMPLE
The program below display the results of converting an integer from host byte order to both little-endian and big-endian byte order. Since host byte order is either little-endian or big-endian, only one of these conversions will have an effect. When we run this program on a little-endian system such as x86-32, we see the following: $ ./a.out x.u32 = 0x44332211 htole32(x.u32) = 0x44332211 htobe32(x.u32) = 0x11223344 Program source #include <endian.h> #include <stdint.h> #include <stdio.h> #include <stdlib.h> int main(int argc, char *argv[]) { union { uint32_t u32; uint8_t arr[4]; } x; x.arr[0] = 0x11; /* Lowest-address byte */ x.arr[1] = 0x22; x.arr[2] = 0x33; x.arr[3] = 0x44; /* Highest-address byte */ printf("x.u32 = 0x%x ", x.u32); printf("htole32(x.u32) = 0x%x ", htole32(x.u32)); printf("htobe32(x.u32) = 0x%x ", htobe32(x.u32)); exit(EXIT_SUCCESS); } SEE ALSO
byteorder(3) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. GNU
2010-09-10 ENDIAN(3)
All times are GMT -4. The time now is 06:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy