From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: More nf_conntrack_sip questions
Date: Sat, 06 Dec 2008 16:31:11 -0800 [thread overview]
Message-ID: <493B194F.20805@redfish-solutions.com> (raw)
In-Reply-To: <4939754F.50905@trash.net>
Patrick McHardy wrote:
> Philip Prindeville wrote:
>> Patrick McHardy wrote:
>>> Try sip_direct_media=0
>>
>> That's not an option in 2.6.25.19... when did it get introduced? Do
>> we need to run a more recent version to pick up useful fixes?
>>
>> Also, does 2.6.25.19 include the port-range helpers?
>>
>> Unless I'm misunderstanding something....
>
> That version is known not to work very well, 2.6.26 includes
> a largely rewritten version.
>
> This is a backport to 2.6.25:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-2.6.25-sip.git
Well, it might be easier to simply jump to 2.6.26.8 (unless there's
something horribly wrong with that version).
Just means going through patch hell again as we munge patches for ocf,
imq, squashfs, unionfs, multi-routing, etc.
Say, I've been wondering about that: what is the status of dead default
gateway detection? Not sure why it requires a patch and isn't just
something selectable via CONFIG_xxx...
-Philip
next prev parent reply other threads:[~2008-12-07 0:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 22:36 More nf_conntrack_sip questions Philip Prindeville
2008-12-05 16:21 ` Patrick McHardy
2008-12-05 18:00 ` Philip Prindeville
2008-12-05 18:07 ` Patrick McHardy
2008-12-05 18:08 ` Patrick McHardy
2008-12-05 18:10 ` Philip Prindeville
2008-12-05 18:13 ` Patrick McHardy
2008-12-05 18:16 ` Philip Prindeville
2008-12-05 18:19 ` Patrick McHardy
2008-12-05 18:32 ` Philip Prindeville
2008-12-05 18:39 ` Patrick McHardy
2008-12-07 0:31 ` Philip Prindeville [this message]
2008-12-07 16:06 ` Patrick McHardy
2008-12-08 0:28 ` Philip Prindeville
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=493B194F.20805@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).