From: Maarten Vanraes <maarten@ba.be>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: advanced routing with NAT: returning UDP traffic
Date: Fri, 26 Sep 2014 16:02:37 +0200 [thread overview]
Message-ID: <1548623.uVd0b5ANDY@localhost> (raw)
In-Reply-To: <542567B2.4060800@plouf.fr.eu.org>
Op vrijdag 26 september 2014 15:18:42 schreef Pascal Hambourg:
> Maarten Vanraes a écrit :
> > Op woensdag 24 september 2014 15:38:26 schreef Eliezer Croitoru:
> >> VOIP and STREAMING are beasts!!!
> >> There are modules which analyze them and also recognize them but you
> >> will need to enable them first.
> >
> > what kind of modules do you know that help conntracking this kind of
> > stuff?
>
> For SIP : nf_conntrack_sip. There is a nf_conntrack_<protocol> helper
> for each supported "complex" protocol (FTP, IRC, PPTP...). Their purpose
> is to set the state of the first packet of the data connection to
> RELATED, and copy the connmark of the control connection to the data
> connection. On a box doing NAT, you also need the related
> nf_nat_<protocol> module.
>
> > and... what about ipv6 and multiple ISPs? (but without natting, but still
> > no bgp or something), won't i still have the same problem?
>
> Yes.
awesome, this makes it totally clear... thx!
--
BA NV
IT & Security
prev parent reply other threads:[~2014-09-26 14:02 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
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 [this message]
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=1548623.uVd0b5ANDY@localhost \
--to=maarten@ba.be \
--cc=netfilter@vger.kernel.org \
--cc=pascal@plouf.fr.eu.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 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.