schat and dccbounce doesn't allow setting a portrange, this should be added to ZNC to make it possible to use behind a firewall.
schat and dccbounce doesn't allow setting a portrange, this should be added to ZNC to make it possible to use behind a firewall.
<!-- github-sync-id:5296082 -->
There's no API in POSIX for doing that.
So we'll need to try every port in the range one by one?
Anyway, DCC sucks, just don't use it.
There're better ways to give files.
There's no API in POSIX for doing that.
So we'll need to try every port in the range one by one?
Anyway, DCC sucks, just don't use it.
There're better ways to give files.
<!-- github-comment-id:6607768 -->
I don't understand your answer. A module argument specifying a port would be nice for schat, instead of the currently (most probably not open) random port.
And what is the better way for sending files via IRC ?
I don't understand your answer. A module argument specifying a port would be nice for schat, instead of the currently (most probably not open) random port.
And what is the better way for sending files via IRC ?
<!-- github-comment-id:163484801 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
schat and dccbounce doesn't allow setting a portrange, this should be added to ZNC to make it possible to use behind a firewall.
There's no API in POSIX for doing that.
So we'll need to try every port in the range one by one?
Anyway, DCC sucks, just don't use it.
There're better ways to give files.
I don't understand your answer. A module argument specifying a port would be nice for schat, instead of the currently (most probably not open) random port.
And what is the better way for sending files via IRC ?