Hi Niels,
thank you for help.
Your patch was not complete, but I think, my version is.
All test are running as before, but this part is not tested!
The error occurs only on little endian machines.
But now, it should work on either endian.
IMHO, there should be a test for the snmpTargetAddrTabl
Den 07-10-2013 19:08, Claus Klein skrev:
> What is the Key to get help on this List?
Patience :-)
> And what is the reason to ignore my posts?
As you probably know, this project is run entirely by people who do it
voluntarily and in their spare time. None of the project developers are
paid for
Den 03-10-2013 11:37, Claus Klein skrev:
what is the reason for different byteorder of port configuration
with snmpUDPDomain and transportDomainUdpIpv6 in snmpTargetAddrTable?
This is a bug, not a feature
It is not clear to me, which port number is really used with this
configuration.
snmpd
What is the Key to get help on this List?
And what is the reason to ignore my posts?
The ipv6 trap Receiver configutration use the wrong Port Nummer if configured
via mib.
With regards
Claus
On 03.10.2013, at 11:37, Claus Klein wrote:
> Hi,
>
> what is the reason for different byteorder of p
Hi,
what is the reason for different byteorder of port configuration with
snmpUDPDomain and transportDomainUdpIpv6 in snmpTargetAddrTable?
with this configuration:
trapsess -v 3 -e 0x80001f88017f01 -u trapuser -l noAuthNoPriv
udp:127.0.0.1:4660
trapsess -v 3 -e 0x80001f88017f01 -u tra
