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)
Hi, I got the following question regarding tcpdump and I would appreciate your help/feedback:
--Scenario
I am instructed to capture the network traffic by getting the tcpdump data/files of our network for every hour.
--Problem
Some of the connections are still open when the capture is done... (1 Reply)
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)
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... (2 Replies)
Hi,
I want to capture TCPDUMP of traffic, I tried doing this but did not find success..can anyone plz correct it.
# tcpdump -s0 -vv -w /home/osuresh/test_tcp_dump host 10.12.10.22 && port 161
bash: tcpdump: command not found
# tcpdump -s0 -vv -w /home/osuresh/test_tcp_dump host... (5 Replies)
Hi Everyone,
anyone face "tcpdump -i any" does not work? i mean if i use -i eth0, can capture eth0, or use -i eth1 also can. but then tcpdump -i any, seems cannot capture packets. :confused:
please advice, thanks (2 Replies)
I'm new to the Unix/Linux world. I have taken classes and played with a few simple scripts but never had a real world application. Here is my problem.
What I need to do is every 15min between 8am and 5pm, run
tcpdump -s 2000 -w flowroute-0000.pcap
where the "0000" is the current time.
... (4 Replies)
I've recently started learning to use TCPdump, and I find it pretty interesting. There's one thing I don't understand. When I tell it to capture packets on, say, the WiFi interface en1, it often captures packets sent or received by other hosts on the network. How can it do this? My... (3 Replies)
Discussion started by: Ultrix
3 Replies
LEARN ABOUT NETBSD
ipresend
IPRESEND(1) General Commands Manual IPRESEND(1)NAME
ipresend - resend IP packets out to network
SYNOPSIS
ipresend [ -EHPRSTX ] [ -d <device> ] [ -g <gateway> ] [ -m <MTU> ] [ -r <filename> ]
DESCRIPTION
ipresend was designed to allow packets to be resent, once captured, back out onto the network for use in testing. ipresend supports a num-
ber of different file formats as input, including saved snoop/tcpdump binary data.
OPTIONS -d <interface>
Set the interface name to be the name supplied. This is useful with the -P, -S, -T and -E options, where it is not otherwise possi-
ble to associate a packet with an interface. Normal "text packets" can override this setting.
-g <gateway>
Specify the hostname of the gateway through which to route packets. This is required whenever the destination host isn't directly
attached to the same network as the host from which you're sending.
-m <MTU>
Specify the MTU to be used when sending out packets. This option allows you to set a fake MTU, allowing the simulation of network
interfaces with small MTU's without setting them so.
-r <filename>
Specify the filename from which to take input. Default is stdin.
-E The input file is to be text output from etherfind. The text formats which are currently supported are those which result from the
following etherfind option combinations:
etherfind -n
etherfind -n -t
-H The input file is to be hex digits, representing the binary makeup of the packet. No length correction is made, if an incorrect
length is put in the IP header.
-P The input file specified by -i is a binary file produced using libpcap (i.e., tcpdump version 3). Packets are read from this file
as being input (for rule purposes).
-R When sending packets out, send them out "raw" (the way they came in). The only real significance here is that it will expect the
link layer (i.e. ethernet) headers to be prepended to the IP packet being output.
-S The input file is to be in "snoop" format (see RFC 1761). Packets are read from this file and used as input from any interface.
This is perhaps the most useful input type, currently.
-T The input file is to be text output from tcpdump. The text formats which are currently supported are those which result from the
following tcpdump option combinations:
tcpdump -n
tcpdump -nq
tcpdump -nqt
tcpdump -nqtt
tcpdump -nqte
-X The input file is composed of text descriptions of IP packets.
SEE ALSO ipftest(1), ipsend(1), iptest(1), bpf(4), ipsend(5), tcpdump(8)DIAGNOSTICS
Needs to be run as root.
BUGS
Not all of the input formats are sufficiently capable of introducing a wide enough variety of packets for them to be all useful in testing.
If you find any, please send email to me at darrenr@pobox.com
IPRESEND(1)
05-06-2013
