From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Thhoep <thhoep@gmx.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Fri, 9 Jan 2004 15:47:45 -0500 [thread overview]
Message-ID: <20040109204745.GE24304@cannon.eng.us.uu.net> (raw)
In-Reply-To: <001101c3d6e3$cdf03e60$1684188d@Kiste>
On Fri, Jan 09, 2004 at 08:06:33PM +0100, Thhoep wrote:
> besides of the marking there is a masquerading active, as mentioned in
> previous mails:
> "iptables -t nat -A POSTROUTING -o ppp4 -j MASQUERADE"
>
> filter table is empty.
>
> ok, i did monitor all interfaces using
> "tcpdump -n -i ppp0 icmp and host 141.24.12.2"
> and so on. as expected nowhere a pong went out. i think any pong leaving the
> box would have showed up in the FORWARD counting rule in the first test.
Yes. But one other possibility is if you receive the return traffic through
another interface (which should not happen because you're MASQ'ing) then
the de-MASQ does not take place. But again, it doesn't have anything to do
with the MARK and rule...
> you are right. and _all_ routing tables contain a route to the local net, so
> a packet should always find its way from the outside in.
Except if it's being dropped by conntrack... And remember, tcpdump sees stuff
before the stack does its thing to the packets.
> i think even if the
> masquerading would be broken, the packet wouldnt get lost. it would show up
> somewhere OR an icmp error would be sent to its sender.
An ICMP is not being sent for another ICMP. But I guess an ICMP for ping
can be sent, though.
> so is there a bug in
> the routing code? and why am i then the only one having this problem?
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.
Ramin
next prev parent reply other threads:[~2004-01-09 20:47 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 [this message]
2004-01-09 20:09 ` Thhoep
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=20040109204745.GE24304@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=netfilter@lists.netfilter.org \
--cc=thhoep@gmx.de \
/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.