Sponsored Content
Top Forums Shell Programming and Scripting How to demonstrate network problems? Post 302493960 by jim mcnamara on Friday 4th of February 2011 10:22:35 AM
Old 02-04-2011
First read up on snoop. You can capture and analyze packets, then run reports against those packets when you have a problem for network verification. The main downside to this strategy is disk usage. Not performance. You point of interest is to be able to realte the send time of a packet from your app to the time it takes for the expected return packet to appear. This is not the same thing as ping return times.

You can also use netstat -i to gather information on packet collisions. When collisions rise to a significant level trafic is impeded to large degree.

However, most network problem I have seen are the result of crappy application code.
Once a network is set up correctly, and is not subject to huge torrents of random data, you do not see problems except for hardware issues or intrusions.

A common application fault is not implementing a circular buffer (queue) large enough to deal with full bore traffic. In other words the network outruns the application between two apps: one slower, one faster.
 

9 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

Windows xp network problems

Hello guys , i have a big big problem. At the company that i work for there are like 4 pcs that are sending and recieving a lot of packets to the point that the network is down. we think that it might be a virus, we run all the antivirus that you could posible think of and nothing so far. ... (2 Replies)
Discussion started by: josramon
2 Replies

2. SuSE

Linux Network problems-Please help

Hullo everyone, I have recently installed SUSE 9.1 and attached it to my Network router (Actiontec 54Mbps Wireless DSL Gateway) but can't connect to the internet. It comes up with the following error message: An error occurred while loading "http://www.yahoo.com":Timeout on server - connection... (2 Replies)
Discussion started by: sybella1
2 Replies

3. Slackware

Network Startup Problems

I recently installed slackware 11 and have been very happy with it until I found out that some gnome related apps can cause gnome's network manager to alter the rc.init1 script by adding 3 lines to the script containing only the command, eth_up. This causes the script not to run properly and not... (1 Reply)
Discussion started by: djtrippin
1 Replies

4. Solaris

Problems with SS5 Network

Hey. i have a SPARCstation 5 running solaris 8 and CDE, i know this hardware is really old but its the only Solaris machine i can afford at this time, (Student) but im having a hard time getting it on the internet, im using a cable modem, andt DHCP IPv4, but i can`t get a connection, i have heard... (0 Replies)
Discussion started by: mads-nielsen
0 Replies

5. Solaris

Network Install Problems T2000

Hi I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1). But when I try to install using # boot net -s I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies

6. Solaris

Troubleshooting Solairs 10 Network problems

recently I've setup a Solaris 10 box & am having network disruption, e.g. disconnects, interrupted pings, etc) when I connect to it from another machine, how should I troubleshoot this ! The machine is a x86 box with 3 NICs (Differnet providors). The Current NIC is a Intel Gigabit, which is... (4 Replies)
Discussion started by: stevie_velvet
4 Replies

7. SCO

network problems with sco

SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that. thanks (8 Replies)
Discussion started by: ajantha
8 Replies

8. SCO

Problems with network card in SCO

hello, i am new to unix and need support</SPAN></SPAN> </SPAN></SPAN>The problem is: I have a SCO 5.0.5 server, and has no local network access, I think my problem are the drivers for network card. my network card is Kingston EtheRx PCI Fast Ethernet Adapter KNE120TX and already installed the... (9 Replies)
Discussion started by: daniel_cie
9 Replies

9. UNIX for Advanced & Expert Users

Vmware 7 unixware 7.13 network problems

i need help, i will always accord mine if my scope allows me, help me in this one.. am running vmware 7.0 in winserver 2008 on a cq61-425el, my network driver is installed correctly. and my vmware network drivers have added as well (in the device manager section). During installation i wasnt... (0 Replies)
Discussion started by: baitz
0 Replies
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)
All times are GMT -4. The time now is 11:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy