All of lore.kernel.org
 help / color / mirror / Atom feed
From: "C. L. Martinez" <carlopmart@gmail.com>
To: Tom van Leeuwen <tom.van.leeuwen@saasplaza.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Problems with a forward rule
Date: Mon, 14 May 2012 09:06:20 +0200	[thread overview]
Message-ID: <CAEjQA5+kYHgcm3FGkz_AEhTa6ASv8w5sWQQxAOkszeDM3=ukZQ@mail.gmail.com> (raw)
In-Reply-To: <4FB0AE39.6040805@saasplaza.com>

On Mon, May 14, 2012 at 9:03 AM, Tom van Leeuwen
<tom.van.leeuwen@saasplaza.com> wrote:
> So, when you do a ping from your host 172.24.50.3 to 1.1.1.x you will
> probably see the counter increase for your rule (with restricted
> destination).
> Do "iptables -vnL FORWARD" to check.
>
> That rule is not the problem.
>
> What traffic are you sending that times out?
> source ip, source port, destination ip, dest port, protocol?
>
> Your forward and postrouting rules look fine and should work
>
> Regards,
> Tom

My principal problems are with http, https and ssh. For example with a
https connection:

Chain FORWARD (policy DROP 48 packets, 2432 bytes)
 pkts bytes target     prot opt in     out     source
destination
 4628 1901K ACCEPT     all  --  *      *       0.0.0.0/0
0.0.0.0/0           state RELATED,ESTABLISHED
   12   746 ACCEPT     all  --  *      *       172.24.50.3
10.196.0.0/16       state NEW
   42  2184 ACCEPT     tcp  --  *      *       172.24.50.3
195.76.69.66        tcp multiport dports 80,443 state NEW
    1    52 ACCEPT     tcp  --  *      *       172.24.50.3
195.76.69.69        tcp dpt:443 state NEW
   48  2432 LOG        all  --  *      *       0.0.0.0/0
0.0.0.0/0           LOG flags 0 level 4 prefix `IPT FORWARD packet
died: '

First packets goes well, but after few seconds all goes to "IPT
FORWARD .." chain ...

  reply	other threads:[~2012-05-14  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 15:04 Problems with a forward rule C. L. Martinez
2012-05-12 15:47 ` Jan Engelhardt
2012-05-12 20:53   ` Tom van Leeuwen
2012-05-14  5:45     ` C. L. Martinez
2012-05-14  6:33       ` Tom van Leeuwen
2012-05-14  6:40         ` C. L. Martinez
2012-05-14  7:03           ` Tom van Leeuwen
2012-05-14  7:06             ` C. L. Martinez [this message]
2012-05-14  7:24               ` Tom van Leeuwen
2012-05-14 16:47                 ` carlopmart
2012-05-14  7:26       ` Neal Murphy
2012-05-14  8:18         ` C. L. Martinez
2012-05-14 17:55           ` Neal Murphy
2012-05-14 19:35             ` carlopmart
2012-05-14 21:12               ` Neal Murphy

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='CAEjQA5+kYHgcm3FGkz_AEhTa6ASv8w5sWQQxAOkszeDM3=ukZQ@mail.gmail.com' \
    --to=carlopmart@gmail.com \
    --cc=netfilter@vger.kernel.org \
    --cc=tom.van.leeuwen@saasplaza.com \
    /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.