We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I'm using wicket on an openSUSE Leap 15.4 host and recognized that the associated process wickedd-dhcp4 listens on a public port.
wickedd-dhcp4
$ sudo netstat -ltup | grep dhcp4 udp 4352 0 0.0.0.0:bootpc 0.0.0.0:* 1375/wickedd-dhcp4
The used bootpc port looks like this:
bootpc
$ grep bootpc /etc/services bootpc 68/tcp # Bootstrap Protocol Client [Bill_Croft] bootpc 68/udp # Bootstrap Protocol Client [Bill_Croft]
For security reasons I want to disable this port, but I did not found any related config option in the wicket configuration.
I tried to search for wicked disable bootpc port on the internet, which gave me no hints.
wicked disable bootpc port
I also tried to search in the wicket config
$ sudo grep -rni bootpc /etc/wicked <empty>
and in the actual network config
$ sudo grep -rni bootpc /etc/sysconfig/network/ <empty>
How to disable listening on that port or at least make it listening on localhost.
localhost
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I'm using wicket on an openSUSE Leap 15.4 host and recognized that the associated process
wickedd-dhcp4
listens on a public port.The used
bootpc
port looks like this:For security reasons I want to disable this port, but I did not found any related config option in the wicket configuration.
I tried to search for
wicked disable bootpc port
on the internet, which gave me no hints.I also tried to search in the wicket config
and in the actual network config
How to disable listening on that port or at least make it listening on
localhost
.The text was updated successfully, but these errors were encountered: