On 10 Aug 2000, Robert Soros wrote:
> > netstat -avnp | grep 3520
>
> but next time it *Probably* wont be on that port, how about grepping for
> 443 instead (thats a pretty good number to use since it will never be
> part of any IP address)
Sure, that'll work. It _might_ return too many lines,
> On Tue, 8 Aug 2000, Wayne Dyer wrote:
>
> > my_machine.org for my machine's name. The traffic is NOT coming from my
> > internal network. Where can I find a listing of the flags FP and R?
> > Any ideas as to what's happening here?
> >
> > 08:21:38.088650 < 10.1.12.50.https > my_machine.org.3
> I noticed some traffic to my system (home system) and captured some with
> tcpdump. This was a quick grab, so I didn't think to do anything other
> than `tcpdump -i eth1`. In the listing below, I've substituted
> my_machine.org for my machine's name. The traffic is NOT coming from my
> intern
Gordon Messmer wrote:
> On Tue, 8 Aug 2000, Wayne Dyer wrote:
>
> > my_machine.org for my machine's name. The traffic is NOT coming from my
> > internal network. Where can I find a listing of the flags FP and R?
> > Any ideas as to what's happening here?
> >
> > 08:21:38.088650 < 10.1.12.50.ht
On Tue, 8 Aug 2000, Wayne Dyer wrote:
> my_machine.org for my machine's name. The traffic is NOT coming from my
> internal network. Where can I find a listing of the flags FP and R?
> Any ideas as to what's happening here?
>
> 08:21:38.088650 < 10.1.12.50.https > my_machine.org.3520: FP 119660
I noticed some traffic to my system (home system) and captured some with
tcpdump. This was a quick grab, so I didn't think to do anything other
than `tcpdump -i eth1`. In the listing below, I've substituted
my_machine.org for my machine's name. The traffic is NOT coming from my
internal network
