> >> this won't work with icmp though...
> >
> > That's fine, I'm only interested in IP traffic.
>
> Presumably you mean "IP traffic other than ICMP traffic", as ICMP
> traffic *is* IP traffic.
Right, of course it is. Thanks for catching that :)
Just as a shot in the dark, changed '-ln ip' to
-BEGIN PGP SIGNED MESSAGE-
> "Paul" == Paul Berube <[EMAIL PROTECTED]> writes:
Paul> Ok. I have a couple traces in tcpdump format. What I
Paul> actually need is just a list of destination addresses for the
Paul> trace. I might be able to use a timestamp if I got really
On Sep 17, 2004, at 3:20 PM, Paul Berube wrote:
One question, though. I see "h.m.s:ms, a.b.c.d.x:", and I'm wondering
what the 'x' is? By the frequent occurences of 80, I'm guessing these
are
port numbers, but I'd like to be sure :)
Yes.
this won't work with icmp though...
That's fine, I'm only
> i think this will accomplish what you want:
> # tcpdump -ln ip| awk '{print $1,",", $5}' | sed 's/\.[0-9]*:$//'
The output looks fantastic, nearly exactly the format I wanted!
One question, though. I see "h.m.s:ms, a.b.c.d.x:", and I'm wondering
what the 'x' is? By the frequent occurences o
Hi Paul,
i think this will accomplish what you want:
# tcpdump -ln ip| awk '{print $1,",", $5}' | sed 's/\.[0-9]*:$//'
this won't work with icmp though...
-alexm
16:11 17/09/2004
On Fri, 17 Sep 2004, Paul Berube wrote:
>
> Hi.
>
> I think I have a simple problem, but I can't seem to find a si
On Sep 17, 2004, at 12:55 PM, Paul Berube wrote:
Ok. I have a couple traces in tcpdump format. What I actually need is
just a list of destination addresses for the trace. I might be able to
use a timestamp if I got really fancy, but it's not required. So,
precisely, for each packet in the trace,
Hi.
I think I have a simple problem, but I can't seem to find a simple
solution... First, let me say that I know very little in the networks
field, that I'm working under Cygwin and Linux, and that I don't have root
access.
Ok. I have a couple traces in tcpdump format. What I actually need
