All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Sérgio Bernardino" <sergio.bernardino@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: LibIPQ issue
Date: Wed, 09 Mar 2005 00:29:28 +0100	[thread overview]
Message-ID: <422E3558.8050200@trash.net> (raw)
In-Reply-To: <e54bc188050308150854d6b128@mail.gmail.com>

Sérgio Bernardino wrote:
> After a bit more time working with this i realized something "interesting":
> When i send a packet from a machine A to a machine B and capture it in
> PRE_ROUTING, if i change the destination address so that it points to
> machine C, the packet disappears and i can't track it anywhere. On the
> other hand, if i instead change the source address of the packet so
> that it points to machine C everything works fine. I can "see" the
> packet traversing into machine B, which receives the packet and
> promptly replies sending a packet to machine C. Machine A never
> receives a reply to the packet it sent and machine C receives a reply
> from a packet it never sent. Exactly the behaviour expected when
> changing the source address field. Now, if this works in this case,
> merely changing it to alter the destination address (my original
> intention) should work also, but it doesn't.
> My code can't be incorrect in a situation like this, so what exactly
> is wrong? And is there a away to solve such situation?
> Ideas anyone?

Have you got IP forwarding enabled ?

echo 1 >/proc/sys/net/ipv4/ip_forward

Regards
Patrick

  reply	other threads:[~2005-03-08 23:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 12:51 LibIPQ issue Sérgio Bernardino
2005-03-07 13:10 ` Patrick McHardy
2005-03-07 19:17   ` Sérgio Bernardino
2005-03-07 19:30     ` Patrick McHardy
2005-03-08 23:08       ` Sérgio Bernardino
2005-03-08 23:29         ` Patrick McHardy [this message]
2005-03-08 23:30         ` Sven Schuster
2005-03-09  0:36           ` Sérgio Bernardino

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=422E3558.8050200@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=sergio.bernardino@gmail.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.