10 More Discussions You Might Find Interesting
1. IP Networking
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
2. Debian
Hi.
Need Help with TcpDump
Trying to sniff associatio-request with tcpdump but when i run this tcpdump -i eth0 wlan subtype assoc-req i get this error
can anyone help me with this error ? Thanks alot !!:) (1 Reply)
Discussion started by: SoulZB
1 Replies
3. IP Networking
Hi,
I am trying to capture manually crafted IP packets, created using Scapy, to a pcap file that can later be replayed using tcpreplay.
When using wireshark, I can successfully capture these packets and view them in wireshark.
However, when using tcpdump, these packets are then shown in... (2 Replies)
Discussion started by: yotamhc
2 Replies
4. Shell Programming and Scripting
i am trying to write a script to parse some tcpdump output, in each line of the tcpdump output, I know for sure there are 3 keywords exist:
User{different usernamehere}
NAS_ipaddr{different ip here}
Calling_station{ip or dns name here}
But the positions for these 3 keywords in the... (4 Replies)
Discussion started by: fedora
4 Replies
5. IP Networking
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)
Discussion started by: chamnanpol
2 Replies
6. Cybersecurity
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
7. Shell Programming and Scripting
hello, i have a lot of pcap files (tcpdump output) that i want to compare.
every tcpdump output has two file, server and client.
what i want to do is:
1. take timestamp, source address, destination address, and packet id from each file (server and client)
2. find the packets sent from... (0 Replies)
Discussion started by: slumpia
0 Replies
8. Shell Programming and Scripting
I wrote a short BASH script to run tcpdump and save the output to a log file for when I'm away from my desk. The script runs fine normally, but fails to start in cron. Any ideas?
#!/bin/bash
today=`date +%Y%m%d`
tcpdump -i eth0 -s 1500 -w ${today}.cap &
exit (5 Replies)
Discussion started by: paulzeromi
5 Replies
9. UNIX for Dummies Questions & Answers
does anybody know what the -d -dd and -ddd options are used for ?
thanks (2 Replies)
Discussion started by: ant04
2 Replies
10. Programming
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
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)
