Re: overwrite standard mib2/interfaces
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 19/03/2008, Masoud Fatollahy <[email protected]> wrote: > so if i used different cummonity name I will give read access to both > default context "" and "my_context" to v1 and v2c clients. If you want to grant access to both the default context ("") and your new "my_context", then you will need to configure different community strings for each one: com2sec cust1_sec 192.168.55.0/24 public1d com2sec -Cn my_context cust1_sec 192.168.55.0/24 public1m Requests using the community string "public1d" will be mapped to the default context (""). Requests using the community string "public1m" will be mapped to the new context ("my_context"). And similarly for "cust2_sec2" Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users