On 10/31/14 11:29, jd1008 wrote:
On 10/30/2014 08:51 PM, Ed Greshko wrote:
> netstat -tnap | grep 53 | grep -i listen
> netstat -tnap | grep 67 | grep -i listen
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 3591/dnsmasq
tcp6 0 0 :::53 :::* LISTEN 3591/dnsmasq
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1670/cupsd
tcp6 0 0 ::1:631 :::* LISTEN 1670/cupsd
So, I will be stopping and disabling dnsmasq since it's "domain" is the
whole world.
I will also disable cupsd and enable and start it only when I need to print.
dnsmasq I could understand, although some find it of use. But not cupsd as the port it is
listening on is 631 as 1670 is just part of the process id and causing the match.
But, since I don't see anything on port 67 (I was expecting dhcpd) I don't think
the ports are getting opened by the starting of the process.
So, I don't expect disabling any services to solve your situation.
Like I said, I've not used iptables in a long time. Prior to firewalld I used
"shorewall" to manage my firewall rules.
If I think of something else, I'll let you know.
--
If you can't laugh at yourself, others will gladly oblige.