Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
iptables has *NOTHING* to do with what ports are being listened on. All you're doing there is saying that the traffic should not be intercept. This will stop things being blocked, not make anything positive happen.
you need somethign to actually listen, i.e. an snmp server.
you appear to have not read my post. You need an snmpd server listening. iptables can't "listen" to anything, that's not what it does. Note that snmpd will not respond at all to a request that does not fit it with it's configuration (commstring etc.)
Is there any problem if I have two different versions of net-snmp on each machine? I really don't know exactly what are the versions because I don't have access to them right now, but they are different..
One snmpd.conf appears with com2sec and the other one has rocommunity things.. I really don't know what's the difference and if there's any difference, but the content is different!
versions of software in themselves don't matter. You're using a standard (very very standard) protocol and that's what matters. You need to understand what you're doing though. Mostly snmpd.conf will be configured with a commstring of "public", but it can be very different depending on what you're doing. TBH i don't know why you're asking about ports being open when you've not configured the server in the first place.