Change Details

It looks like that since [[ https://cgit.FreeBSD.org/src/commit/?id=fdb987bebddf05e15a5af840379c7715a94aec1c | fdb987bebddf05e15a5af840379c7715a94aec1c ]] it is not possible anymore to use the `inp_next` iterator for bound and unconnected sockets. In the TCP case, these are listening sockets. This breaks `tcpsso` when used without the `-i` option. Fallback to iterate through all endpoints, which is not as performant as it was, but un-breaks `tcpsso`.

It looks like that since [[ https://cgit.FreeBSD.org/src/commit/?id=fdb987bebddf05e15a5af840379c7715a94aec1c | fdb987bebddf05e15a5af840379c7715a94aec1c ]] it is not possible anymore to use the `inp_next` iterator for bound but unconnected sockets. In the TCP case, these are listening sockets. This breaks `tcpsso` when used without the `-i` option. Fallback to iterate through all endpoints, which is not as performant as it was, but un-breaks `tcpsso`.

It looks like that since [[ https://cgit.FreeBSD.org/src/commit/?id=fdb987bebddf05e15a5af840379c7715a94aec1c | fdb987bebddf05e15a5af840379c7715a94aec1c ]] it is not possible anymore to use the `inp_next` iterator for bound andbut unconnected sockets. In the TCP case, these are listening sockets. This breaks `tcpsso` when used without the `-i` option. Fallback to iterate through all endpoints, which is not as performant as it was, but un-breaks `tcpsso`.