etc.ini

wm PNE 3.3 source code, running at more than vxworks6.x version.

;; $Header: /usr/cvsroot/target/src/wrn/wm/demo/snmptalk/etc.ini,v 1.1.1.1 2001/11/05 17:49:11 tneale Exp $

;; This is a sample configuration file for the Snark port of snmptalk
;; it includes sections for Attache and Envoy, if you are building
;; snmptalk for a unix platform and not using Attache you will be able
;; to ignore the Attache section.
;; All the lines beginning with ";" characters are comments.
;;
;; The lines beginning with ";;" are comments meant for humans.
;;
;; The lines beginning with a single ";" are commented-out commands.
;; Uncomment the commands you need, filling in the addresses, masks, and
;; DNS names as appropriate for your site.

[etc attache]

;; Part one: interface definitions.
;;
;; For each interface, there are several values that you can configure.
;; See the function netconfig_if() in snark/lib/netconf.c for details.
;; The most useful parameters are the IP address ("xxx-address = a.b.c.d"),
;; the netmask ("xxx-netmask = a.b.c.d"), and, for a serial line, the line
;; speed ("xxx-speed = nnnnn").  In all of these, "xxx" is the interface name.
;;
;; How interfaces are named varies depending on the environment in which
;; snark is running.  Currently, the NetBSD port of snark supports two kinds
;; of interfaces: BPF interfaces have names like "bpfxxx" where "xxx" is the
;; name of the NetBSD interface device; serial interfaces have names like
;; "sln" where "n" is the unit number of the serial device.  The SunOS 4.1.2
;; port of snark supports the NIT streams interface.  For either NetBSD or
;; SunOS, be sure you have access to the network device special file
;; (/dev/bpfnnn or /dev/nit).  Under MS-DOS, the only kind of interface
;; currently supported is the FTP Software packet driver spec (aka
;; "Clarkson" or "Crynwr" packet driver); interfaces have names of the form
;; "xxxxnnn" where "xxxx" is the short name by which the packet driver
;; identifies itself, and "nnn" is the hex interrupt number.  Last, all
;; ports of snark support the Attache loopback device, "lp0".

;; This is a host running over BPF over interface we0 on NetBSD 0.8.
;bpfwe0-address = a.b.c.d
;bpfwe0-netmask = 255.255.255.0

;; This is a host running over NIT over interface le0 on SunOS 4.1.2.
;nitle0-address = a.b.c.d
;nitle0-netmask = 255.255.255.0

;; This is a host running over SLIP over interface /dev/com0 on NetBSD 0.8.
;sl1-address = a.b.c.d
;sl1-netmask = 255.255.255.0
;sl1-speed   = 38400

;; This is an ethernet packet driver on interrupt 0x60 on MS-DOS.
;ether60-address = a.b.c.d
;ether60-netmask = 255.255.255.0

;; Attache loopback interface, any port of Snark.
;; Don't change the IP address, it's the one Berkeley seized for this purpose
;; and it's been retroactively blessed by the Number Czar.
;; Don't try to change the netmask either.
;lp0-address = 127.0.0.1
;lp0-netmask = 255.255.255.255

;; Part two: routing setup.
;;
;; There are a couple of commands you can use to configure routes
;; at boot time.  See netconfig_route() in snark/lib/netconf.c for details.
;;
;; You almost certainly want to configure a default route: this simply
;; names the router to which we should send packets that would
;; otherwise be dropped for lack of better information.  This command
;; takes one argument, the IP address of the default router.
;;
;; For more complicated static routing, you can use the route-gw
;; command.  This establishes a route to a particular network via
;; a specified router.  This command takes three arguments: the
;; destination network, the netmask for the destination network, and
;; the first-hop router to get to the destination network.  There's an
;; optional fourth argument which sets the route's priority.

;; Static route to network p.q.r.s via router w.x.y.z.
;route-gw = p.q.r.s 255.255.255.0 w.x.y.z

;; Default router, gets all traffic with no better destination.
;route-default = m.n.o.p

;; Part three: Domain Name System configuration
;;
;; If you're going to use the DNS code to translate between hostnames
;; and IP addresses, you need to configure at least snark to know
;; about at least one DNS nameserver that offers recursive DNS
;; service.  You should really configure at least two for any serious
;; use.  You may also want to configure a search path, to allow you to
;; specify just the prefix portion of a hostname and have the DNS code
;; know what you mean.  See netconfig_dns() in snark/lib/netconf.c for
;; the details of how this all works.
;;
;; To configure a name server, use the nameserver command.  At present
;; it takes one argument, the IP address of the nameserver.  This may
;; be expanded in a future version of this code.
;;
;; To configure a DNS search path, use the dns-suffix command.  It
;; takes one argument, the "printed" (human-readable) form of a DNS
;; name which will be used as a suffix.  If you use this command more
;; than once, it establishes a list of suffixes, in the specified
;; order.  WARNING: if you use this command, be sure to put the null
;; suffix (written as ".") in your search path.  If you don't,
;; fully-qualified DNS names will mysteriously fail to work.

;; DNS name servers
;nameserver = q.r.s.t
;nameserver = u.v.w.x

;; DNS search path
;dns-suffix = my.do.main
;dns-suffix = .

[etc envoy]
; the file from which to get the manager's mib
mibfile=mib.rt

; community string to use on gets
read-community=public

; community string to use on sets
write-community=private

; seconds to wait before retrying request
timeout=3

; number of times to try before giving up
retry-count=2

;;; the non volatile group, with their defaults
;; the configuration file for non volatile info
nv-config-file = snmptalk_nv.txt

;; the old configuration file 
nv-config-file-old = snmptalk_nv.old

;; the temporary configurationfile
nv-config-file-temp = snmptalk_nv.tmp

;; the read only flag, 1 = config file is read only, 0 = file is writeable
; nv-read-only = 0

;;; configuration information for SNMPv3 and defaults
;; engined id of this engine, unseparated hex string
;; if this field is filled in it is used as the engine id,
;; if it is empty the engine id should come from the nv config file
;v3_engine_id = 0000000c000000007f000001

;; the security engine id, unseparated hex string
v3_security_id = 0000000c000000007f000001

;;; the security name
v3_security_name = initialmd5

;; the context engine id, unseparated hex string
;v3_context_id = 

;; the context name
;v3_context_name =