Linux Netfilter discussions
 help / color / mirror / Atom feed
From: David Cannings <lists@edeca.net>
To: netfilter@lists.netfilter.org
Subject: Re: Not forwarding?
Date: Sun, 28 Mar 2004 21:43:47 +0100	[thread overview]
Message-ID: <200403282143.47746.lists@edeca.net> (raw)
In-Reply-To: <20040328155231.32b07799@darna.vectec.net>

On Sunday 28 March 2004 20:52, Cody Harris wrote:
> This is my firewall setup:
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     all  --  anywhere             anywhere
> ACCEPT     icmp --  anywhere             anywhere           icmp
> echo-reply ACCEPT     icmp --  anywhere             anywhere          
> icmp destination-unreachable ACCEPT     icmp --  anywhere            
> anywhere           icmp redirect ACCEPT     icmp --  anywhere          
>   anywhere           icmp echo-request ACCEPT     icmp --  anywhere    
>         anywhere           icmp time-exceeded ACCEPT     tcp  -- 
> anywhere             192.168.0.2        tcp dpt:ssh
> We have noticed that ssh isn't getting forwarded. What's wrong?

What about the replies from SSH which will come from source port 22?  
Either add a rule to explicitly allow from sport ssh or add an 
ESTABLISHED/RELATED rule in there.

David


  reply	other threads:[~2004-03-28 20:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 19:52 Not forwarding? Cody Harris
2004-03-28 20:43 ` David Cannings [this message]
2004-03-28 20:54   ` Antony Stone
2004-03-28 21:07     ` Cody Harris
2004-03-28 21:15       ` David Cannings
2004-03-29 19:53         ` Cody Harris
2004-03-28 21:24       ` Antony Stone
2004-03-29 19:51         ` Cody Harris
2004-03-29 20:26           ` Cody Harris
2004-03-29 21:42             ` Antony Stone
2004-03-29 22:56               ` Cody Harris
2004-03-30  7:48                 ` Antony Stone
2004-03-30 11:33                   ` Cody Harris
2004-03-30 11:53                     ` Antony Stone
2004-03-30 20:01                       ` Adding a flag to a packet Cody Harris
2004-03-30 20:24                         ` Antony Stone
2004-03-30 20:35                           ` Cody Harris
2004-03-30 20:50                             ` Antony Stone
2004-03-30 21:06                               ` Cody Harris
2004-03-30 21:23                                 ` Antony Stone
2004-03-30 21:28                                   ` Cody Harris
2004-03-30 21:40                                     ` Antony Stone
2004-03-30 22:19                                       ` Cody Harris
2004-03-31  8:19                                     ` Cedric Blancher
2004-03-31  8:22                               ` Cedric Blancher
2004-03-30 22:12                             ` Tony Earnshaw
2004-03-30 22:25                               ` Cody Harris
2004-03-30 23:46                               ` Antony Stone
2004-03-31  0:21                                 ` Tony Earnshaw
2004-03-28 20:48 ` Not forwarding? Antony Stone
2004-03-28 20:59   ` Cody Harris
2004-03-28 21:09     ` Antony Stone
2004-03-28 21:16       ` Cody Harris
2004-03-28 21:14     ` David Cannings
2004-03-28 21:15   ` Cody Harris
2004-03-28 21:32     ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2004-03-28 19:49 Cody Harris

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=200403282143.47746.lists@edeca.net \
    --to=lists@edeca.net \
    --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