10 More Discussions You Might Find Interesting
1. IP Networking
hi
From mt windows machine I can ping a LINUX machine but there is no arp entry for the same LINUX on my windows.
How is it possible and what can I do to add the arp entry as I need it.
thanks (1 Reply)
Discussion started by: leghorn
1 Replies
2. Solaris
What am I doing wrong, I configure interfaces ce1,ce,2 and ce3 but when I reboot the server they lose the configuration and I have to reset them?
ifconfig ce1 plumb
ifconfig ce2 plumb
ifconfig ce1 155.216.13.72 netmask 255.255.255.240
ifconfig ce2 155.216.13.73 netmask 255.255.255.240... (5 Replies)
Discussion started by: Kjons76
5 Replies
3. IP Networking
Hi,
I have a question on networking. I will try to ask with an example...
Suppose i am googling something, as in searching something in the google page. In this case what I basically want to know is, does the client do a connect evrytime to the server whenever a search is done in google,... (1 Reply)
Discussion started by: naan
1 Replies
4. UNIX for Advanced & Expert Users
hi everyone
this is dipendra, i am interested in networking,i know simple socket programming . and now i am wonder to get in to audio socket. i have no clue how to build audio socket.so i am looking if u can provide me a link regarding the audio socket building tutorials. (1 Reply)
Discussion started by: dipendra_regmi
1 Replies
5. Solaris
I can't or i don't know how to put up a network and internet on sun solaris 10. I looked and found some stuff on forums around net but I'm missing a few files. Like, "defaultrouter", "resolve.conf", ping is not working ( host unreachable), my card is "lo0" when I use ifconfig -a comand. Should I... (8 Replies)
Discussion started by: salvor_hardin
8 Replies
6. AIX
Please accept my apology ahead of time. Our AIX admin left the company unexpectedly and I am now left with trying to get a p570 w/5.3 setup. I had the help of an IBM reseller on setting up the LPARs, but need some quick questions answered.
1. I have 1 on-board NIC and 2 slot NICs. How do I... (2 Replies)
Discussion started by: LegendMan
2 Replies
7. IP Networking
HI guys/gals
basic question
lets say i am running a network. lets say i am using Win Me.
how would i network Win Me to a computer that has linux and another that has 98 well the 98 is no problem but the linux well i have an idea but i am rusty with linux. No i have rusted out. Would you make... (1 Reply)
Discussion started by: pydyer
1 Replies
8. UNIX for Dummies Questions & Answers
Hi new user to UNIX and I am in the process of networking my UNIX box to my windows2000....Is there a special program I have to install so that my windows would recognize and see the Unix box....any suggestions would be great
Thanks (1 Reply)
Discussion started by: jonas27
1 Replies
9. IP Networking
dear sir
how many name server can be configured in single machine?
thank you very much.
sandeep goel (3 Replies)
Discussion started by: ask_goel
3 Replies
10. IP Networking
In plain english what exactly is IP Networking?
Can someone take the time to explain? please! (3 Replies)
Discussion started by: kikkin
3 Replies
LEARN ABOUT OSF1
pcap-tstamp
PCAP-TSTAMP(7) Miscellaneous Information Manual PCAP-TSTAMP(7)
NAME
pcap-tstamp - packet time stamps in libpcap
DESCRIPTION
When capturing traffic, each packet is given a time stamp representing, for incoming packets, the arrival time of the packet and, for out-
going packets, the transmission time of the packet. This time is an approximation of the arrival or transmission time. If it is supplied
by the operating system running on the host on which the capture is being done, there are several reasons why it might not precisely repre-
sent the arrival or transmission time:
if the time stamp is applied to the packet when the networking stack receives the packet, the networking stack might not see the
packet until an interrupt is delivered for the packet or a timer event causes the networking device driver to poll for packets, and
the time stamp might not be applied until the packet has had some processing done by other code in the networking stack, so there
might be a significant delay between the time when the last bit of the packet is received by the capture device and when the net-
working stack time-stamps the packet;
the timer used to generate the time stamps might have low resolution, for example, it might be a timer updated once per host operat-
ing system timer tick, with the host operating system timer ticking once every few milliseconds;
a high-resolution timer might use a counter that runs at a rate dependent on the processor clock speed, and that clock speed might
be adjusted upwards or downwards over time and the timer might not be able to compensate for all those adjustments;
the host operating system's clock might be adjusted over time to match a time standard to which the host is being synchronized,
which might be done by temporarily slowing down or speeding up the clock or by making a single adjustment;
different CPU cores on a multi-core or multi-processor system might be running at different speeds, or might not have time counters
all synchronized, so packets time-stamped by different cores might not have consistent time stamps.
In addition, packets time-stamped by different cores might be time-stamped in one order and added to the queue of packets for libpcap to
read in another order, so time stamps might not be monotonically increasing.
Some capture devices on some platforms can provide time stamps for packets; those time stamps are usually high-resolution time stamps, and
are usually applied to the packet when the first or last bit of the packet arrives, and are thus more accurate than time stamps provided by
the host operating system. Those time stamps might not, however, be synchronized with the host operating system's clock, so that, for
example, the time stamp of a packet might not correspond to the time stamp of an event on the host triggered by the arrival of that packet.
Depending on the capture device and the software on the host, libpcap might allow different types of time stamp to be used. The
pcap_list_tstamp_types(3PCAP) routine provides, for a packet capture handle created by pcap_create(3PCAP) but not yet activated by
pcap_activate(3PCAP), a list of time stamp types supported by the capture device for that handle. The list might be empty, in which case
no choice of time stamp type is offered for that capture device. If the list is not empty, the pcap_set_tstamp_type(3PCAP) routine can be
used after a pcap_create() call and before a pcap_activate() call to specify the type of time stamp to be used on the device. The time
stamp types are listed here; the first value is the #define to use in code, the second value is the value returned by
pcap_tstamp_type_val_to_name() and accepted by pcap_tstamp_name_to_val().
PCAP_TSTAMP_HOST - host
Time stamp provided by the host on which the capture is being done. The precision of this time stamp is unspecified; it might or
might not be synchronized with the host operating system's clock.
PCAP_TSTAMP_HOST_LOWPREC - host_lowprec
Time stamp provided by the host on which the capture is being done. This is a low-precision time stamp, synchronized with the
host operating system's clock.
PCAP_TSTAMP_HOST_HIPREC - host_hiprec
Time stamp provided by the host on which the capture is being done. This is a high-precision time stamp; it might or might not
be synchronized with the host operating system's clock. It might be more expensive to fetch than PCAP_TSTAMP_HOST_LOWPREC.
PCAP_TSTAMP_ADAPTER - adapter
Time stamp provided by the network adapter on which the capture is being done. This is a high-precision time stamp, synchronized
with the host operating system's clock.
PCAP_TSTAMP_ADAPTER_UNSYNCED - adapter_unsynced
Time stamp provided by the network adapter on which the capture is being done. This is a high-precision time stamp; it is not
synchronized with the host operating system's clock.
SEE ALSO
pcap_set_tstamp_type(3PCAP), pcap_list_tstamp_types(3PCAP), pcap_tstamp_type_val_to_name(3PCAP), pcap_tstamp_name_to_val(3PCAP)
22 August 2010 PCAP-TSTAMP(7)