From: "Franklin Marmon" <marmon@hydeco.com>
To: linux-sctp@vger.kernel.org
Subject: address already in use on previously used (but currently unused) IP:PORT combinations in sctp_bindx(
Date: Tue, 01 Aug 2017 19:43:47 +0000 [thread overview]
Message-ID: <0bbe01d30afe$80ce96f0$826bc4d0$@hydeco.com> (raw)
Hello,
I'm having trouble with sctp_bindx() reporting address already in use when
attempting to bind sockets. The IP:PORT combinations are not open, do not
show up in /proc/net/sctp/assocs, netstat, ss, or lsof. The IP:PORTs were
bound in a previous instance of the client application however that
application itself has been killed and restarted. It is as if the kernel
believes the IP:PORT pair is in use when, as far as I can tell, it isn't. If
I change the ports used in my addresses to ports I have not used previously
the bind succeeds without issue. Any suggestions on how I can tell what is
holding the ports open, or how to reset the sctp port table in the kernel?
Lksctp-tools verison: 1.0.16
Kernel version: 4.4.6
IP-Family: IPv4
Number of addresses passed to sctp_bindx(): normally 2, have tested with
each address individually
frm
Franklin Marmon
The Hyde Company
331 East Broadway
Missoula, MT 59801
Office: 406.541.4777
Cell: 406.493.2460
http://www.hydeco.com
marmon@hydeco.com
next reply other threads:[~2017-08-01 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 19:43 Franklin Marmon [this message]
2017-08-02 9:08 ` address already in use on previously used (but currently unused) IP:PORT combinations in sctp_bi David Laight
2017-08-02 13:28 ` Xin Long
2017-08-02 14:08 ` Franklin Marmon
2017-08-02 14:09 ` Franklin Marmon
2017-08-03 0:37 ` Xin Long
2017-11-20 16:29 ` Franklin Marmon
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='0bbe01d30afe$80ce96f0$826bc4d0$@hydeco.com' \
--to=marmon@hydeco.com \
--cc=linux-sctp@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.