The answer is yes, but you probably want to start using a messge headers, that way everybody can decode what the incoming message is.
example:
Code:
the header template is nnnnXX[data]
where nnnn is the length of the packet, XX is a pre-agreed upon text code to tell you what the [data] is.
0010DT[raw integer]
This says "I sent you a raw integer": the way it is stored memory (4 bytes)
because the header is 6 bytes long 6 + 4 = 10 which is the whole length of the entire packet.
0011TXAABfd
I sent you an eleven byte message, the last five are text characters.
you decide what to use in XX. AK is commonly used as "I got it ok", NK (NAK) means I did not get your message. You could make your header template nnnnXXX[data] if you want more descriptive mesage types.
This User Gave Thanks to jim mcnamara For This Post:
Hi,
I want to know how to send a mail in unix using mailx or mail or sendmail to send a mail with a file attached. I have read the answers from the other threads but I still don't understand. I want to do it in the command line as well as in script.
Can anyone help? DO I need to use... (1 Reply)
Can someone email me a copy of this file? Our AIX 5 cds are at our hotsite and I need a copy to try a fix on a printer.
flyingdutchman1978@gmail.com
Thanks! (0 Replies)
if test.dat is the file
cat test.dat|uuencode test.dat|mailx -s "subject" mailid
can be used for attaching test.dat
how can i attach more than one file to a mail using mailx (2 Replies)
Hii can anyone pls tell how to limit the max no of message in a posix message queue. I have made changes in proc/sys/fs/mqueue/msg_max
But still whenever i try to read the value of max. message in the queue using attr.mq_curmsgs (where struct mq_attr attr) its giving the default value as 10.... (0 Replies)
hi
I know this topic has been discussed a lot in the forum but still couldnt get a exact solution to problem i am facing
I have a CSV file genertaed on Unix box and want to be sent to my email .
mailx -s "TEST" "xyz@hotmail.com" < 1.csv
cat 1.csv | mailx -s "TEST" "xyz@hotmail.com"
... (10 Replies)
Hi All,
Can any-one explain me how update on attach works on solaris zones.
Here is the situation .
I am trying to migrate a zones xx-xxx-xxx from Global zone A to Global zone B.
Here is the error message zoneadm is displaying
zoneadm: zone 'xx-xx-xxx': ERROR: attempt to downgrade... (0 Replies)
Hi,
Code written in C++ got compiled successfully using Sun 4.2 Compiler on Solaris 6. As part of migration, i am using same code and trying to compile using Sun 5.8 C++ compiler(Sun Studio11) on Solaris 10 and could not compile the below line,
outStr.attach(1); // here outStr is declared... (1 Reply)
Hi guys.
I'm studding XEN virtualization with 'The Book Of XEN'. in page 46 it has a statement about how to use xm block-attach command that I don't understand.
here is the command:
xm block-attach 0 tap:aio:/opt/xen/anthony.img /dev/xvda1 w 0and here is sentence:
we are attaching anthony.img... (1 Reply)
Hi All,
I am having trouble with my metadevices and I hope someone can help.
when i try to attach my submirror i get the following error:
root@xxxx>metattach d31 d21
metattach: tbair1: d21: submirror too small to attach
root@xxxx>
However, There is a submirror on the other disk which is... (3 Replies)
Discussion started by: A-Train
3 Replies
LEARN ABOUT PHP
pcap-savefile
PCAP-SAVEFILE(5) File Formats Manual PCAP-SAVEFILE(5)NAME
pcap-savefile - libpcap savefile format
DESCRIPTION
NOTE: applications and libraries should, if possible, use libpcap to read savefiles, rather than having their own code to read savefiles.
If, in the future, a new file format is supported by libpcap, applications and libraries using libpcap to read savefiles will be able to
read the new format of savefiles, but applications and libraries using their own code to read savefiles will have to be changed to support
the new file format.
``Savefiles'' read and written by libpcap and applications using libpcap start with a per-file header. The format of the per-file header
is:
+------------------------------+
| Magic number |
+--------------+---------------+
|Major version | Minor version |
+--------------+---------------+
| Time zone offset |
+------------------------------+
| Time stamp accuracy |
+------------------------------+
| Snapshot length |
+------------------------------+
| Link-layer header type |
+------------------------------+
All fields in the per-file header are in the byte order of the host writing the file. The first field in the per-file header is a 4-byte
magic number, with the value 0xa1b2c3d4. The magic number, when read by a host with the same byte order as the host that wrote the file,
will have the value 0xa1b2c3d4, and, when read by a host with the opposite byte order as the host that wrote the file, will have the value
0xd4c3b2a1. That allows software reading the file to determine whether the byte order of the host that wrote the file is the same as the
byte order of the host on which the file is being read, and thus whether the values in the per-file and per-packet headers need to be byte-
swapped.
Following this are:
A 2-byte file format major version number; the current version number is 2.
A 2-byte file format minor version number; the current version number is 4.
A 4-byte time zone offset; this is always 0.
A 4-byte number giving the accuracy of time stamps in the file; this is always 0.
A 4-byte number giving the "snapshot length" of the capture; packets longer than the snapshot length are truncated to the snapshot
length, so that, if the snapshot length is N, only the first N bytes of a packet longer than N bytes will be saved in the capture.
a 4-byte number giving the link-layer header type for packets in the capture; see pcap-linktype(7) for the LINKTYPE_ values that can
appear in this field.
Following the per-file header are zero or more packets; each packet begins with a per-packet header, which is immediately followed by the
raw packet data. The format of the per-packet header is:
+---------------------------------------+
| Time stamp, seconds value |
+---------------------------------------+
| Time stamp, microseconds value |
+---------------------------------------+
| Length of captured packet data |
+---------------------------------------+
|Un-truncated length of the packet data |
+---------------------------------------+
All fields in the per-packet header are in the byte order of the host writing the file. The per-packet header begins with a time stamp
giving the approximate time the packet was captured; the time stamp consists of a 4-byte value, giving the time in seconds since January 1,
1970, 00:00:00 UTC, followed by a 4-byte value, giving the time in microseconds since that second. Following that are a 4-byte value giv-
ing the number of bytes of captured data that follow the per-packet header and a 4-byte value giving the number of bytes that would have
been present had the packet not been truncated by the snapshot length. The two lengths will be equal if the number of bytes of packet data
are less than or equal to the snapshot length.
SEE ALSO pcap(3PCAP), pcap-linktype(7)
21 October 2008 PCAP-SAVEFILE(5)