net-snmp-coders — Discussion of internal project coding (Please use this OR -users, NOT both!)

Disable IPv6 support via snmpd.conf

[Josef R. <jr...@re...>]

Hi,

I was reached with question about $SUBJ, that I am not sure, if it's possible.

Imagine this situation.

Someone have linux system, on which is disabled IPv6 support via grub file (/etc/default/grub -> ipv6.disable=1). After reboot, this will cause following error message by snmpd [1], that /proc/net/if_inet6 could not be opened. That's completely fine and makes sense. But, is there some way, how to avoid this error message to be shown, when IPv6 is disabled on the system and we don't want to rebuild the whole package just to remove -DNETSNMP_ENABLE_IPV6 from CFLAGS? 

[1] https://github.com/net-snmp/net-snmp/blob/5247f624a36be284b24a7fee941c80a8c74342d8/agent/mibgroup/ip-mib/data_access/ipaddress_linux.c#L237

Best regards

Josef Ridky
Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

iftype for bond

[Michael Wu <mic...@gm...>]

Dear Net-Snmp coders:

On the device I am working on there are bond interfaces configured and the
snmpwalk of IF-MIB::ifType (1.3.6.1.2.1.2.2.1.3) returns INTEGER:
ethernetCsmacd(6) for both physical interfaces and bond interfaces. Juniper
devices returns ieee8023adLag(161) for bond interfaces. Should net-snmp
also return ieee8023adLag(161) for bond? I am using a older net-snmp v5.8
and made changes so ieee8023adLag is returned for bond interface.

Is this behavior good to have?

Thanks,

Michael

forward traps

[Pushpa T. <pus...@gm...>]

Hi Folks ,

*Scenario:*
System-1 : IP-1.1.1.1 , It has no internet . Can access to System-2. Has
snmp-agent
System-2 : IP 2.2.2.2:  It has internet.  Has snmp-agent.
NMS-1 : IP 3.3.3.3 , It has internet. Reachable by System-2
Both System-1, system-2 is back to connected

*Requirement:  *Send snmptraps from system-1 to NMS-1
1. Is it possible via snmp ? i.e  use snmp to forward traps from system-1
to system-2 and system-2 to NMS-1
2. Using router to forward traps is only way?

Thank you,
Pushpa.T

Re: identical snmpEngineID across multiple device

[Bill F. <fe...@gm...>]

On Wed, Mar 18, 2020 at 6:30 AM Pushpa Thimmaiah <pus...@gm...>
wrote:

> If two device has same snmpEngineID then will it impact on device security?
>

Two things off the top of my head:

1. The localized keys will be the same,  meaning that if a localized key is
stolen it can be used for all devices with the same engineID;
2. A conforming SNMP manager may not be able to talk to multiple devices
with the same EngineID (because it will cache the engineBoots/engineTime,
but different agents will have different engineBoots/engineTime values).
Doing this can cause messages to be determined to be replay attacks
(because the engineID in use identifies a different system).

  Bill

identical snmpEngineID across multiple device

[Pushpa T. <pus...@gm...>]

Hi Folks,

If two device has same snmpEngineID then will it impact on device security?


Thank you,
Pushpa Thimmaiah

View Access Control not working in case of v2c traps in SNMP AGENT

[Jindal, R. <roj...@ci...>]

Hi,

I have configured the v2c traps with the community which is not created on the agents.

Ideally traps should not be sent to these type of destinations, as community does not have proper access permission.
But I am receiving the traps for these destination.

RFC 2573 Reference:

The appropriate set of variable-bindings is retrieved from local

MIB instrumentation within the relevant MIB view.  The relevant

MIB view is determined by the securityLevel, securityModel,

contextName, and securityName of the management target.  To

determine whether a particular object instance is within the

relevant MIB view, the isAccessAllowed abstract service

interface is used, in the same manner as described in the

preceding section.  If the statusInformation returned by

isAccessAllowed does not indicate accessAllowed, the

notification is not sent to the management target.



Thanks
Rohit Jindal

Re: v5.8 - Error opening specified endpoint ""

[Krishna C. <cha...@gm...>]

Can you try running without '-c <config_file>' option? If you see
using 'strace' snmpd default
starts listening on udp:161 and then reads the config file and tries
to listen to the
same udp:161 which causes issues and once you kill snmpd both of them are gone,
hence not seen in netstat.

On Mon, Mar 9, 2020 at 11:01 PM Schmoll Walter
<Wal...@an...> wrote:
>
> Hi,
>
>
>
> I’m not sure, but are UDP ports ever listening? I don’t think so.
>
> Why not try something like
>
> netstat –aupn | grep 161
>
> ?
>
>
>
> But I’m just guessing.
>
>
>
>
>
>
>
> From: Simon Chamlian [mailto:sim...@mp...]
> Sent: Monday, 9. March 2020 14:36
> To: David Moriconi (dmoricon) <dmo...@ci...>
> Cc: net-snmp-users <net...@li...>; Net-SNMP Coders <net...@li...>
> Subject: Re: v5.8 - Error opening specified endpoint ""
>
>
>
> NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR ATTACHMENTS.
>
> It is not the case!
>
>
>
> # netstat -tulpn | grep LISTEN
> tcp        0      0 0.0.0.0:36847           0.0.0.0:*               LISTEN      248/rpc.statd
> tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      238/rpcbind
> tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      246/vsftpd
> tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      232/systemd-resolve
> tcp6       0      0 :::111                  :::*                    LISTEN      238/rpcbind
> tcp6       0      0 :::80                   :::*                    LISTEN      530/httpd
> tcp6       0      0 :::22                   :::*                    LISTEN      1/init
> tcp6       0      0 :::55423                :::*                    LISTEN      248/rpc.statd
> tcp6       0      0 :::5355                 :::*                    LISTEN      232/systemd-resolve
> #
>
>
>
>
>
> # cat /etc/services | grep 161
> snmp 161/tcp # Simple Net Mgmt Protocol
> snmp 161/udp
> #
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Fri, Mar 6, 2020 at 4:30 PM David Moriconi (dmoricon) <dmo...@ci...> wrote:
>
> This error can also happen when port 161 is already in use. Make sure it is not the case.
>
>
>
> From: Simon Chamlian <sim...@mp...>
> Date: Friday, March 6, 2020 at 3:50 PM
> To: Larry Hayes <lh...@gm...>
> Cc: Net-SNMP Coders <net...@li...>, net-snmp-users <net...@li...>
> Subject: Re: v5.8 - Error opening specified endpoint ""
>
>
>
> when I run your suggestion, I get:
>
>
>
> Error opening specified endpoint "udp:0.0.0.0:161"
>
>
>
>
>
>
>
> ________________________________
>
> This message and any attachments are solely for the use of the intended recipients. They may contain privileged and/or confidential information or other information protected from disclosure. If you are not an intended recipient, you are hereby notified that you received this email in error and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system.
>
> ANDRITZ HYDRO GmbH
>
>
> Rechtsform/ Legal form: Gesellschaft mit beschränkter Haftung / Corporation
>
> Firmensitz/ Registered seat: Wien
>
> Firmenbuchgericht/ Court of registry: Handelsgericht Wien
>
> Firmenbuchnummer/ Company registration: FN 61833 g
>
> DVR: 0605077
>
> UID-Nr.: ATU14756806
>
>
> Thank You
> ________________________________
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders



-- 
Thanks,
Regards,
Chaitanya T K.

RE: v5.8 - Error opening specified endpoint ""

[Schmoll W. <Wal...@an...>]

Hi,

I’m not sure, but are UDP ports ever listening? I don’t think so.
Why not try something like
netstat –aupn | grep 161
?

But I’m just guessing.



From: Simon Chamlian [mailto:sim...@mp...]
Sent: Monday, 9. March 2020 14:36
To: David Moriconi (dmoricon) <dmo...@ci...>
Cc: net-snmp-users <net...@li...>; Net-SNMP Coders <net...@li...>
Subject: Re: v5.8 - Error opening specified endpoint ""


NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR ATTACHMENTS.
It is not the case!

# netstat -tulpn | grep LISTEN
tcp        0      0 0.0.0.0:36847<https://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2f0.0.0.0%3a36847&umid=c1dbcf7b-ca40-4e6a-a7bb-e4bc4e0fca53&auth=144056baf7302d777acad187aac74d4b9ba425e1-6fca6a6a41336a1729e1f1665cf85cf5021381a0>           0.0.0.0:*               LISTEN      248/rpc.statd
tcp        0      0 0.0.0.0:111<https://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2f0.0.0.0%3a111&umid=c1dbcf7b-ca40-4e6a-a7bb-e4bc4e0fca53&auth=144056baf7302d777acad187aac74d4b9ba425e1-cf21bedcb237835ec4f120f78e199d2d5616729d>             0.0.0.0:*               LISTEN      238/rpcbind
tcp        0      0 0.0.0.0:21<https://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2f0.0.0.0%3a21&umid=c1dbcf7b-ca40-4e6a-a7bb-e4bc4e0fca53&auth=144056baf7302d777acad187aac74d4b9ba425e1-1a75be4eafc370cdcbf4d8631655557187159b4e>              0.0.0.0:*               LISTEN      246/vsftpd
tcp        0      0 0.0.0.0:5355<https://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2f0.0.0.0%3a5355&umid=c1dbcf7b-ca40-4e6a-a7bb-e4bc4e0fca53&auth=144056baf7302d777acad187aac74d4b9ba425e1-c060aa48d138f615da1f982d4ccfc650c01a5786>            0.0.0.0:*               LISTEN      232/systemd-resolve
tcp6       0      0 :::111                  :::*                    LISTEN      238/rpcbind
tcp6       0      0 :::80                   :::*                    LISTEN      530/httpd
tcp6       0      0 :::22                   :::*                    LISTEN      1/init
tcp6       0      0 :::55423                :::*                    LISTEN      248/rpc.statd
tcp6       0      0 :::5355                 :::*                    LISTEN      232/systemd-resolve
#


# cat /etc/services | grep 161
snmp 161/tcp # Simple Net Mgmt Protocol
snmp 161/udp
#








On Fri, Mar 6, 2020 at 4:30 PM David Moriconi (dmoricon) <dmo...@ci...<mailto:dmo...@ci...>> wrote:
This error can also happen when port 161 is already in use. Make sure it is not the case.

From: Simon Chamlian <sim...@mp...<mailto:sim...@mp...>>
Date: Friday, March 6, 2020 at 3:50 PM
To: Larry Hayes <lh...@gm...<mailto:lh...@gm...>>
Cc: Net-SNMP Coders <net...@li...<mailto:net...@li...>>, net-snmp-users <net...@li...<mailto:net...@li...>>
Subject: Re: v5.8 - Error opening specified endpoint ""

when I run your suggestion, I get:

Error opening specified endpoint "udp:0.0.0.0:161<https://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2f0.0.0.0%3a161&umid=c1dbcf7b-ca40-4e6a-a7bb-e4bc4e0fca53&auth=144056baf7302d777acad187aac74d4b9ba425e1-110930f61eabd9e9eb4454a219b97c12d2846ad1>"



________________________________

This message and any attachments are solely for the use of the intended recipients. They may contain privileged and/or confidential information or other information protected from disclosure. If you are not an intended recipient, you are hereby notified that you received this email in error and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system.

ANDRITZ HYDRO GmbH


Rechtsform/ Legal form: Gesellschaft mit beschränkter Haftung / Corporation

Firmensitz/ Registered seat: Wien

Firmenbuchgericht/ Court of registry: Handelsgericht Wien

Firmenbuchnummer/ Company registration: FN 61833 g

DVR: 0605077

UID-Nr.: ATU14756806


Thank You
________________________________

Re: v5.8 - Error opening specified endpoint ""

[Simon C. <sim...@mp...>]

It is not the case!

# netstat -tulpn | grep LISTEN
tcp        0      0 0.0.0.0:36847           0.0.0.0:*               LISTEN
     248/rpc.statd
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN
     238/rpcbind
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN
     246/vsftpd
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN
     232/systemd-resolve
tcp6       0      0 :::111                  :::*                    LISTEN
     238/rpcbind
tcp6       0      0 :::80                   :::*                    LISTEN
     530/httpd
tcp6       0      0 :::22                   :::*                    LISTEN
     1/init
tcp6       0      0 :::55423                :::*                    LISTEN
     248/rpc.statd
tcp6       0      0 :::5355                 :::*                    LISTEN
     232/systemd-resolve
#


# cat /etc/services | grep 161
snmp 161/tcp # Simple Net Mgmt Protocol
snmp 161/udp
#








On Fri, Mar 6, 2020 at 4:30 PM David Moriconi (dmoricon) <dmo...@ci...>
wrote:

> This error can also happen when port 161 is already in use. Make sure it
> is not the case.
>
>
>
> *From: *Simon Chamlian <sim...@mp...>
> *Date: *Friday, March 6, 2020 at 3:50 PM
> *To: *Larry Hayes <lh...@gm...>
> *Cc: *Net-SNMP Coders <net...@li...>,
> net-snmp-users <net...@li...>
> *Subject: *Re: v5.8 - Error opening specified endpoint ""
>
>
>
> when I run your suggestion, I get:
>
>
>
> Error opening specified endpoint "udp:0.0.0.0:161"
>
>
>
>
>
>
>
> On Fri, Mar 6, 2020 at 3:13 PM Larry Hayes <lh...@gm...> wrote:
>
> Have you tried specifying the listening address, I know it's optional
> but...
>
>
>
> snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt udp:0.0.0.0:161
>
>
>
> On Thu, Mar 5, 2020 at 11:53 AM Simon Chamlian <sim...@mp...>
> wrote:
>
> Hi,
>
>
>
> When I start snmpd agent, it exists with an error message:
>
>              Error opening specified endpoint ""
>
>
>
> I start as root with:
>
>      snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt
>
>
>
>
>
> The config file my_snmpd.conf is very simple:
>
> createUser Simon   MD5 "Simon-pass"
> rwuser     Simon
> rocommunity  public
> rwcommunity  private
>
>
>
> This method used to work on other platforms but suddenly, I am getting the
> above error.
>
>
>
> I found a few mentions of this problem:
>
>
>
> https://sourceforge.net/p/net-snmp/mailman/message/36398374/
>
>
> https://stackoverflow.com/questions/50054564/net-snmp-on-start-says-error-opening-specified-endpoint-in-raspberry-pi-j
>
>
>
> but they don't work.
>
>
>
> Any hint on what to do?
>
>
>
> Thx,
>
> S
>
>
>
>
>
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
>

Re: v5.8 - Error opening specified endpoint ""

[David M. (dmoricon) <dmo...@ci...>]

This error can also happen when port 161 is already in use. Make sure it is not the case.

From: Simon Chamlian <sim...@mp...>
Date: Friday, March 6, 2020 at 3:50 PM
To: Larry Hayes <lh...@gm...>
Cc: Net-SNMP Coders <net...@li...>, net-snmp-users <net...@li...>
Subject: Re: v5.8 - Error opening specified endpoint ""

when I run your suggestion, I get:

Error opening specified endpoint "udp:0.0.0.0:161<http://0.0.0.0:161>"



On Fri, Mar 6, 2020 at 3:13 PM Larry Hayes <lh...@gm...<mailto:lh...@gm...>> wrote:
Have you tried specifying the listening address, I know it's optional but...

snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt udp:0.0.0.0:161<http://0.0.0.0:161>

On Thu, Mar 5, 2020 at 11:53 AM Simon Chamlian <sim...@mp...<mailto:sim...@mp...>> wrote:
Hi,

When I start snmpd agent, it exists with an error message:
             Error opening specified endpoint ""

I start as root with:
     snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt


The config file my_snmpd.conf is very simple:
createUser Simon   MD5 "Simon-pass"
rwuser     Simon
rocommunity  public
rwcommunity  private

This method used to work on other platforms but suddenly, I am getting the above error.

I found a few mentions of this problem:

https://sourceforge.net/p/net-snmp/mailman/message/36398374/
https://stackoverflow.com/questions/50054564/net-snmp-on-start-says-error-opening-specified-endpoint-in-raspberry-pi-j

but they don't work.

Any hint on what to do?

Thx,
S


_______________________________________________
Net-snmp-coders mailing list
Net...@li...<mailto:Net...@li...>
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Re: v5.8 - Error opening specified endpoint ""

[Simon C. <sim...@mp...>]

when I run your suggestion, I get:

Error opening specified endpoint "udp:0.0.0.0:161"



On Fri, Mar 6, 2020 at 3:13 PM Larry Hayes <lh...@gm...> wrote:

> Have you tried specifying the listening address, I know it's optional
> but...
>
> snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt udp:0.0.0.0:161
>
> On Thu, Mar 5, 2020 at 11:53 AM Simon Chamlian <sim...@mp...>
> wrote:
>
>> Hi,
>>
>> When I start snmpd agent, it exists with an error message:
>>              Error opening specified endpoint ""
>>
>> I start as root with:
>>      snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt
>>
>>
>> The config file my_snmpd.conf is very simple:
>> createUser Simon   MD5 "Simon-pass"
>> rwuser     Simon
>> rocommunity  public
>> rwcommunity  private
>>
>> This method used to work on other platforms but suddenly, I am getting
>> the above error.
>>
>> I found a few mentions of this problem:
>>
>> https://sourceforge.net/p/net-snmp/mailman/message/36398374/
>>
>> https://stackoverflow.com/questions/50054564/net-snmp-on-start-says-error-opening-specified-endpoint-in-raspberry-pi-j
>>
>> but they don't work.
>>
>> Any hint on what to do?
>>
>> Thx,
>> S
>>
>>
>> _______________________________________________
>> Net-snmp-coders mailing list
>> Net...@li...
>> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>
>

Re: v5.8 - Error opening specified endpoint ""

[Larry H. <lh...@gm...>]

Have you tried specifying the listening address, I know it's optional but...

snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt udp:0.0.0.0:161

On Thu, Mar 5, 2020 at 11:53 AM Simon Chamlian <sim...@mp...>
wrote:

> Hi,
>
> When I start snmpd agent, it exists with an error message:
>              Error opening specified endpoint ""
>
> I start as root with:
>      snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt
>
>
> The config file my_snmpd.conf is very simple:
> createUser Simon   MD5 "Simon-pass"
> rwuser     Simon
> rocommunity  public
> rwcommunity  private
>
> This method used to work on other platforms but suddenly, I am getting the
> above error.
>
> I found a few mentions of this problem:
>
> https://sourceforge.net/p/net-snmp/mailman/message/36398374/
>
> https://stackoverflow.com/questions/50054564/net-snmp-on-start-says-error-opening-specified-endpoint-in-raspberry-pi-j
>
> but they don't work.
>
> Any hint on what to do?
>
> Thx,
> S
>
>
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

Snmpd not answering if an unknown context is used in query from client

[daniele <dan...@gm...>]

Hello everybody,

I'm using NET-SNMP 5.7.3 with SSL support enabled and I can properly
configure the daemon to run SNMPV3 with authNoPriv users.
At run time my subagent will register OIDs with a configurable context name.
Everything is working perfectly.

However I can see a minor but unexpected behavior when querying the daemon
from a client with a context unknown to the daemon: the daemon is not
answering at all and I must wait for the client side timeout to expire.

Is this behavior expected from your side or should I open a bug? I was
instead waiting for a reply like "SNMP_NOSUCHOBJECT" or similar...

I posted the same request also on net-snmp-users here:
https://sourceforge.net/p/net-snmp/mailman/message/36932085/

Thanks

v5.8 - Error opening specified endpoint ""

[Simon C. <sim...@mp...>]

Hi,

When I start snmpd agent, it exists with an error message:
             Error opening specified endpoint ""

I start as root with:
     snmpd  -c /home/user/my_snmpd.conf  -Lf /tmp/snmpd_log.txt


The config file my_snmpd.conf is very simple:
createUser Simon   MD5 "Simon-pass"
rwuser     Simon
rocommunity  public
rwcommunity  private

This method used to work on other platforms but suddenly, I am getting the
above error.

I found a few mentions of this problem:

https://sourceforge.net/p/net-snmp/mailman/message/36398374/
https://stackoverflow.com/questions/50054564/net-snmp-on-start-says-error-opening-specified-endpoint-in-raspberry-pi-j

but they don't work.

Any hint on what to do?

Thx,
S

Handler signature parameters meaning

[Philippe D. <phd...@gm...>]

Hello all,

I've a (stupid) question linked to the Handler signature. When using mib2c,
the Handler is created with the following signature:

MyHandler(netsnmp_mib_handler *handler,
        netsnmp_handler_registration *reginfo,
        netsnmp_agent_request_info *reqinfo,
        netsnmp_request_info *requests)

In all the examples, I've read only the 3rd and 4th arguments is used.
According to my understanding, the 3rd one is linked to the agent request
information (set or get) and the 4th one is linked to the value.

Regarding the doxygen man page, I've found the following signature which is
quite closed:

int netsnmp_call_handler
( netsnmp_mib_handler
<http://www.net-snmp.org/dev/agent/structnetsnmp__mib__handler__s.html> *
*next_handler*,
netsnmp_handler_registration
<http://www.net-snmp.org/dev/agent/structnetsnmp__handler__registration__s.html>
 *  *reginfo*,
netsnmp_agent_request_info
<http://www.net-snmp.org/dev/agent/structnetsnmp__agent__request__info__s.html>
 *  *reqinfo*,
netsnmp_request_info
<http://www.net-snmp.org/dev/agent/structnetsnmp__request__info__s.html> *
*requests*
)

So, what is the meaning of the 1st and 2nd argument? I've assumed that the
1st one is linked to the registration process but without any certitude.

Thanks by advance for your help.
-- 
B/R
Phil

Re: How to delink tables in IP MIB

[Aferjes B. R. <are...@gm...>]

Hi Wes,

Thanks for the help. It worked. Again Thanks for the help.

On Wed, 19 Feb, 2020, 4:52 am Wes Hardaker, <har...@us...>
wrote:

> Aferjes Blesswin Redeemson <are...@gm...> writes:
>
> > I'm implementing IP MIB for my project using NetSNMP. I don't want to
> > initailize "ipRoutingDiscards and ipNetToPhysicalTable".
>
> ipRoutingDiscards is a column implemented within the
> ./agent/mibgroup/mibII/ip.c file; you'd need to go edit that file to
> remove its support.
>
> (you could also make use of the 'override' token in snmpd.conf to alter
> it at run time too)
>
> Net-SNMP doesn't come with ipNetToPhysicalTable, so if you're using our
> stock version it shouldn't even have that table compiled in.  If you
> have it as an additional module from someone else, you can use
> configure's --with-out-mib-modules flag to remove it from being included
> in the agent, if you know the module name (grep is your friend).
> --
> Wes Hardaker
> Please mail all replies to net...@li...
>

Re: Get interface IPV6 addresses

[Michael Wu <mic...@gm...>]

>What OS is this? Is this your own compilation from the release tar ball
>or the versions provided by your distribution?

It is Debian Linux and my own compilation from older 5.8 last year (Tue Feb
26 commit 21260fdd60c172839f997fb6f888a6e21c6825eb)

>  I do, with the CentOS 7 provided version (5.7.2), and with a somewhat
>recent installation of the 5-8-patches branch.
 Actually I do too :) I was mistaken when I stated that I did not see
ipAddressPrefix.
So If I want to get "interface name" to "ipv6 address" mapping, I need to
get
1. ifIndex = 2  from
IP-MIB::ipAddressIfIndex.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00:00:00:00:01"
= INTEGER: 2
2. Then get ifName from ifIndex

Niels, Thank you for your help,

Michael

On Thu, Feb 27, 2020 at 1:31 PM Niels Baggesen <ni...@ba...> wrote:

> Den 27-02-2020 kl. 18:40 skrev Michael Wu:
> > Dear Net-Snmp coders:
> >
> > I am using net-snmp v5.8 with ipv6 enabled. Trying to get interface's
> > ipv6 addresses. I tried a couple of oids but could not figure out how to
> > map the ifindex to the ipv6 address assigned to the interfaces. All
> > interfaces have both ipv4 and ipv6 addresses assigned.
>
> What OS is this? Is this your own compilation from the release tar ball
> or the versions provided by your distribution?


> > 1. The ipv6AddrPrefixTable documented in
> > http://www.net-snmp.org/docs/mibs/ipv6MIB.html
> > <http://www.net-snmp.org/docs/mibs/ipv6MIB.html> was not available:
> >
> > snmpwalk -v 2c -c public x.x.x.x .1.3.6.1.2.1.55.1.7
> > IPV6-MIB::ipv6AddrPrefixTable = No Such Object available on this agent
> > at this OID
>
> No, the IPV6-MIB has been deprecated in favor of the augmented IP-MIB
> (as used below)
>
> > 2. ipAddressTable (1.3.6.1.2.1.4.34) has entries of ipv6 prefix:
> >
> > snmpwalk -v 2c -c public x.x.x.x .1.3.6.1.2.1.4.34
> > IP-MIB::ipAddressIfIndex.ipv4."243.0.3.129" = INTEGER: 230
> >
> IP-MIB::ipAddressIfIndex.ipv6."fe:80:00:00:00:00:00:00:02:e0:ec:ff:fe:e1:5e:44"
>
> > = INTEGER: 230
> > IP-MIB::ipAddressType.ipv4."243.0.3.129" = INTEGER: unicast(1)
> >
> IP-MIB::ipAddressType.ipv6."fe:80:00:00:00:00:00:00:02:e0:ec:ff:fe:e1:5e:44"
>
> > = INTEGER: unicast(1)
> > ...
> > But I don't see ipAddressPrefix ( .1.3.6.1.2.1.4.34.5) from the output.
>
> I do, with the CentOS 7 provided version (5.7.2), and with a somewhat
> recent installation of the 5-8-patches branch.
>
> IP-MIB::ipAddressPrefix.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01"
>
> = OID:
> IP-MIB::ipAddressPrefixOrigin.1.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:
>                                           00:00:00:01".128
> IP-MIB::ipAddressPrefix.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00:00:00:00:01"
>
> =                                           OID:
> IP-MIB::ipAddressPrefixOrigin.2.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00:
>                                           00:00:00:00".64
> IP-MIB::ipAddressPrefix.ipv6."fe:80:00:00:00:00:00:00:de:98:3e:20:92:51:bd:11"
>
> =                                           OID:
> IP-MIB::ipAddressPrefixOrigin.2.ipv6."fe:80:00:00:00:00:00:00:00:00:00:00:
>                                           00:00:00:00".64
>
>
> > 3. Also tried ipAdEntIfIndex ( 1.3.6.1.2.1.4.20.1.2)
> >
> > snmpwalk -v 2c -c public x.x.x.x 1.3.6.1.2.1.4.20.1.2
> > ...
> > IP-MIB::ipAdEntIfIndex.243.0.3.129 = INTEGER: 230
> > ...
> > But it only has ipv4 addresses.
>
> Yes, this is a IPv4 only table.
>
> > What is the right approach to get the ipv6 address from the interface?
>
> I would look at
> IP-MIB::ipAddressIfIndex.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01"
>
> = INTEGER: 1
> IP-MIB::ipAddressIfIndex.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00:00:00:00:01"
>
> = INTEGER: 2
>
> /Niels
>
> PS: Sorry about the line wrap of these extreme OIDs :-(
>
> --
> <https://www.e-julemaerket.dk/?f78133c1-061f-4320-b728-d1dbbf6996c7>
>
>
>
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

Re: Get interface IPV6 addresses

[Niels B. <ni...@ba...>]

Den 27-02-2020 kl. 18:40 skrev Michael Wu:
> Dear Net-Snmp coders:
> 
> I am using net-snmp v5.8 with ipv6 enabled. Trying to get interface's 
> ipv6 addresses. I tried a couple of oids but could not figure out how to 
> map the ifindex to the ipv6 address assigned to the interfaces. All 
> interfaces have both ipv4 and ipv6 addresses assigned.

What OS is this? Is this your own compilation from the release tar ball 
or the versions provided by your distribution?

> 1. The ipv6AddrPrefixTable documented in 
> http://www.net-snmp.org/docs/mibs/ipv6MIB.html 
> <http://www.net-snmp.org/docs/mibs/ipv6MIB.html> was not available:
> 
> snmpwalk -v 2c -c public x.x.x.x .1.3.6.1.2.1.55.1.7
> IPV6-MIB::ipv6AddrPrefixTable = No Such Object available on this agent 
> at this OID

No, the IPV6-MIB has been deprecated in favor of the augmented IP-MIB 
(as used below)

> 2. ipAddressTable (1.3.6.1.2.1.4.34) has entries of ipv6 prefix:
> 
> snmpwalk -v 2c -c public x.x.x.x .1.3.6.1.2.1.4.34
> IP-MIB::ipAddressIfIndex.ipv4."243.0.3.129" = INTEGER: 230
> IP-MIB::ipAddressIfIndex.ipv6."fe:80:00:00:00:00:00:00:02:e0:ec:ff:fe:e1:5e:44" 
> = INTEGER: 230
> IP-MIB::ipAddressType.ipv4."243.0.3.129" = INTEGER: unicast(1)
> IP-MIB::ipAddressType.ipv6."fe:80:00:00:00:00:00:00:02:e0:ec:ff:fe:e1:5e:44" 
> = INTEGER: unicast(1)
> ...
> But I don't see ipAddressPrefix ( .1.3.6.1.2.1.4.34.5) from the output.

I do, with the CentOS 7 provided version (5.7.2), and with a somewhat 
recent installation of the 5-8-patches branch.

IP-MIB::ipAddressPrefix.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01" 
= OID: 
IP-MIB::ipAddressPrefixOrigin.1.ipv6."00:00:00:00:00:00:00:00:00:00:00:00: 
                                          00:00:00:01".128
IP-MIB::ipAddressPrefix.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00:00:00:00:01" 
=                                           OID: 
IP-MIB::ipAddressPrefixOrigin.2.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00: 
                                          00:00:00:00".64
IP-MIB::ipAddressPrefix.ipv6."fe:80:00:00:00:00:00:00:de:98:3e:20:92:51:bd:11" 
=                                           OID: 
IP-MIB::ipAddressPrefixOrigin.2.ipv6."fe:80:00:00:00:00:00:00:00:00:00:00: 
                                          00:00:00:00".64


> 3. Also tried ipAdEntIfIndex ( 1.3.6.1.2.1.4.20.1.2)
> 
> snmpwalk -v 2c -c public x.x.x.x 1.3.6.1.2.1.4.20.1.2
> ...
> IP-MIB::ipAdEntIfIndex.243.0.3.129 = INTEGER: 230
> ...
> But it only has ipv4 addresses.

Yes, this is a IPv4 only table.

> What is the right approach to get the ipv6 address from the interface?

I would look at
IP-MIB::ipAddressIfIndex.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01" 
= INTEGER: 1
IP-MIB::ipAddressIfIndex.ipv6."20:01:04:70:df:9a:00:00:00:00:00:00:00:00:00:01" 
= INTEGER: 2

/Niels

PS: Sorry about the line wrap of these extreme OIDs :-(

-- 
<https://www.e-julemaerket.dk/?f78133c1-061f-4320-b728-d1dbbf6996c7>

Get interface IPV6 addresses

[Michael Wu <mic...@gm...>]

Dear Net-Snmp coders:

I am using net-snmp v5.8 with ipv6 enabled. Trying to get interface's ipv6
addresses. I tried a couple of oids but could not figure out how to map the
ifindex to the ipv6 address assigned to the interfaces. All interfaces have
both ipv4 and ipv6 addresses assigned.

1. The ipv6AddrPrefixTable documented in
http://www.net-snmp.org/docs/mibs/ipv6MIB.html was not available:

snmpwalk -v 2c -c public x.x.x.x .1.3.6.1.2.1.55.1.7
IPV6-MIB::ipv6AddrPrefixTable = No Such Object available on this agent at
this OID

2. ipAddressTable (1.3.6.1.2.1.4.34) has entries of ipv6 prefix:

snmpwalk -v 2c -c public x.x.x.x .1.3.6.1.2.1.4.34
IP-MIB::ipAddressIfIndex.ipv4."243.0.3.129" = INTEGER: 230
IP-MIB::ipAddressIfIndex.ipv6."fe:80:00:00:00:00:00:00:02:e0:ec:ff:fe:e1:5e:44"
= INTEGER: 230
IP-MIB::ipAddressType.ipv4."243.0.3.129" = INTEGER: unicast(1)
IP-MIB::ipAddressType.ipv6."fe:80:00:00:00:00:00:00:02:e0:ec:ff:fe:e1:5e:44"
= INTEGER: unicast(1)
...
But I don't see ipAddressPrefix ( .1.3.6.1.2.1.4.34.5) from the output.

3. Also tried ipAdEntIfIndex ( 1.3.6.1.2.1.4.20.1.2)

snmpwalk -v 2c -c public x.x.x.x 1.3.6.1.2.1.4.20.1.2
...
IP-MIB::ipAdEntIfIndex.243.0.3.129 = INTEGER: 230
...
But it only has ipv4 addresses.

What is the right approach to get the ipv6 address from the interface?

Thanks and best regards,

Michael

Re: net-snmp-5.8.1.pre2 released

[Bart V. A. <bva...@ac...>]

On 2020-02-26 04:04, Wes Hardaker wrote:
> Bart Van Assche <bva...@ac...> writes:
>> One change seems to be missing from this list, namely commit
>> 9a2753282c6a ("new autoconf"). That commit regenerated the configure
>> script with autoconf v2.69. Has it been considered to also switch to
>> newer versions of automake (v1.11 -> v1.16) and libtool (v2.4 ->
>> v2.4.6)? I have to reapply several patches manually after every
>> autoreconf run to fix bugs in the old versions of these tools. One of
>> these patches has been documented on
>> http://www.net-snmp.org/wiki/index.php/Build_System.
> 
> Yes, the packaging mechanism does rebuild autoconf based on the last
> agreed version that we proposed using.  Which was 2.69.
> 
> Maybe we should discuss what the minimum tools available should be for
> new releases (again)?

Hi Wes,

How about upgrading both libtool and automake to the latest available
versions? libtool v2.4.6 + automake 1.11.6 support FreeBSD 10 and MinGW
but the versions endorsed for the v5.8 branch not.

Bart.

Re: Appreciation for the Net-SNMP Project

[Wes H. <har...@us...>]

Shea Newton <sh...@ac...> writes:

> We directed the donation today to the email address you provided, you
> should see it soon. Please do let me know if there are any issues.  

Thanks Shea,

I got the donation.  I think it's time to start a sticker design contest :-)
-- 
Wes Hardaker
Please mail all replies to net...@li...

Re: net-snmp-5.8.1.pre2 released

[Wes H. <har...@us...>]

Bart Van Assche <bva...@ac...> writes:

> One change seems to be missing from this list, namely commit
> 9a2753282c6a ("new autoconf"). That commit regenerated the configure
> script with autoconf v2.69. Has it been considered to also switch to
> newer versions of automake (v1.11 -> v1.16) and libtool (v2.4 ->
> v2.4.6)? I have to reapply several patches manually after every
> autoreconf run to fix bugs in the old versions of these tools. One of
> these patches has been documented on
> http://www.net-snmp.org/wiki/index.php/Build_System.

Yes, the packaging mechanism does rebuild autoconf based on the last
agreed version that we proposed using.  Which was 2.69.

Maybe we should discuss what the minimum tools available should be for
new releases (again)?
-- 
Wes Hardaker
Please mail all replies to net...@li...

Re: Issue linked to .0 at the end of OID

[Wes H. <har...@us...>]

Philippe Denis <phd...@gm...> writes:

> I’ve a strange behavior when using snmpget command. When I used the
> OID of one of my objects correctly registered, the sub agent replied
> correctly but when I put .0 at the end of the OID, It doesn’t
> reply. For sake of clarity, it’s a scalar object.
> 
> Have you already experienced this behavior ?
> 
> What is the meaning of this .0 ? Is it mandatory ?

Scalar objects are supposed to have a .0 at the end, and is functionally
their identifier.  Since there is only one, it has just a single
identifier (.0).  Tables, on the other hand, have more identifiers under
their column registration point.

So if your implementation of a scalar should only respond if the .0 is
present in the oid beyond your registration point.
-- 
Wes Hardaker
Please mail all replies to net...@li...

Issue linked to .0 at the end of OID

[Philippe D. <phd...@gm...>]

Hello all,

I’ve a strange behavior when using snmpget command. When I used the OID of one of my objects correctly registered, the sub agent replied correctly but when I put .0 at the end of the OID, It doesn’t reply. For sake of clarity, it’s a scalar object.

Have you already experienced this behavior ?

What is the meaning of this .0 ? Is it mandatory ?

B/R 
Philippe

Re: net-snmp-5.8.1.pre2 released

[Bart V. A. <bva...@ac...>]

On 2020-02-20 14:58, Wes Hardaker via Net-snmp-coders wrote:
> 
> After far far too long of a delay, I've just pushed net-snmp-5.8.1.pre2
> to the download site:
> 
>     https://www.net-snmp.org/download.html
> 
> Please give it a whirl, and report issues and fixes to our github site
> at:
> 
>     https://github.com/net-snmp/net-snmp
> 
> Current changes to 5.8.1.pre2 total:
> 
> *5.8.1* [ ... ]

Hi Wes,

One change seems to be missing from this list, namely commit
9a2753282c6a ("new autoconf"). That commit regenerated the configure
script with autoconf v2.69. Has it been considered to also switch to
newer versions of automake (v1.11 -> v1.16) and libtool (v2.4 ->
v2.4.6)? I have to reapply several patches manually after every
autoreconf run to fix bugs in the old versions of these tools. One of
these patches has been documented on
http://www.net-snmp.org/wiki/index.php/Build_System.

Thanks,

Bart.