From: Patrick McHardy <kaber@trash.net>
To: Nils Ohlmeier <lists@ohlmeier.org>
Cc: netfilter-devel@lists.netfilter.org,
Christian Hentschel <chentschel@arnet.com.ar>,
Harald Welte <laforge@gnumonks.org>,
Harry Behrens <harry@behrens.com>
Subject: Re: SIP helper review
Date: Mon, 20 Feb 2006 18:34:59 +0100 [thread overview]
Message-ID: <43F9FDC3.50102@trash.net> (raw)
In-Reply-To: <200602192312.05240.lists@ohlmeier.org>
Nils Ohlmeier wrote:
> Hello,
>
> I'm not a kernel programer but with several years experience in the SIP
> business I could call myself a SIP expert I guess. Therefor I was asked by a
> friend to take a look at the current SIP netfiler module.
>
> So I made a code review of the code from this link:
> http://svn.netfilter.org/netfilter/trunk/patch-o-matic-ng/patchlets/sip-conntrack-nat/linux-2.6.13/
Thanks for your help.
> From looking at the code I think I found the following two issues which might
> be worth fixing:
>
> 1) As far as I got it the skp_epaddr_len function in ip_conntrack_sip.c
> expects to find a username in the SIP URI in the Contact header. As usernames
> are generally optional in SIP URIs there are several User Agents (UA),
> especially the cheaper hardware UA's which support only one SIP account,
> which do not put a username into their Contact's. Thus I would propose that
> the searching for the username in the Contact header should be optional as
> well.
I think this is what made the helper fail with my crappy chinese SIP
ATA. Without the username, is there still an '@'-character (in which
case it should work as it is) or does the string start directly with
the address?
> 2) As far as I got it the epaddr_len function looks for 'UDP' in Via headers.
> Is it by intention that the IP address replacement would only work for the
> UDP transport but not for TCP? Allthough TCP is not very widely used yet I
> think it should be easy to do the replacement for TCP as well, or?
It should be easy to change. Is TCP used for SIP itself? In that case
it would also have to register for TCP in addition to UDP.
next prev parent reply other threads:[~2006-02-20 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 22:12 SIP helper review Nils Ohlmeier
2006-02-20 17:34 ` Patrick McHardy [this message]
2006-02-20 20:45 ` Nils Ohlmeier
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=43F9FDC3.50102@trash.net \
--to=kaber@trash.net \
--cc=chentschel@arnet.com.ar \
--cc=harry@behrens.com \
--cc=laforge@gnumonks.org \
--cc=lists@ohlmeier.org \
--cc=netfilter-devel@lists.netfilter.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.