All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanasescu Mihai <skyraven@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Wierd traceroute/routing problem
Date: Thu, 06 Jan 2005 23:52:15 +0000	[thread overview]
Message-ID: <e82fadc00501061552bb66bc6@mail.gmail.com> (raw)

Hello,

I'm having a very strange problem concerning traceroute and routing
and didn't know if lartc or netfilter would be the correct choice for
asking. (so sorry if my question is misplaced)

I have the following setup:

public ip -- gw1 -- 172.16.0.1 --- 172.16.0.2/and public ip's --- gw2
--- switch --users (public and private ip addresses; ip-user-pub)

from the internet:
Traceroute to a ip-user-pub shows: public ip gw1 --> 172.16.0.2 --> ip-user-pub

I tried using SNAT on gw2 so that instead of 172.16.0.2 I would get
one of the public ip addresses I have on gw2.
It seems that packets with ttl time exceeded in transit get through to
the mangle table in POSTROUTING but no longer reach the nat table in
POSTROUTING (so they no longer get SNATed).
The same thing happens to these kind of icmp packets if I try to SNAT
them on gw1.

Tcpdump just shows me 172.16.0.2 each time, exitting the public
interfaces and the nat rule counter does not increase..

I also tried marking packets in mangle table and then seeing if that
same mark reaches the nat table (both done in POSTROUTING) and saw
that my mark no longer gets to the nat table.

Any ideea what's causing this ?
Or how can I make it so that instead of 172.16.0.2 I would get one of
gw2's public ip's ?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2005-01-06 23:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e82fadc00501061552bb66bc6@mail.gmail.com \
    --to=skyraven@gmail.com \
    --cc=lartc@vger.kernel.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 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.