From: Maarten Vanraes <maarten@ba.be>
To: Eliezer Croitoru <eliezer@ngtech.co.il>
Cc: netfilter@vger.kernel.org
Subject: Re: advanced routing with NAT: returning UDP traffic
Date: Wed, 24 Sep 2014 11:35:59 +0200 [thread overview]
Message-ID: <4623776.NNCmRlCAkc@localhost> (raw)
In-Reply-To: <5421B0B4.4040106@ngtech.co.il>
conntrack and conntrack ? i'm assuming this is a typo?
so, even some kind of odd udp reply will still be the same connection if it's
within 30seconds?
so, i can use connmark on not just TCP, but on all protocols?
Regards,
Maarten
Op dinsdag 23 september 2014 20:41:08 schreef Eliezer Croitoru:
> Hey Maarten,
>
> As long as I remember conntrack and conntrack are working together.
> Which means that udp traffic will be distinguished the same way as TCP
> as long the connection tracking categorized it under the same connection
> stream.
> (I think for unestablished connection 30 secs and more for an
> "established" one)
>
> Eliezer
>
> On 09/23/2014 03:46 PM, Maarten wrote:
> > Hi,
> >
> > until now, i've done multiple ISPs with nexthop default route, 2 extra
> > tables, ip rule and TCP connmark.
> >
> > but, how does this involve UDP traffic...
> >
> > if for example i have in my NAT LAN an NTP server, how would i get the udp
> > packet out the same interface where it was originally coming in from?
> >
> > please advise...
> >
> > Maarten
--
BA NV
IT & Security
next prev parent reply other threads:[~2014-09-24 9:35 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 [this message]
2014-09-24 9:49 ` Pascal Hambourg
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=4623776.NNCmRlCAkc@localhost \
--to=maarten@ba.be \
--cc=eliezer@ngtech.co.il \
--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).