From: "Dharmendra.T" <dharmu@nsecure.net>
To: mdew <mdew@mdew.dyndns.org>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: RE: opening a port..
Date: 09 Jan 2003 11:56:53 +0530 [thread overview]
Message-ID: <1042093627.810.17.camel@india> (raw)
In-Reply-To: <1042092980.487.4.camel@nirvana>
On Thu, 2003-01-09 at 11:46, mdew wrote:
> On Thu, 2003-01-09 at 17:55, Dharmendra.T wrote:
> > On Thu, 2003-01-09 at 08:11, mdew wrote:
> > > On Thu, 2003-01-09 at 03:24, Rob Sterenborg wrote:
> > > > > ok, telnet from another machine to the router.
> > > > >
> > > > > telnet 10.0.0.6 4662
> > > > > Trying 10.0.0.6...
> > > > > telnet: Unable to connect to remote host: Connection refused
> > > > >
> > > > > what "service" should I be running? I simply want 4662 open both ways.
> > > >
> > > > # netstat -an|grep 4662
> > > > should tell you if your box is listening at all on port 4662.
> > > >
> > > > If you run eDonkey server on the firewall box, open port in the INPUT
> > > > chain.
> > > > If your eDonkey server is *behind* the firewall, open the port in the
> > > > FORWARD chain, and add a DNAT rule in the nat table -> PREROUTING chain.
> > >
> > > the edonkey server is behind the firewall
> > >
> > > 210.54.175.12--->eth0 (Router) 10.0.0.6(eth1)--->10.0.0.x
> > >
> > > iptables -t nat -A PREROUTING -p tcp -i eth0 -d 210.54.175.12 --dport 4662 -j DNAT --to 10.0.0.6:4662
> > >
> >
> > This should work without the last rule.
> >
> > iptables -A FORWARD -p tcp -i eth0 -d 10.0.0.6 --dport 4662 -j ACCEPT
> > >
> > > like that?
>
> the router isnt picking this up..
>
> mdew:~# iptables -t nat -A PREROUTING -p tcp -i eth0 -d 210.54.175.12
> --dport 4662 -j DNAT --to 10.0.0.6:4662
> mdew:~# iptables -A FORWARD -p tcp -i eth0 -d 10.0.0.6 --dport 4662 -j
> ACCEPT
> mdew:~# netstat -an|grep 4662
> mdew:~#
>
> mdew@nirvana:~$ nmap 10.0.0.6
>
> Starting nmap V. 3.10ALPHA4 ( www.insecure.org/nmap/ )
> Interesting ports on debian (10.0.0.6):
> (The 1598 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
> 113/tcp open auth
> 135/tcp filtered loc-srv
> 139/tcp filtered netbios-ssn
> 8080/tcp open http-proxy
>
> Nmap run completed -- 1 IP address (1 host up) scanned in 2.545 seconds
> >
>
As said you are not running any service on that port so the port is not
listening, Try the rules by listening a port using nc(netcat)
# nc -l -p 4662
And then run nmap. You should get listed this port!
--
Dharmendra.T
Linux Enthu
next prev parent reply other threads:[~2003-01-09 6:26 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 [this message]
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
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=1042093627.810.17.camel@india \
--to=dharmu@nsecure.net \
--cc=mdew@mdew.dyndns.org \
--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