Re: Why can I telnet my port 21
From: Tim Haynes (usenet-20040325_at_stirfried.vegetable.org.uk)
Date: 03/26/04
- Next message: Johan Lindquist: "Re: Why can I telnet my port 21"
- Previous message: Johan Lindquist: "Re: Why can I telnet my port 21"
- In reply to: Johan Lindquist: "Re: Why can I telnet my port 21"
- Next in thread: Johan Lindquist: "Re: Why can I telnet my port 21"
- Reply: Johan Lindquist: "Re: Why can I telnet my port 21"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 25 Mar 2004 23:45:27 +0000
Johan Lindquist <spam@smilfinken.net> writes:
> So anyway, it was like, 21:41 CET Mar 25 2004, you know? Oh, and, yeah,
> Tim Haynes was all like, "Dude,
>> Colin McKinnon <colin.thisisnotmysurname@ntlworld.deletemeunlessURaBot.com> writes:
>
>>> What does netstat -ap say?
>>
>> Speedier version: `netstat -plant | grep LISTEN'. Tcp is all that's
>> interesting here and we don't need names for things.
>
> I've just gotta ask (because I might be missing some Clue or other here),
> what's the reason for specifying both -l (listening) and -a (all) and
> then grepping for the listening ports?
IME -l doesn't seem to work, hence the greppery afterwards. The `-an' is
finger-memory from even longer back than:
> Especially if you like to call it speedy. :)
It falls off the fingers easily. I spent too long digging through TFM one
day, saw `-l', thought `hmm, let's try that'... and it stuck ;8)
~Tim
-- The night skips the sleeping years |piglet@stirfried.vegetable.org.uk And re-awakes the memory |http://spodzone.org.uk/cesspit/
- Next message: Johan Lindquist: "Re: Why can I telnet my port 21"
- Previous message: Johan Lindquist: "Re: Why can I telnet my port 21"
- In reply to: Johan Lindquist: "Re: Why can I telnet my port 21"
- Next in thread: Johan Lindquist: "Re: Why can I telnet my port 21"
- Reply: Johan Lindquist: "Re: Why can I telnet my port 21"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]