Re: Telnet is not working with iptables

Salam n thnx Ahmed,
 
what I did... I enabled SSH port by using
 
system-config-securitylevel tool
 
and I also added my desired port
 
now I can telnet and ssh also
 
Best Regards,

Shariq Siddiqui
Advanced Operations Technology
PO.Box : 25904 - Riyadh 11476
Riyadh Saudi Arabia
Tel : +966 1 291 0605 -
Fax:+966 1 291 3328

 
 

--- On Tue, 9/29/09, Ahmed Sharif <ahmed.sharif.bd@xxxxxxxxx> wrote:


From: Ahmed Sharif <ahmed.sharif.bd@xxxxxxxxx>
Subject: Re: Telnet is not working with iptables
To: "General Red Hat Linux discussion list" <redhat-list@xxxxxxxxxx>
Date: Tuesday, September 29, 2009, 5:44 AM


Hello Siddiqui,

You are appending to the existing rules (option -A). There may be other rule
above your rule that is causing denial of the the specific port. Check the
rule list with iptables -nL command. You can also try inserting the rule
instead of appending (-I option). Another thing to try is, while trying to
do telnet on that specific port run iptables -nVL command at the destination
and observing the packet count increament you will understand what rule is
causing the problem.


Thanks and Regards,

Ahmed Sharif
Warid Telecom International Ltd
Bangladesh

On Tue, Sep 29, 2009 at 3:51 PM, Shariq Siddiqui
<shariq.siddiqui@xxxxxxxxx>wrote:


Hi All,

i am facing a lil bit problem, hope anyone out there can help me...


i want to open specific port using iptables i.e 3159

Whenever i tried to telnet it generates the following error


# telnet 172.16.4.100 3195
Trying 172.16.4.100...
telnet: connect to address 172.16.4.100: No route to host
telnet: Unable to connect to remote host: No route to hostbut when I
stopped iptables


# service iptables stopIts working fine

i added the ports in iptables i.e.


#iptables -A INPUT -p tcp --dport 3195 -j ACCEPTfor safe side I also added
telnet port


#iptables -A INPUT -p tcp --dport 23 -j ACCEPT
but result was same....

In short telnet works without iptables but with iptables it generates the
error mentioned above



Best Regards,

Shariq Siddiqui
Advanced Operations Technology
PO.Box : 25904 - Riyadh 11476
Riyadh Saudi Arabia
Tel : +966 1 291 0605 -
Fax:+966 1 291 3328






--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjectunsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list




--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Relevant Pages

  • Re: Telnet is not working with iptables
    ... You are appending to the existing rules. ... above your rule that is causing denial of the the specific port. ... rule list with iptables -nL command. ... Whenever i tried to telnet it generates the following error ...
    (RedHat)
  • Opening port on machine
    ... the firewall. ... I restarted iptables successfully and would now expect to be able to ... telnet to that port on the machine locally as I'm expecting the port to ...
    (comp.os.linux.security)
  • Re: Opening port on machine
    ... the firewall. ... Standard RHEL4 iptables setup with your port 5505/tcp add. ... telnet to that port on the machine locally as I'm expecting the port to ...
    (comp.os.linux.security)
  • RE: Could not open connection to the host, on port 143
    ... "iptables -L" is showing perfect output. ... Subject: RE: Could not open connection to the host, on port 143 ... I am not able to telnet to this box at port 143. ...
    (RedHat)
  • RE: redhat-list Digest, Vol 4, Issue 38
    ... Re: Iptables: port 22 open only for my IP ... Windows Services for Unix 3.5 ... It does absolutely nothing if you have a rampant application on your Windows box that opens a port to the outside world. ...
    (RedHat)