All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai Alexandrov <voyager123bg@gmail.com>
To: vladimir@fetchbook.info
Cc: netfilter@lists.netfilter.org
Subject: Re: Filtered address in can login
Date: Tue, 16 Aug 2005 20:34:59 +0300	[thread overview]
Message-ID: <430223C3.1090509@gmail.com> (raw)
In-Reply-To: <1124203482.8177.18.camel@localhost>

Are you sure your default POLICIES are ok? I mean...
do you have somewhere:
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP
... your script ...
iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

You should also consider adding rules for the DNS to work.


vladimir wrote:

>Hi, I have iptables-1.2.7a and 2.4.26 kernel and there is something
>strange.
>I have the following rule:
>iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
>iptables -A INPUT -s 0/0 --protocol tcp --destination-port 80 -j ACCEPT
>iptables -A INPUT -s IP_ADDR  --protocol tcp --destination-port 22  -j
>ACCEPT
>iptables -A INPUT -p tcp --syn -j DROP
>
>So I expect that only  the specified IP_ADDR can ssh to port 22 in my
>server.
>But in /var/log/secure I see that some other IP's for example
>168.179.113.141 try to login to ssh  with different user names to my
>server.
>However, then I try ssh to that server not from IP_ADDR I can not, as
>expected.
>Please tell me how this 168.179.113.141 bypass my firewall.
>Thank you very much, 
>Vladimir
>  
>


  reply	other threads:[~2005-08-16 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 14:44 Filtered address in can login vladimir
2005-08-16 17:34 ` Nikolai Alexandrov [this message]
2005-08-17  5:06 ` Grant Taylor
2005-08-17  5:43   ` Jan Engelhardt
2005-08-17  5:46     ` Grant Taylor

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=430223C3.1090509@gmail.com \
    --to=voyager123bg@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=vladimir@fetchbook.info \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.