From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: Maarten Vanraes <maarten@ba.be>
Cc: netfilter@vger.kernel.org
Subject: Re: advanced routing with NAT: returning UDP traffic
Date: Wed, 24 Sep 2014 11:49:02 +0200 [thread overview]
Message-ID: <5422938E.2030104@plouf.fr.eu.org> (raw)
In-Reply-To: <4623776.NNCmRlCAkc@localhost>
Maarten Vanraes a écrit :
>
> so, even some kind of odd udp reply will still be the same connection if it's
> within 30seconds?
Not odd. The reply packet has to match the addresses and ports in the
original packet (with source and destination swapped).
> so, i can use connmark on not just TCP, but on all protocols?
Not all protocols, but any protocol implementation which behaves in the
way expected by conntrack.
next prev parent reply other threads:[~2014-09-24 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 12:46 advanced routing with NAT: returning UDP traffic Maarten
2014-09-23 17:41 ` Eliezer Croitoru
2014-09-24 9:35 ` Maarten Vanraes
2014-09-24 9:49 ` Pascal Hambourg [this message]
2014-09-24 10:16 ` Maarten Vanraes
2014-09-24 12:38 ` Eliezer Croitoru
2014-09-24 12:52 ` Maarten Vanraes
2014-09-26 13:18 ` Pascal Hambourg
2014-09-26 14:02 ` Maarten Vanraes
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=5422938E.2030104@plouf.fr.eu.org \
--to=pascal@plouf.fr.eu.org \
--cc=maarten@ba.be \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).