This is done in natty now.
chuck
** Changed in: net-snmp (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in ubuntu.
https://bugs.launchpad.net/bugs/74896
Title:
Forced bind
This is done in natty now.
chuck
** Changed in: net-snmp (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/74896
Title:
Forced bind to 127.0.0.1 is
All me to add my support. I am NOT new to this. I have written snmp
apps...
This behavior goes against the man pages, the snmpconf tool, and most of
what you find on Google. At the least, we need to add to the comments
of the /etc/snmpd/snmpd.conf that /etc/default/snmpd exists.
--
You
All me to add my support. I am NOT new to this. I have written snmp
apps...
This behavior goes against the man pages, the snmpconf tool, and most of
what you find on Google. At the least, we need to add to the comments
of the /etc/snmpd/snmpd.conf that /etc/default/snmpd exists.
--
You
Peter,
You rule mate! I stumbled on exactly the same problem today and spend so much
time figuring out what was going wrong. In my case I'm using Ubuntu 9.04 and I
found that the only change I need to do is in the /etc/snmp/snmpd.conf. I added
there agentaddress local_ip_address. In this case
Peter,
You rule mate! I stumbled on exactly the same problem today and spend so much
time figuring out what was going wrong. In my case I'm using Ubuntu 9.04 and I
found that the only change I need to do is in the /etc/snmp/snmpd.conf. I added
there agentaddress local_ip_address. In this case
Thanks for this Bug Report! It also helped me solving my issue.
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because you are a member of Ubuntu
Server Team,
Thanks for this Bug Report! It also helped me solving my issue.
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the bug report. I will consider this for karmic+1
** Changed in: net-snmp (Ubuntu)
Importance: Undecided = Wishlist
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this
Thanks for the bug report. I will consider this for karmic+1
** Changed in: net-snmp (Ubuntu)
Importance: Undecided = Wishlist
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this
+1
I just spent quite some time trying to figure this out, and only now
happened upon this bug report.
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because
+1
I just spent quite some time trying to figure this out, and only now
happened upon this bug report.
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because
+1
Don't change a package's default behavior without putting notification
in an obvious, intuitive place.
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because
+1 I think. This is somewhat confusing.
Putting agentaddress 127.0.0.1 at the the top of snmpd.conf instead of
in .../defaults/.. would seem reasonable and quite helpful. However I am
not entirely familiar with the way defaults functions.
--
Forced bind to 127.0.0.1 is hardcoded' into
+1 I think. This is somewhat confusing.
Putting agentaddress 127.0.0.1 at the the top of snmpd.conf instead of
in .../defaults/.. would seem reasonable and quite helpful. However I am
not entirely familiar with the way defaults functions.
--
Forced bind to 127.0.0.1 is hardcoded' into
+1. It took me a while to figure this out. Putting the option in
snmpd.conf is a lot more intuitive.
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because you
** Changed in: net-snmp (Ubuntu)
Status: New = Confirmed
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://bugs.launchpad.net/bugs/74896
You received this bug notification because you are a member of Ubuntu
Bugs, which is
+1 I have lost many time to found this bug.
This is only for security reason to bind on loopback ?
--
Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of
option in /etc/snmp/snmpd.conf
https://launchpad.net/bugs/74896
--
ubuntu-bugs mailing list
+1 for this. I just wasted 30 minutes playing with the snmpd.conf file
trying (unsuccessfuly) to enable remote connections. Having to modify
/etc/default/snmpd is not intuitive and will not be found by the average
user. Besides, why would you want to run snmpd without allowing remote
connections?
19 matches
Mail list logo
