iven system
> without testing, so I'd strongly advise against using in a community
> for devices where you may or may not have 100 % control of them. It
> could even be that in the next software release you put on a
> switch/router/... it stops working, not to mention how to use thes
I'm trying to determine if a community name or userid can contain a backslash.
I've created a v2c SNMP community name called "testing\" and I cannot get it to
work with an snmpwalk (I tried with version 5.7.3 on Linux). I realize that
backslash is an escape character so I made sure to account
I downloaded the code for 5.7.2.1 again because I wanted to insert trace
statements so that I could tell you what the values were for the variables
listed in #2 from your message.
I ran configure with these options:
./configure --without-nl --with-transports=UDP TCP Unix UDPIPv6 TCPIPv6
I looked in the bug database and didn't see this listed. I've found a scenario
where snmptrap will default to port 161 for a IPv6 trap instead of port 162.
In sending a simple trap on the command line I realized that it was stripping
off the end of my IPv6 addr and using it as a port.
the trap.
Bill
On Thu, May 8, 2014 at 6:54 PM, christopher.wu wrote:
My configuration and invocation is similar. To simplify things I did some
testing using your exact examples and found that the same problem happened.
I sent the trap using your syntax and port:
snmptrap -v 2c -c
PM, christopher.wu wrote:
My configuration and invocation is similar. To simplify things I did some
testing using your exact examples and found that the same problem
happened.
I sent the trap using your syntax and port:
snmptrap -v 2c -c trappy
udp6:[fd22::
, May 1, 2014 at 2:00 PM, christopher.wu wrote:
I'm having a strange problem where my snmptrapd server will not accept v2
traps/informs if they are sent via ipv6. My snmptrapd server is version
5.7.2.1 running on Linux. The traps/informs are being sent by version 5.5.1
of snmptrap, also
I'm having a strange problem where my snmptrapd server will not accept v2
traps/informs if they are sent via ipv6. My snmptrapd server is version
5.7.2.1 running on Linux. The traps/informs are being sent by version 5.5.1 of
snmptrap, also on Linux. I tried version 5.7.2.1 of snmptrap but
I have found that when I pull the WAN Ethernet cable from the device I'm
running snmptrap on my inform retries will stop immediately. If I pull the
cable before I run snmptrap it exits immediately when I launch it. If I wait
until it has retried a few times and pull the cable it exits before
the group name. Therefore a 22 character community name made a 32
character group name, which is not allowed.
On Fri, 19 Oct 2012 13:21:05 -0700 christopher.wu wrote
For quite a while I have been under the impression that the maximum v2c
community or v3 username that I can use
christopher.wu wrote
I can add some more insight to my original question.
After the first time I bounce the PPPoE daemon snmpd (version 5.5.1) returns
two ppp0 interfaces. After a few minutes the first one will disappear. Before
that could happen I decided to restart snmpd to see what
any insight as to why this is happening, or better yet how to
stop it?
Thank you.
On Tue, 05 Jun 2012 12:02:48 -0700 christopher.wu
christopher...@zoho.com wrote
First off, apologies for what will be a lengthy post, but I wanted to
include as much
First off, apologies for what will be a lengthy post, but I wanted to include
as much background as possible to help with a potential answer.
When we were running net-snmp version 5.2.5.1 (on an embedded Linux system) we
encountered a customer that complained that their SNMP poller was
13 matches
Mail list logo
