Sponsored Content
Full Discussion: Seeing IP packet
Special Forums IP Networking Seeing IP packet Post 27613 by binhnx2000 on Wednesday 4th of September 2002 10:35:13 AM
Old 09-04-2002
Hammer & Screwdriver

In Unix/Linux...You can use: tcpdump, ethereal, iptraf...

tcpdump: default was install with any version UnixSmilie
 

10 More Discussions You Might Find Interesting

1. IP Networking

packet loss problem

I have 4 network ports on our T5240 sun server. all but 1 gives packet losses (nxge1) nxge0 gives on average 50% packet loss, very bad. nxge2 gives on average 1-2% packet loss. nxge3 gives on average 20% packet loss. Is there a tool or something to help me find the problem? (11 Replies)
Discussion started by: photon
11 Replies

2. Programming

Packet capturing using pcap

Hi, i am using a linux CentOS machine. I have 2 real network interfaces eth0, eth1 and 2 virtual interfaces tap0 and tap1. I am using PCAP library to capture the packets on theses interfaces. If i specify the interface as "any", i cannot find a way to know from which interface the packet... (1 Reply)
Discussion started by: rahulnitk2004
1 Replies

3. IP Networking

Packet parsing and modification

Hi All, I need your help regarding packet capturing and modification. Like we may add extra content into the original html content. Any open source tools.. programs...etc.. Do share your views and ideas. -Vivek (1 Reply)
Discussion started by: viveksnv
1 Replies

4. Programming

Writing a Packet sniffer

Hi, I want to write a packet sniffer in C without using libpcap. Can anyone suggest me how to begin writing it? Any tutorials or books? Thanks in advance! (2 Replies)
Discussion started by: nefarious_genus
2 Replies

5. Programming

packet capture

can anyone tell me how can i capture the packets. i have tried ethernet software to capture them but its not doing what i want it to do it (1 Reply)
Discussion started by: dazdseg
1 Replies

6. IP Networking

Packet decoding

Hi, wondering if anyone can suggest a tool to me that will let me either cut & paste hex or type it in for packet decoding. I want to be able to decode a packet as done with tcpdump or wireshark, but I want to be able to manually input the hex myself. (2 Replies)
Discussion started by: Breakology
2 Replies

7. Cybersecurity

filter packet

Exercise: Protection of WEB and DNS servers using the context-free rules for packet filtering: - Protect your WEB-server, so that would be for him can be accessed by browsers, and could go to dns. - Protect your primary DNS-server so that it could be to contact clients and secondary servers.... (1 Reply)
Discussion started by: numeracy
1 Replies

8. Homework & Coursework Questions

filter packet

Exercise: Protection of WEB and DNS servers using the context-free rules for packet filtering: - Protect your WEB-server, so that would be for him can be accessed by browsers, and could go to dns. - Protect your primary DNS-server so that it could be to contact clients and secondary servers.... (1 Reply)
Discussion started by: numeracy
1 Replies

9. AIX

Packet loss coming with big packet size ping

(5 Replies)
Discussion started by: Vishal_dba
5 Replies

10. Solaris

WakeOnLan, tcp packet

I'd like to use SPARC Solaris10 to 'wake up' an old PC on same LAN. what is the simplest way of doing it? (preferably without installing new software) thanks. (14 Replies)
Discussion started by: orange47
14 Replies
nstreams(1)							   Users Manuals						       nstreams(1)

NAME
network streams - a tcpdump output analyzer SYNOPSIS
nstreams [ -v ] [ -c nstreams-services ] [ -n nstreams-networks_file ] [ -N [ -i ] [ -I ]] [ -r ] [ -O output [ -D iface ] [ -Y ]] [ -u ] [ -U ] [ -B ] [ -f tcpdump_file ] [ -l <iface> ] [ tcpdump output ] DESCRIPTION
nstreams is a utility designed to identify the IP streams that are occuring on a network from a non-user friendly tcpdump output of several megabytes. This is especially useful when you plan to install a firewall but if you do not know the nstreams that the network users are generating (http, real audio, and more...). nstreams can read the tcpdump output directly from stdin, or from a file. It can even generate the con- figuration file of your firewall, using the -O option. OPTIONS
-c <nstreams-services-file> The path to an alternate nstreams service file. This file is used to identify each protocol. See the services file section later in this manual page. -n <nstreams-networks-file> The path to an alternate nstreams network file. This file is used to identify which hosts belong to which network. See the networks file section later in this manual page. -f <tcpdump output file> The path to the file to read data from. This file must have been generated using 'tcpdump -w filename'. -l <iface> Listen directly on interface <iface>. This avoids the use of tcpdump. -N print the networks names instead of the hosts IP addresses. The intra-network traffic will not be shown. Use this option twice to show the networks IP address instead of their names. -i Also show the intra-network traffic (must be used with -N) -I Only show the intra-network traffic (must be used with -N) -r be redundant. That is, the same streams will be printed each time they appear in the dump. -v print version number and exit. -O <type> output type. You can use this option to generate your firewall startup script. Do nstreams -h to see the supported output types. -D <iface> interface to apply to output onto. Must be used with -O. -Y The firewall rules that will be generated will deny all packets coming from the outside trying to establish connections to the inside. If you system is not serving anything, then it's safe to turn on this option. -u Do not print the unknown streams -U Only print the unknown streams -B Show broadcasts and networks USAGE
Let tcpdump(1) run some time on your network (like one week), and save its output in a file, by doing : tcpdump -l -n > output or tcpdump -w filename Then, feed nstreams with this output file, and it will turn it into a easily-readable file which will help you to write efficient firewall filters. You may also do : tcpdump -l -n | nstreams or nstreams -f filename (if you used tcpdump -w) THE SERVICES FILE
The service file contains the description of each protocol, as well as their name. Its syntax is : protocol_name:server_port(s)/{udp,tcp}:client_ports(s) or : protocol_name:type(s)/icmp:code(s) Whereas : protocol_name is the name of the protocol described. This name may contain any character, including space, except ':'. server_port(s) is the range of ports used by the server. Usually, you will want to define one server port only, but you may enter any range you want. ip_protocol is the IP protocol that this protocol is lying onto. Acceptable values are tcp and udp client_port(s) is the range of ports that the client may use. You can set this to any or, for more accurate results, to ports ranges, like '1-1024,2048-4096'. The rules are : 'first match, first taken'. SERVICE FILE EXAMPLE
Using this syntax, you would declare the ssh protocol by : ssh-unix:22/tcp:1000-1023 Because the Unix version of the ssh client uses a privileged port to connect onto the ssh server which listens on port 22. THE NETWORKS FILE
The networks file is used to define sets and subsets of hosts (also known as networks). This avoids redundancy in the output file. The syn- tax format for this file is : network name:ip/mask Whereas the network name is whatever you want, the IP is the ip of the network, and the mask is the CIDR netmask of the network. The rule is 'first match, first taken'. NETWORKS FILE EXAMPLE
admin:192.168.19.0/29 whole_subnet:192.168.0.0/16 internet:0.0.0.0/0 LIMITS
o nstreams can only parse the output of 'tcpdump -n' o Even though the output of nstreams is easier to read than the one of tcpdump, it is still not easily readable. Use sort(1) on the nstream output to get a more readable file. o This program could have been written in perl FILES
/etc/nstreams-services /etc/nstreams-networks SEE ALSO
tcpdump(1) AUTHORS
Concept : Herve Schauer Consultants - http://www.hsc.fr Coding : Renaud Deraison <deraison@cvs.nessus.org> BUG REPORTS
Please send all your bug reports with the detail of your configuration to Renaud Deraison <deraison@cvs.nessus.org> nstreams July 1999 nstreams(1)
All times are GMT -4. The time now is 01:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy