Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Dmitri <dk-netfilter@nth.ca>
To: netfilter@lists.netfilter.org
Subject: Re: matching -d to a given interface without specifying ip address
Date: Thu, 07 Sep 2006 22:03:55 -0400	[thread overview]
Message-ID: <4500CF8B.8060304@nth.ca> (raw)
In-Reply-To: <000601c6d0a5$da2c37b0$0101000a@tanjian>

Rob Sterenborg wrote:
> Yes, but there is a difference:
> Here you are talking about packets that come from your client that are
> sent to Google. These do not have the destination IP of the firewall box
> but pass through the firewall because you have set your gateway
> according. Besides, that would be SNAT which is something else.
...
 > ... A client from the internet can
 > only point to your public IP ...

Yes, but a client from the local network can either point at google's 
ip, or the public or private IP of the gateway. I wanted to detect these 
cases. It's specifically about local clients, whichever IP they're 
pointing to.

> Perhaps you're confusing DNAT with SNAT?
> When packets for Google pass through it's (initial) direction is from
> your LAN to the internet and packets are SNAT-ed. This is the opposite
> of what you want above.

No, I'm not confusing DNAT with SNAT. SNAT, particularly MASQUERADE, is 
happening anyway for -o ppp0. But I wanted to DNAT some things directed 
to the box itself to some other destination. When they come -o ppp0, 
they will get MASQUERADEd as well.

Anyway, I think I have the answer to my question, as explained in my 
response to Danny.

Thanks,
--Dmitri


  reply	other threads:[~2006-09-08  2:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02 22:32 matching -d to a given interface without specifying ip address Dmitri
2006-09-04  5:05 ` Rob Sterenborg
2006-09-05  4:42   ` Dmitri
2006-09-05  4:43     ` Rob Sterenborg
2006-09-08  2:03       ` Dmitri [this message]
2006-09-06 18:11     ` Danny Rathjens
2006-09-08  1:42       ` Dmitri
2006-09-08  9:44         ` Pascal Hambourg
2006-09-08  9:26 ` Pascal Hambourg

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=4500CF8B.8060304@nth.ca \
    --to=dk-netfilter@nth.ca \
    --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