[tcpdump-workers] measure upload and download traffic ratio to specific port using tcpdump

2011-11-27 Thread Martin T
I would like to measure ratio between download traffic and upload traffic when using Windows Terminal Server(RDP; TCP port 3389). I would use iptraf, but there are other connections over this interface and I'm not able to disconnect this. Is it possible to measure bandwidth usage with tcpdump? I tr

Re: [tcpdump-workers] measure upload and download traffic ratio to specific port using tcpdump

2011-11-27 Thread Martin T
affic is smaller because only keyboard input, cursor coordinates etc is uploaded to server.. regards, martin 2011/10/27 Martin T : > I would like to measure ratio between download traffic and upload > traffic when using Windows Terminal Server(RDP; TCP port 3389). I > would use iptraf

[tcpdump-workers] odd behavior of telnet server

2011-10-05 Thread Martin T
Hello, I have a radio device which supports management over telnet. However, it supports only one telnet session at a time. If I do "hping -S -p 23 -i 5 -I fxp0 10.10.10.1"(send TCP SYN packet to port 23 of 10.10.10.1 after every 5 seconds over interface fxp0) I get following tcpdump output: 17:08

[tcpdump-workers] capture certain bit in ICMP package

2011-08-21 Thread Martin T
I would like to capture only the value of 108'th and 110'th bit in ICMP echo request packet. Those bits should reside in ICMP payload area. Is there a possibility in tcpdump to capture only specific bit? Or at least show the "tcpdump -i eth0 -n -X" output in binary instead of hexadecimal? - This is

Re: [tcpdump-workers] hardware loop and frame length increase

2011-06-09 Thread Martin T
Fulko, Guy thanks for explaining this! regards, martin 2011/6/7 Guy Harris : > > On Jun 6, 2011, at 3:02 PM, Martin T wrote: > >> As you can see, every second I sent and received one frame. The >> question is, why is the frame, which I receive, 18 bytes longer than >

[tcpdump-workers] hardware loop and frame length increase

2011-06-06 Thread Martin T
I made a RJ45 hardware loopback connector(connected Tx- with Rx+ and Tx+ with Rx-), connected this to my eth2 port, configured 192.168.88.0/24 to eth2 and executed: "ping -i0.1 -c3 192.168.88.88" ..while running tcpdump like this: root@martin-desktop:~# tcpdump -n -i eth2 -e -v -XX tcpdump: list