Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Jörg Esser" <jackfritt@boh.de>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: opening a port..
Date: Thu, 09 Jan 2003 09:04:33 +0100	[thread overview]
Message-ID: <3E1D2D11.50302@boh.de> (raw)
In-Reply-To: <1042095879.433.17.camel@nirvana>



mdew wrote:

>On Thu, 2003-01-09 at 19:53, Dharmendra.T wrote:
>  
>
>>>># nc -l -p 4662
>>>>
>>>>And then run nmap. You should get listed this port!
>>>>
>>>>-- 
>>>>Dharmendra.T
>>>>Linux Enthu
>>>>        
>>>>
>>>mdew:~# nc -l -p 4662
>>>ãP<H¹ogÝT'b´\Y6▒http://emule-project.net<6Ñ~ÖEmdew:~#
>>>
>>>(some strange characters, then it quits)
>>>
>>>mdew:~# netstat -an|grep 4662
>>>mdew:~#
>>>
>>>nirvana:/home/mdew# nmap 10.0.0.6
>>>      
>>>
nmap -p4662 10.0.0.6
Should work better.
and a new version of nmap should work better, too.
I heard that when you use nmap as your way it picks just well known 
ports (/etc/service file ?) and then you won´t get this special port if 
its not in there.(Maybe I´m wrong)

>>>Starting nmap V. 3.10ALPHA4 ( www.insecure.org/nmap/ )
>>>Interesting ports on debian (10.0.0.6):
>>>(The 1591 ports scanned but not shown below are in state: closed)
>>>Port       State       Service
>>>22/tcp     open        ssh
>>>25/tcp     open        smtp
>>>110/tcp    open        pop-3
>>>111/tcp    filtered    sunrpc
>>>113/tcp    open        auth
>>>135/tcp    filtered    loc-srv
>>>136/tcp    filtered    profile
>>>137/tcp    filtered    netbios-ns
>>>138/tcp    filtered    netbios-dgm
>>>139/tcp    filtered    netbios-ssn
>>>199/tcp    filtered    smux
>>>826/tcp    filtered    unknown
>>>953/tcp    filtered    rndc
>>>8080/tcp   open        http-proxy
>>>
>>>
>>>
>>>
>>>      
>>>
>>nc, I mean to say netcat.?
>>    
>>
>
>it was netcat
>
>apt-get install netcat
>
>
>
>
>  
>



  reply	other threads:[~2003-01-09  8:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 12:12 opening a port mdew
2003-01-08 12:33 ` Dharmendra.T
2003-01-08 12:52   ` mdew
2003-01-08 14:24     ` Rob Sterenborg
2003-01-09  1:58       ` mdew
2003-01-09  2:41       ` mdew
2003-01-09  4:55         ` Dharmendra.T
2003-01-09  6:16           ` mdew
2003-01-09  6:26             ` Dharmendra.T
2003-01-09  6:45               ` mdew
2003-01-09  6:53                 ` Dharmendra.T
2003-01-09  7:04                   ` mdew
2003-01-09  8:04                     ` Jörg Esser [this message]
2003-01-09  8:36                       ` mdew
2003-01-09  8:11                     ` Dharmendra.T
2003-01-09  8:24                       ` mdew
2003-01-09 20:38                         ` Athan
2003-01-09  8:21         ` Rob Sterenborg
2003-01-09  9:51           ` mdew
2003-01-09 10:35             ` Rob Sterenborg
2003-01-08 14:40     ` Rodrigo Hidalgo
2003-01-09  4:10     ` Dharmendra.T
2003-01-08 13:02   ` Robert Botha
2003-01-08 12:53 ` mdew
2003-01-08 13:54   ` Raymond Leach
     [not found] <FD8F124A387AD6119F7900A0D218B321561E53@hslex01.hslbz.local>
2003-01-09 10:40 ` Rob Sterenborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E1D2D11.50302@boh.de \
    --to=jackfritt@boh.de \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox