All of lore.kernel.org
 help / color / mirror / Atom feed
From: Portedaix <portedaix@gmail.com>
To: netfilter@vger.kernel.org
Subject: iptables rule for ovh
Date: Thu, 29 Jul 2010 11:08:31 +0200	[thread overview]
Message-ID: <4C51450F.7070906@gmail.com> (raw)

Hello,

QUESTION - SHORT VERSION :
Is there a way to have a rule equivalent to the one below which is for 
kernel 2.6.14 and above,  with a linux kernel 2.6.9 ?
'#iptables -A INPUT -p udp -m udp --dport 5060 -m string --string 
"Cirpack KeepAlive Packet" --algo bm --to 65535 --source sip.ovh.net -j 
DROP'

QUESTION - DETAILED VERSION :

I use a sip telephone line from OVH and run asterisk PBX on a sme linux 
server to connect to it.
The asterisk command line is polluted by an error message.

#chan_sip.c:7289 determine_firstline_parts: Bad request protocol Packet

asterisk debug shows

#<--- SIP read from 91.121.129.17:5060 --->
#Cirpack KeepAlive Packet


I could avoid that by activating the rule

#iptables -A INPUT -p udp -m udp --dport 5060 -m string --string 
"Cirpack KeepAlive Packet" --algo bm --to 65535 --source sip.ovh.net -j DROP

But my main problem is this string module. My kernel is 2.6.9, and 
string module is used starting from 2.6.14 kernel. Upgrading the kernel 
on my production server is not easy, and may lead to a heavy 
reconfiguration. So if I can find a way just to have this rule 
activated, that would be fine.

Thanks in advance for any help.
Olivier



             reply	other threads:[~2010-07-29  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  9:08 Portedaix [this message]
2010-07-29  9:30 ` iptables rule for ovh Pascal Hambourg
2010-07-31  9:23   ` Portedaix
2010-07-31 11:10     ` Pascal Hambourg
2010-07-29  9:30 ` Richard Horton
2010-07-29  9:34   ` Pascal Hambourg
2010-07-29  9:47 ` Jan Engelhardt
2010-07-29 10:07   ` Richard Horton

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=4C51450F.7070906@gmail.com \
    --to=portedaix@gmail.com \
    --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 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.