-
sctp
SCTP Discussions
Text archives Help
- From: "Noam Rathaus" <noamr AT beyondsecurity.com>
- To: sctp-discussion AT sctp.de
- Subject: [SCTP-Discussion] Association ID doesn't "rollover"
- Date: Mon, 17 Nov 2008 18:02:39 +0200
- List-archive: <http://lists.franken.de/pipermail/sctp-discussion>
- List-id: SCTP Discussions <sctp-discussion.sctp.de>
Hi,
The SCTP Library apparently has not been built to address more than
65,535 connections, after which the association ID should have reset
itself to 0x0001, instead it goes beyond the 0xFFFF value, which
causes all subsequent packets to get lost (as they are unassociated
with anything on the sender side).
I have a patch for this, if you are interested, I might have done
something wrong which needs to be done to prevent this, but it looks
like the assocID is always incremented (never decremented).
Another side issue is that if you never "delete" the associated
records, the port table will get filled, with used ports, and
subsequent requested to associated a new connection will get stuck in
an endless loop as it looks for an available position (where there is
none), this is worth fixing as well (pretty easy if you use a static
counter to count how many ports are left for use).
- [SCTP-Discussion] Association ID doesn't "rollover", Noam Rathaus, 11/17/2008
- Re: [SCTP-Discussion] Association ID doesn't "rollover", Thomas Dreibholz, 11/18/2008
Archive powered by MHonArc 2.6.19+.
