All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thhoep" <thhoep@gmx.de>
To: Ramin Dousti <ramin@cannon.eng.us.uu.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Fri, 9 Jan 2004 21:09:14 +0100	[thread overview]
Message-ID: <004101c3d6ec$7801b6b0$1684188d@Kiste> (raw)
In-Reply-To: 20040109204745.GE24304@cannon.eng.us.uu.net

> Except if it's being dropped by conntrack... And remember, tcpdump sees
stuff
> before the stack does its thing to the packets.

is there a logical reason (besides some bug in the code) why it should drop
something? i thought (but aint sure) that the "demasquerading" happens right
in the prerouting, before the routing process, so that no routing rule in
the world could disturb it?

> An ICMP is not being sent for another ICMP. But I guess an ICMP for ping
> can be sent, though.

.. you made me think with that.. ;) but i've just tested it with http
requests. no icmp errors either.

> You got me there. Try to reduce the complexity of your setup (just bring
> up one ppp, remove the unnecessary tables and so forth) and retest again.
> If the test passes then add little by little to your setup. I'm sure
you'll
> find/locate the problem that way.

i just did it. killed all other ppp connections, there was just eth4 (the
local lan interface), ppp0 and a bunch of non-ip ethernet interfaces. but
the result was the same, and no mis-guided packages in either direction.

i've really no clue what to do now.

i will try to reproduce the configuration on another server here.



  reply	other threads:[~2004-01-09 20:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 23:05 Iproute2 and fwmark usage Thhoep
2004-01-09 16:47 ` Ramin Dousti
2004-01-09 16:17   ` Thhoep
2004-01-09 17:35     ` Ramin Dousti
2004-01-09 16:50       ` Thhoep
2004-01-09 19:42         ` Ramin Dousti
2004-01-09 19:06           ` Thhoep
2004-01-09 20:47             ` Ramin Dousti
2004-01-09 20:09               ` Thhoep [this message]
2004-01-09 21:22                 ` Ramin Dousti
2004-01-09 21:30                   ` Thhoep
2004-01-09 22:02                     ` Thhoep
2004-01-11 20:57                       ` Thhoep
2004-01-11 21:07                         ` Antony Stone
2004-01-11 21:50                           ` Thhoep
2004-01-11 23:12                             ` Thhoep
2004-01-11 23:22                               ` Antony Stone
2004-01-13 23:46                               ` Thhoep
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:20 Filter out broadcast messages Gabby James
2004-01-08 14:31 ` iproute2 and fwmark usage Thhoep

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='004101c3d6ec$7801b6b0$1684188d@Kiste' \
    --to=thhoep@gmx.de \
    --cc=netfilter@lists.netfilter.org \
    --cc=ramin@cannon.eng.us.uu.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 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.