Sorry to be such a pain, but I installed this on a pristine installation
of RH 9.0 (ie, no OpenSS7 on it) and I still have the same issue.
Did I misunderstand when you stated that I couldn't have a kernel
w/SCTP. I assumed that I now had one because of the OpenSS7 install.
Is there another way or reason that I could have a kernel with SCTP?
How can I verify that I do or don't have one?
Thanks, Robin
On Thu, 2005-03-10 at 14:21, Michael Tuexen wrote:
See my comments in-line.
Best regards
Michael
On Mar 10, 2005, at 18:04 Uhr, IOT Developer-1 wrote:
I mis-spoke. This is not an OpenSS7 implementation, it is the one fromOK.
your website.
I think you do not need stt. This is a packet generator which is
I'm using sctplib-1.0.3, socketapi-1.3.2 and stt-0.9. The same issues
exist however.
used to test SCTP implementations.
If you still have a kernel with SCTP this is the cause of the problem.
Early on, I had attempted to install the OpenSS7 SCTP package, but ran
into problems and eventually adopted yours since it worked. Could the
remnants of that installation attempt be causing me problems? It is on
You need the original RedHat kernel.
the same remote host that I am launching sctpterminal from.The rule is: You can use only one SCTP implementation on a host at the
same time.
Thanks, Robin
On Thu, 2005-03-10 at 11:39, Michael Tuexen wrote:
Dear Robin,
see my comments in-line.
Best regards
Michael
On Mar 10, 2005, at 17:15 Uhr, IOT Developer-1 wrote:
Hi,This is a kernel implementation. You can not run a kernel
I have successfully compiled and installed the OpenSS7 SCTP
distribution.
implementation
and a userland implementation (like the one from www.sctp.de, which
we are supporting here) on the same host at the same time.
These programs work with the userland implementation and do not
I can also successfully execute sctpmultiserver and sctpterminal in
say
echo mode as long as they both reside on the the same host.
work with any kernel implementation.
You must decide which SCTP implementation to use:
When I attempt to connect to sctpmultiserver when sctpterminal is
being
invoked from a remote host, I cannot get a connection. At first I
thought it to be typical firewall issues, however that now doesn't
appear to be the case.
1. A kernel implementation like the one from OpenSS7 or the normal
Linux kernel implementation (they are not the same)
2. A userland implementation like the sctplib.
That is OK, if you have a kernel SCTP.
If I fire up ethereal and monitor traffic, I can for example see
connection attempts to port 7 from my remote host when I attempt to
telnet to it. I see no traffic whatsoever when I execute
sctpterminal.
This is not a ethereal capture issue, as I can readily capture theThe packets should use CRC32C, so they are adler32 checksum errors.
SCTP
messages when both client and server are on the same box.
BTW, both boxes are Redhat Linux.
Is there anything additional that I need to do for this scenario?
The
only thing odd that I noticed was that if I run ethereal on the
remote
host when executing sctpterminal, I do see an adler32 checksum error
in
one of the two SCTP packets that are generated. Would this prevent
the
packets from ever leaving the remote host? What would cause this?
Just
select in ethereal the Automatic option for checksum selection.
Thanks in advance for any help you can provide in resolving this
issue.
Robin
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion
Archive powered by MHonArc 2.6.19+.