Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: cerowrt-users@lists.bufferbloat.net
Subject: Re: [Cerowrt-users] no xt_TRACE in kernel
Date: Mon, 4 Mar 2013 22:07:02 -0800	[thread overview]
Message-ID: <20130305060702.GE15079@merlins.org> (raw)
In-Reply-To: <20130305050111.GB15079@merlins.org>

On Mon, Mar 04, 2013 at 09:01:11PM -0800, Marc MERLIN wrote:
> But if I do this from the lan, it shoul darrive on br-lan and be re-forwarded out 
> on the br-lan interface, but that's not working.

I forgot to say that the answer to this is to use SNAT, something like
iptables -t nat -I POSTROUTING 1 -d dest -p tcp --dport 443 -s 192.168.1.1/24 -j SNAT --to 192.168.1.254

but my question was more about xt_TRACE than fixing this specific problem :)

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

      reply	other threads:[~2013-03-05  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05  5:01 Marc MERLIN
2013-03-05  6:07 ` Marc MERLIN [this message]

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=20130305060702.GE15079@merlins.org \
    --to=marc@merlins.org \
    --cc=cerowrt-users@lists.bufferbloat.net \
    /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