From: Marek Kierdelewicz <marek@piasta.pl>
To: Barry R Cisna <brcisna@eazylivin.net>
Cc: netfilter@vger.kernel.org
Subject: Re: sip voip traffic forwarding
Date: Mon, 5 Jan 2009 23:04:03 +0100 [thread overview]
Message-ID: <20090105230403.6964e0e7@catlap> (raw)
In-Reply-To: <1231028358.31327.47.camel@localhost.localdomain>
>I would need to of course udp 5061, 10000-20000 forward to asterisk
>server from LinTS eth1,eth0?.
>Would someone be good enough to do a ,,1.,,2.,,3. how to accomplish
>this?
I hope I understand your post the way you meant. If so following
iptables rule on TS may do the job:
iptables -t nat -A PREROUTING -d 192.168.1.2 -p udp --dport 5060:5061 \
-j DNAT --to ASTERISK_ADDR
This would allow connections coming from internet to be redirected to
asterisk box. Rules above may not work in the desired way if you
already have some entries in PREROUTING chain or some of the traffic
is filtered.
Regards,
Marek Kierdelewicz
prev parent reply other threads:[~2009-01-05 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 0:19 sip voip traffic forwarding Barry R Cisna
2009-01-05 22:04 ` Marek Kierdelewicz [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=20090105230403.6964e0e7@catlap \
--to=marek@piasta.pl \
--cc=brcisna@eazylivin.net \
--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