All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Netfilter and SCTP
Date: 30 Apr 2003 16:04:44 +0200	[thread overview]
Message-ID: <1051711484.1690.121.camel@raylinux.internal> (raw)
In-Reply-To: <Law8-F94rhYQYx3G5aY000150f0@hotmail.com>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

Hi

Isn't SCTP just a sub-protocol of TCP/IP?

If it is then you can use rules like this:

iptables -A FORWARD -i eth0 -p 132 -s 1.2.3.4 -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT


This is what I do for protocol 47 which is used by MS VPN connections.

Ray

On Wed, 2003-04-30 at 14:50, Cyrille Colin wrote:
> Hi,
> 
> I would like to know how Netfilter's translator deals with SCTP / IP packets 
> (Stream Control Transmission Protocol, IP protocol 132).
> 
> similarly to UDP, it should be able to translate the source adress in the IP 
> header, and the source port in the SCTP common header, if needed. And 
> recompute SCTP and IP headers checksums.
> 
> is this currently supported ? if not how Netfilter behave when receiving 
> such a packet ??
> 
> any help on this would be very much appreciated... seems that NAT boxes do 
> not like SCTP very much...
> 
> 
> Thanks
> 
> Cyrille
> 
> 
> 
> 
> 
> _________________________________________________________________
> MSN Messenger : discutez en direct avec vos amis ! 
> http://www.msn.fr/msger/default.asp
> 
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-30 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 12:50 Netfilter and SCTP Cyrille Colin
2003-04-30 14:04 ` Ray Leach [this message]
2003-04-30 15:12   ` Maciej Soltysiak
2003-04-30 14:24 ` Martin Josefsson
2003-05-03 15:14   ` Harald Welte

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=1051711484.1690.121.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --cc=netfilter@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.