I don't have any other suggestions here, other than trying a rebuild from
scratch to make sure you have a self-consistent tree. I'm not familiar with
cross compiling. rocommunity6 works for me when I specify it in my
natively-compiled agent.
Bill
On Thu, Jan 25, 2018 at 9:29 AM, Simon Chamlian
SNMP Versions Supported:1 2c 3
Building for: linux
Net-SNMP Version: 5.7.3
Network transport support: Callback Unix Alias TCPIPv6 UDPIPv6 UDP TCP
IPv6Base SocketBase TCPBase UDPBase UDPIPv4Base IPv4Base
SNMPv3 Security Modules: usm
*** MIB Module warning
Can you paste the end of your configuration run, where it summarizes the
results? The “rocommunity6” configuration directive will be available if
that configuration summary includes “UDPIPv6” in the “Network transport
support:” list - e.g.,
-
On Wed, Jan 17, 2018 at 10:58:40AM -0500, Simon Chamlian wrote:
> but these tokens are not recognized:
> ./snmpd.conf: line 12: Warning: Unknown token: rocommunity6.
> ./snmpd.conf: line 13: Warning: Unknown token: rwcommunity6.
This means that snmpd did not understand you config, and acco
Seems like --enable-ipv6 is not enough to make SNMPv2 work with IPv6 since:
# ./snmpd -H 2>&1 | grep community
trapsink host [community] [port]
trap2sinkhost [community] [port]
informsink host [community] [port]
trapcommunity
I am sure about the compilation with --enable-ipv6 because it works with
snmp v3
# snmpget -v 3 -u Admin -a MD5 -A Admin-00 -l authNoPriv 172.27.42.15
MPBC-1RU-MIB::mpbc1RUNEID.0 -Oqv
"VERSA_199"
# snmpget -v 3 -u Admin -a MD5 -A Admin-00 -l authNoPriv
[fe80::6eff:beff:fe02:d0%eth0] MPBC-1RU-MIB:
n Wed, Jan 17, 2018 at 10:58:40AM -0500, Simon Chamlian wrote:
> but these tokens are not recognized:
> ./snmpd.conf: line 12: Warning: Unknown token: rocommunity6.
> ./snmpd.conf: line 13: Warning: Unknown token: rwcommunity6.
This means that snmpd did not understand you config, and accor
Hi Simon,
Read
https://serverfault.com/questions/242013/difference-between-link-local-and-global-link-addresses-in-isatap/242014
Regards
Anders
Den ons 24 jan. 2018 02:13Simon Chamlian skrev:
> Since there is no reply, let me ask a different question:
>
> Was anyone able to use IPv6 with SNMPv
Since there is no reply, let me ask a different question:
Was anyone able to use IPv6 with SNMPv2?
IPv4
# snmpget -v 2c -c public 172.27.42.199 MPBC-1RU-MIB::mpbc1RUNEID.0
MPBC-1RU-MIB::mpbc1RUNEID.0 = STRING: "VERSA_199"
works fine
IPv6
# snmpget -v 2c -c public [fe80::6eff:beff:fe
I got the Ipv6 working finally with SNMP v3. I had to add:
agentaddress udp:161
agentaddress udp6:161
in snmpd.conf.
Now the problem is SNMPv2 that does not work with IPv6.
I added:
rocommunity6 public
rwcommunity6 private
but these tokens are not recognized:
./snmpd.conf
Simon,
Can you try with global addresses? I wouldn't be horribly surprised if
scope zones were not supported properly. (Global v6 addresses have worked
for me in net-snmp for years.)
Bill
On Mon, Jan 15, 2018 at 2:37 PM, Simon Chamlian
wrote:
> Hi,
>
> Just recompiled the agent by enabling
Hi,
Just recompiled the agent by enabling IPv6 ( --enable-ipv6).
The agent is working fine but don't seem to be able to use IPv6.
Example:
# snmpget -v 3 -u Admin -a MD5 -A Admin-00 -l authNoPriv 172.27.42.199
MPBC-1RU-MIB::mpbc1RUNEID.0 -Oqv
"TestNew"
works fine.
In Ipv6:
# snmpget -v 3 -
12 matches
Mail list logo
