Re: netfilter & SIP
- From: Balwinder S Dheeman <bsd.SANSPAM@xxxxxxxxxxxxxxxxx>
- Date: Sat, 29 Sep 2007 01:41:57 +0530
On 09/28/2007 09:27 PM, Mark T.B. Carroll wrote:
Balwinder S Dheeman <bsd.SANSPAM@xxxxxxxxxxxxxxxxx> writes:
(snip)
I have:
[bsd@cto ~]$ grep SIP=. /usr/src/linux-2.6.22.8/.config
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_NAT_SIP=m
</blah>
Mmmm. My problem is my ISP gives me an RFC1918 address on my external
interface but they route a static routable IP address to it, in a sort
of NAT-on-their-end. So, if I try using the netfilter stuff above,
it puts the wrong IP address as the place to find me.
That's why people prefer STUN, which is much more mature compared to
netfilter. In some of the cases, where your SIP client and, or server
does not have STUN functionality, we may still use some independent STUN
client to discover our external IP and reconfigure the iptables accordingly.
--
Dr Balwinder S "bsd" Dheeman Registered Linux User: #229709
Anu'z Linux@HOME Machines: #168573, 170593, 259192
Chandigarh, UT, 160062, India Gentoo, Fedora, Debian/FreeBSD/XP
Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/
.
- Follow-Ups:
- Re: netfilter & SIP
- From: Pascal Hambourg
- Re: netfilter & SIP
- References:
- netfilter & SIP
- From: Miss Terre
- Re: netfilter & SIP
- From: Mark T.B. Carroll
- Re: netfilter & SIP
- From: Miss Terre
- Re: netfilter & SIP
- From: Balwinder S Dheeman
- Re: netfilter & SIP
- From: Miss Terre
- Re: netfilter & SIP
- From: Balwinder S Dheeman
- Re: netfilter & SIP
- From: Mark T.B. Carroll
- netfilter & SIP
- Prev by Date: Olicom CrossFire 9100 software
- Next by Date: Re: netfilter & SIP
- Previous by thread: Re: netfilter & SIP
- Next by thread: Re: netfilter & SIP
- Index(es):