search

lextudio / sharpsnmplib

C# SNMP Library (#SNMP) - Open source SNMP implementation for C# and .NET
https://sharpsnmp.com
MIT License
358 stars 151 forks source link

Does #SNMP Support 64 bit windows and mono? #667

Closed lextudio-support closed 1 month ago

lextudio-support commented 1 month ago

Does #SNMP directly support 64 bit OS like Windows 2008 or the 64 bit linux versions with MONO?

I have used WinSNMP in the past, but this is only a 32 bit application API.

I want to build a SNMP Agent in to my server side application that will support .NET in a 64 environment directly, so as to not have to run in a 32 sub system.

If the well known SNMP ports are in use by WinSNMP, is it as simple as connecting to a private port for my SNMP Agent?

Or does this open issues in having an SNMP agent sending traps and accepting GETS from a non standard IP PORT?

Thanks

Original Reported Date: 2010-03-30T08:24:30.107-07:00 Original CodePlex Discussion Thread ID: 207799

lextudio-support commented 1 month ago

Copied from CodePlex without authors:

Hi :SKYKING

You want to run this project in the 64 bit OS.

can you give me your contact information.

I hope talk over with you.

My email:cagy@net028.com

Original Posted Date: 2010-03-30T18:22:36.473-07:00

lextudio-support commented 1 month ago

Copied from CodePlex without authors:

My development machine for this project is running Windows 7 Ultimate x64 build. So yes, #SNMP suite is fully x64 compliant.

I cannot say much about Mono, as personally I don't have enough resources to run a open SUSE machine. But a fully C# based project like this one should run without much trouble.

I heard about the 32 bit limitation of WinSNMP, and that's why I never touch it. #SNMP is not a port of that thing to .NET. It is fully managed and created from scratch.

Currently snmpd.exe shipped in our distribution package is a reference design for SNMP agents, which runs fine on Windows x64. Please play with it and see how easy it is to run it under non standard port.

Running under non-default port (161) means whenever you want to do queries, you must explicitly specify the right port to use. That's the only issue for SNMP managers. But once you know how to configure that, it is fine. The real world issue comes from the network infrastructure. If there are network devices (firewall, routers, or gateways) blocking out non-standard ports, you cannot expect the managers talk to your agent successfully.

Regards,

Lex

Original Posted Date: 2010-03-30T22:46:26.14-07:00

lextudio-support commented 1 month ago

Marked as Answer Date: 2013-10-06T21:24:05.037-07:00