[tcpdump-workers] is tcpdump supposed to behave like this?

2013-07-01 Thread Téssio Fechine
Hello, I was trying to analyze the traffic generated by this command: root@atena:~# dig rt-dq.quimica.ufpb.br @150.165.145.1 But I noticed that when the option '-w file' was not used, the tcpdump capture changed: ** WITH -w (2 packets captured): root@atena:~# tcpdump -pi eth0 port 53 -w dns.dum

Re: [tcpdump-workers] is tcpdump supposed to behave like this?

2013-07-01 Thread Michael Tuexen
On Jul 1, 2013, at 3:32 PM, Téssio Fechine wrote: > Hello, > I was trying to analyze the traffic generated by this command: > > root@atena:~# dig rt-dq.quimica.ufpb.br @150.165.145.1 > > But I noticed that when the option '-w file' was not used, the tcpdump > capture changed: > > ** WITH -w (

Re: [tcpdump-workers] is tcpdump supposed to behave like this?

2013-07-01 Thread Guy Harris
On Jul 1, 2013, at 6:32 AM, Téssio Fechine wrote: > Hello, > I was trying to analyze the traffic generated by this command: > > root@atena:~# dig rt-dq.quimica.ufpb.br @150.165.145.1 > > But I noticed that when the option '-w file' was not used, the tcpdump > capture changed: > > ** WITH -w

Re: [tcpdump-workers] is tcpdump supposed to behave like this?

2013-07-01 Thread Téssio Fechine
Thanks, everyone! I can see it clearly now.. 2013/7/1 Guy Harris > > On Jul 1, 2013, at 6:32 AM, Téssio Fechine wrote: > > > Hello, > > I was trying to analyze the traffic generated by this command: > > > > root@atena:~# dig rt-dq.quimica.ufpb.br @150.165.145.1 > > > > But I noticed that when