Re: Should the module nf_conntrack_sip also be included in rc.net?

On 7/16/2014 7:23 AM, Administrator wrote:
> On Mon, 2014-07-14 at 20:46 -0700, David W Studeman wrote:
>> On 7/13/2014 4:44 PM, Jack Beglinger wrote:
>> > David -
>> >
>> > Could adding a configuration page better?  So SIP can turned on/off as
>> > needed.  And the ports could be changed that way also.
>> >
>> > jackb
>> >
>> It could if anyone has the time, desire and skill to do it. It isn't
>> something that needs to be changed often. In any case, it would need to
>> be loaded when the other nf modules are loaded namely in rc.net.
>>
> If you would like to make the UI addition possible, you'd need to create
> a config file and a start/stop/reload script that could be used by the
> UI to effect the changes.
>
> David
>
Scripts like that are for services, not to reload a single kernel module 
and the script that it should be in already exists as rc.net which 
starts all the netfilter modules. Unloading and reloading the individual 
module should not even occur frequently enough to warrant much fuss and 
likely not at all. nf_nat_sip should never be loaded as it is nothing 
but trouble and nf_conntrack_sip would cover the majority of people 
using VOIP with it's default parameters since port 5060 will almost 
always be used and you will almost always be doing sip signaling as well 
as rtp through the server of your provider.

A relative of SIP's, h323, already has it's modules loaded by rc.net 
even though nf_conntrack_h323 also has parameters that can be set in a 
modules.conf file just like nf_conntrack_sip does but most people would 
need nothing but have it loaded invibly as nf_conntrack_h323 already is. 
I've never heard anyone complain about needing to tweak 
nf_conntrack_h323 module loading options so that their net meeting will 
work correctly.

If it were to make it into the gui, it would only need a tiny space of 
an existing page such as Firewall Settings and in advanced mode only at 
that. The cgi itself could easily handle unloading and reloading a 
module when changes are saved. The config file in any case would go in 
/etc/modprobe.d.

The original question is whether it (nf_conntrack_sip) should be loaded 
by default. I think it should be but it's not my call. If not, I can 
easily have it loaded in my own individual installation in either 
/etc/modules (would it load too soon?) or rc.event.local. It would need 
to be loaded after rc.net if outside of that since rc.net loads the base 
nf_conntrack module which is needed by nf_conntrack_sip.
-- 
Dave Studeman
http://www.raqcop.com


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds