Thanks very much for your kindly reply.
You really understand my problem well.

I searched the Internet and used following options:

---------------------------------------------------------
 
[EMAIL PROTECTED] net-snmp-5.4]# ./configure --enable-mini-agent 
--with-mibs="IP-MIB:IF-MIB:TCP-MIB:UDP-MIB:SNMPv2-MIB:RFC1213-MIB" 
--target=arm-linux --build=i686-pc-linux-gnu --host=arm-linux --disable-scripts 
--disable-embedded-perl
--enable-static=yes --without-rpm --with-endianness=big --without-perl-modules  


And I get the  " Net-SNMP configuration summary" as follow:
---------------------------------------------------------
            Net-SNMP configuration summary:
---------------------------------------------------------
 
  SNMP Versions Supported:    1 2c 3
  Net-SNMP Version:           5.4
  Building for:               linux
  Network transport support:  Callback Unix TCP UDP
  SNMPv3 Security Modules:     usm
  Agent MIB code:             default_modules =>  snmpv3mibs mibII/snmp_mib 
mibII/system_mib mibII/sysORTable mibII/vacm_vars utilities/execute
  Embedded Perl support:      disabled
  SNMP Perl modules:          building -- not embeddable
  SNMP Python modules:        disabled
  Authentication support:     MD5
  Encryption support:
 
---------------------------------------------------------
 
So does that mean I just compiled "mibII/snmp_mib mibII/system_mib 
mibII/sysORTable mibII/vacm_vars "? And if so, how should I run the 
"./configure" to make it implement all the MIB II?




Best Regards,
Robin 
 
Tel: +86-27-8761-7326 Ext: 309
2007-01-24



发件人: Dave Shield
发送时间: 2007-01-24 17:14:33
收件人: liu.renfeng
抄送: [EMAIL PROTECTED]
主题: Re: Re: Porting net-snmp to arm platform questions

On 24/01/07, liu.renfeng  <[EMAIL PROTECTED] > wrote:

> Is there any thing I need to do to fix this problem ?

You need to simplify your snmpd.conf file!

In particular, you have *two* active access control sections:

> com2sec notConfigUser  default       public
> group   notConfigGroup v1           notConfigUser
> group   notConfigGroup v2c           notConfigUser
> view    systemview    included   .1.3.6.1.2.1.1
> view    systemview    included   .1.3.6.1.2.1.25.1.1
> access  notConfigGroup ""  any noauth  exact  systemview none none


Which gives "public" access to the system group only,
then later:


> com2sec notConfigUser   default         public
> group   notConfigGroup  v1              notConfigUser
> group   notConfigGroup  v2c             notConfigUser
> view    roview          included        .1
> view    rwview          included       system.sysContact
> view    rwview          included       system.sysName
> view    rwview          included       system.sysLocation
        [etc]
> access  notConfigGroup ""      any       noauth    exact  roview rwview none

Which tries to give public access to the whole tree.

But because you've already set up access to the "systemview",
that's what will be used instead.  The 'roview'/'rwview' settings will
be ignored

I suggest you start again with a clean config file.
Something like

     rocommunity public

would be the simplest.


> I cross compiled net-snmp with --enable-mini-agent  option

Note that this will omit most of the 'mib-2' objects from the agent.
You should still get the system group, but I'm not sure how much
else will be implemented.

Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to