On Thu, 2021-11-11 at 10:46 -0600, Steve Berg wrote: > I'm trying to setup snmpd on a newly updated F35 system. So far I > cannot get any response and port 161 remains closed. I've checked that > firewalld is not running. No iptables. There's no hosts.allow or > hosts.deny to cause this. The daemon is running. The port is > listening > according to "netstat -tulnp". > > The only warning or error I can see is "Can't find directory of RPM > packages" when I run systemctl status snmpd but that doesn't seem like > it would cause this problem. > > Anyone got an idea where I should be looking next? > > Hi, It's hard to guess here without your snmpd.conf (or parts of it). If restricted to an IP address or subnet and you try to access it from hosts which are not allowed, or provide wrong community string, it shouldn't respond if I'm not wrong. Regarding firewalls, you say firewalld is not running. Do know that recently firewalld defaults to nftables instead of iptables. (if not running not relevant here I guess)[1]. I won't go deep into thinking selinux is preventing something, but it could be as well, should be visible in the logs. I think first you should check your snmpd.conf. Regards, Branko [1] https://fedoraproject.org/wiki/Changes/firewalld_default_to_nftables _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
