Re: Why can I telnet my port 21
From: Johan Lindquist (spam_at_smilfinken.net)
Date: 03/26/04
- Previous message: Tim Haynes: "Re: Why can I telnet my port 21"
- In reply to: Tim Haynes: "Re: Why can I telnet my port 21"
- Next in thread: Tim Haynes: "Re: Why can I telnet my port 21"
- Reply: Tim Haynes: "Re: Why can I telnet my port 21"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 26 Mar 2004 00:23:05 +0100
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?
Especially if you like to call it speedy. :)
-- Time flies like an arrow, fruit flies like a banana. Perth ---> * 00:20:44 up 33 days, 6:58, 3 users, load average: 3.41, 3.23, 2.85 $ cat /dev/bollocks Registered Linux user #261729 incentivize transparent e-tailers
- Previous message: Tim Haynes: "Re: Why can I telnet my port 21"
- In reply to: Tim Haynes: "Re: Why can I telnet my port 21"
- Next in thread: Tim Haynes: "Re: Why can I telnet my port 21"
- Reply: Tim Haynes: "Re: Why can I telnet my port 21"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|