Login or Register to Ask a Question and Join Our Community


IP Networking

Detect Socket timeout in tcpdump capture

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums IP Networking Detect Socket timeout in tcpdump capture
# 1  
Old 07-20-2012
Detect Socket timeout in tcpdump capture
Hello,

I detect these errors in my logs :
Socket timeout calling url [http://server:port/bla/soap/selfcare/infoRapide]
Unable to make proxyRequest

I've made a tcpdump capture this way :

Code:
tcpdump -i eth0 -s 0 -w /app/captura.pcap port 8080

But I'm fairly new in reading .pcap files with wireshark... too much info for me. So I would like to know if you have some hints in what exactly should I look for in the capture to detect the errors I see in my logs "Socket timeout / Unable to make proxyRequest ".

Thanks
Last edited by Scott; 07-20-2012 at 05:55 AM.. Reason: Code tags
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. IP Networking

Clarification - Setting socket options at the same time when socket is listening

I need clarification on whether it is okay to set socket options on a listening socket simultaneously when it is being used in an accept() call? Following is the scenario:- -- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies

2. Red Hat

RHEL5.5 Socket Timeout Setting

Is there a Linux tunable to reduce the amount of time a socket waits before considering the remote side dead? Its the same senario when you try to telnet to a dead machine, telnet sits and waits for ~30seconds, before the socket timer expires and cancels the request. (5 Replies)
Discussion started by: mrmurdock
5 Replies

3. Programming

How detect TCP/IP socket shutdown when ethernet cable is disconnected

Hi, I want to code TCP/IP client/server in linux application capable to fastly detect ethernet cable disconnection in any condition. So I have activate SO_KEEPALIVE options and set TCP_KEEPCNT, TCP_KEEPIDLE and TCP_KEEPINTVL to 1. When I disconnect ethernet cable I have the following... (5 Replies)
Discussion started by: jeje_clb
5 Replies

4. IP Networking

Capture packets (TcpDump) and forwarding them

Hi, I want to capture a certain type of packets (selected according to the protocol) coming to my PC and then transmit them to another PC. I had the idea to use tcpdump to filter input packets and extract those chosen. Well my questions are: 1- after filtering input packets, those that have not... (1 Reply)
Discussion started by: ziedf
1 Replies

5. Programming

Error with socket operation on non-socket

Dear Experts, i am compiling my code in suse 4.1 which is compiling fine, but at runtime it is showing me for socket programming error no 88 as i searched in errno.h it is telling me socket operation on non socket, what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies

6. Programming

socket function to read a webpage (socket.h)

Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct... #include <stdio.h> #include <stdlib.h> #include <sys/types.h> #include <sys/stat.h> #include <string.h> #include... (3 Replies)
Discussion started by: cyler
3 Replies

7. Programming

which socket should socket option on be set

Hi all, On the server side, one socket is used for listening, the others are used for communicating with the client. My question is: if i want to set option for socket, which socket should be set on? If either can be set, what's the different? Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies

8. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

9. Cybersecurity

i would like to know about tcpdump

i would like to know about tcpdump i would like to use tcpdump to get information about these - Date - time - source hostname - source mac address - source ip address - destination ip address - see outbound only then i use command like this tcpdump -i le0 -n -q -tttt -e src net... (0 Replies)
Discussion started by: chamnanpol
0 Replies

10. Programming

How To Use tcpdump

I have two net-card. one is 172.16.24.99(ENG) ,another is 172.16.25.99(ENG-B). Both masks is 255.255.255.0. I will monitor data on the tcp port 8055 in ENG, How do I set option of tcpdump command (2 Replies)
Discussion started by: chenhao_no1
2 Replies
Login or Register to Ask a Question

LEARN ABOUT SUSE

capinfos

CAPINFOS(1)						  The Wireshark Network Analyzer					       CAPINFOS(1)

NAME

       capinfos - Prints information about capture files

SYNOPSIS

       capinfos [ -t ] [ -E ] [ -c ] [ -s ] [ -d ] [ -u ] [ -a ] [ -e ] [ -y ] [ -i ] [ -z ] [ -x ] [ -h ] <infile> ...

DESCRIPTION

       Capinfos is a program that reads one or more capture files and returns some or all available statistics of each <infile>.

       The user specifies which statistics to report by specifying flags corresponding to the statistic.  If no flags are specified, Capinfos will
       report all statistics available.

       Capinfos is able to detect and read the same capture files that are supported by Wireshark.  The input files don't need a specific filename
       extension; the file format and an optional gzip compression will be automatically detected.  Near the beginning of the DESCRIPTION section
       of wireshark(1) or http://www.wireshark.org/docs/man-pages/wireshark.html <http://www.wireshark.org/docs/man-pages/wireshark.html> is a
       detailed description of the way Wireshark handles this, which is the same way Capinfos handles this.

OPTIONS

       -t  Displays the capture type of the capture file.

       -E  Displays the per-file encapsulation of the capture file.

       -c  Counts the number of packets in the capture file.

       -s  Displays the size of the file, in bytes.  This reports the size of the capture file itself.

       -d  Displays the total length of all packets in the file, in bytes.  This counts the size of the packets as they appeared in their original
	   form, not as they appear in this file.  For example, if a packet was originally 1514 bytes and only 256 of those bytes were saved to
	   the capture file (if packets were captured with a snaplen or other slicing option), Capinfos will consider the packet to have been 1514
	   bytes.

       -u  Displays the capture duration, in seconds.  This is the difference in time between the earliest packet seen and latest packet seen.

       -a  Displays the start time of the capture.  Capinfos considers the earliest timestamp seen to be the start time, so the first packet in
	   the capture is not necessarily the earliest - if packets exist "out-of-order", time-wise, in the capture, Capinfos detects this.

       -e  Displays the end time of the capture.  Capinfos considers the latest timestamp seen to be the end time, so the last packet in the
	   capture is not necessarily the latest - if packets exist "out-of-order", time-wise, in the capture, Capinfos detects this.

       -y  Displays the average data rate, in bytes/sec

       -i  Displays the average data rate, in bits/sec

       -z  displays the average packet size, in bytes

       -x  displays the average packet rate, in packets/sec

       -h  Prints the help listing and exits.

SEE ALSO

       tcpdump(8), pcap(3), wireshark(1), mergecap(1), editcap(1), tshark(1), dumpcap(1)

NOTES

       Capinfos is part of the Wireshark distribution.	The latest version of Wireshark can be found at <http://www.wireshark.org>.

       HTML versions of the Wireshark project man pages are available at: http://www.wireshark.org/docs/man-pages
       <http://www.wireshark.org/docs/man-pages>.

AUTHORS

	 Original Author
	 -------- ------
	 Ian Schorr	      <ian[AT]ianschorr.com>

	 Contributors
	 ------------
	 Gerald Combs	      <gerald[AT]wireshark.org>

1.2.8								    2010-05-05							       CAPINFOS(1)