From: Maarten Vanraes <maarten@ba.be>
To: Eliezer Croitoru <eliezer@ngtech.co.il>
Cc: Pascal Hambourg <pascal@plouf.fr.eu.org>, netfilter@vger.kernel.org
Subject: Re: advanced routing with NAT: returning UDP traffic
Date: Wed, 24 Sep 2014 14:52:51 +0200 [thread overview]
Message-ID: <3545996.7GKZQHL5tP@localhost> (raw)
In-Reply-To: <5422BB42.6040707@ngtech.co.il>
Op woensdag 24 september 2014 15:38:26 schreef Eliezer Croitoru:
> On 09/24/2014 01:16 PM, Maarten Vanraes wrote:
> > ok, thanks,
> >
> > so, this is why streaming/voip stuff will still have issues...
>
> Yes indeed.
> and I Meant conntrack and connmark...
> VOIP and STREAMING are beasts!!!
> There are modules which analyze them and also recognize them but you
> will need to enable them first.
>
> The issue is not UDP by itself as you understand.
> It's a well known issue with multi IP nat machines in ISPS.
> In many cases a SIP proxy helps to fix couple things.
> I haven't tried it yet but it seems like there are commercial products
> that implement these SIP proxy.
i've used siproxd before... but it's limited, i could set up an asterisk in
between, but that might be overkill and i'm not sure i could intercept it
without configuring stuff on the other side...
what kind of modules do you know that help conntracking this kind of stuff?
and... what about ipv6 and multiple ISPs? (but without natting, but still no
bgp or something), won't i still have the same problem?
Regards,
Maarten
--
BA NV
IT & Security
next prev parent reply other threads:[~2014-09-24 12:52 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 [this message]
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=3545996.7GKZQHL5tP@localhost \
--to=maarten@ba.be \
--cc=eliezer@ngtech.co.il \
--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 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).