Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why remove the option to listen on an interface? #26

Open
arty-hlr opened this issue May 1, 2024 · 0 comments
Open

Why remove the option to listen on an interface? #26

arty-hlr opened this issue May 1, 2024 · 0 comments

Comments

@arty-hlr
Copy link
Contributor

arty-hlr commented May 1, 2024

Hi,

A few years ago I made a pull request adding some QoL features, including being able to give an interface to listen on (#13). I didn't check again until I fixed the issue of nc listening on a random port on my fork, and then noticed that there was another commit from @CrossedWires after the PR that squashed being able to give an interface to listen on (ad0ac3a).

Why remove that option? Why can't it do both? In the end that commit also checked that the IP was bound to an an interface, so why not allow giving it an interface as well as an IP?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant