Re: Unknown token: smux

Le Lundi, 7 Avril 2008 12:22:40 +0100,
"Dave Shield" <[email protected]> a écrit :

> On 07/04/2008, lanas <[email protected]> wrote:
> >  I would like to do a simple connection test with OSPF, forgetting
> > about the license issue with OpenSSL.  Now, in order to do that, do
> > I simply have to install SSL and then perhaps given net-snmp a
> > compile option to find it ?
> 
> If you install the OpenSSL libraries (e.g. via the 'openssl-devel'
> RPM), then a simple
> 
>      configure
>      make
>      make install
> 
> should be sufficient.

Yes, it was, after installing openSSL.  But I'm still getting the same
darn communication failure error with ospfd although I have the two
smuxpeer and 'smux peer' lines in both snmpd.conf and ospfd.conf.  I
must be missing something.  At least I know that net-snmp reads the
proper config file:

read_config: Reading configuration /usr/share/snmp/snmpd.conf
read_config: /usr/share/snmp/snmpd.conf:1 examining: syslocation    "Right here"
read_config: Found a parser.  Calling it: syslocation / "Right here"
read_config: /usr/share/snmp/snmpd.conf:2 examining: syscontact     [email protected]
read_config: Found a parser.  Calling it: syscontact / [email protected]
read_config: /usr/share/snmp/snmpd.conf:3 examining: rwcommunity    private
read_config: Found a parser.  Calling it: rwcommunity / private
read_config: /usr/share/snmp/snmpd.conf:4 examining: rocommunity    public
read_config: Found a parser.  Calling it: rocommunity / public
read_config: /usr/share/snmp/snmpd.conf:5 examining: authtrapenable 0
read_config: Found a parser.  Calling it: authtrapenable / 0
/usr/share/snmp/snmpd.conf: line 5: Error: authtrapenable must be 1 or 2
read_config: /usr/share/snmp/snmpd.conf:6 examining: trapcommunity  trapcomm
read_config: Found a parser.  Calling it: trapcommunity / trapcomm
read_config: /usr/share/snmp/snmpd.conf:7 examining: trapsink       192.168.1.200
read_config: Found a parser.  Calling it: trapsink / 192.168.1.200
read_config: /usr/share/snmp/snmpd.conf:8 examining: trap2sink      192.168.1.200
read_config: Found a parser.  Calling it: trap2sink / 192.168.1.200
read_config: /usr/share/snmp/snmpd.conf:9 examining: smuxpeer .1.3.6.1.4.1.3317.1.2.5 quagga_ospfd
read_config: Found a parser.  Calling it: smuxpeer / .1.3.6.1.4.1.3317.1.2.5 quagga_ospfd
smux_conf: parsing registration for: .1.3.6.1.4.1.3317.1.2.5 quagga_ospfd
smux_conf: password is: quagga_ospfd
[...]
read_config: storing: engineBoots 4
read_config: storing: oldEngineID 0x80001f88802f324525891df847
snmpd: send_trap: Failure in sendto (Sub-id not found: enterprises -> 5 quagga_ospfd) (Network is unreachable)
snmpd: send_trap: Failure in sendto (Network is unreachable)


I presume the failure to sendto comes from the funny email address.
ospfd password seems OK.  netstat reports a listen on port 199.

One question: I noticed that without openSSL net-snmp links against a
GNU libcrypt.  And quagga does the same.  Does this mean - or for that
matter in a general sense - that it is possible to have both net-snmp
and ospfd talking to each other without SSL being in the way ?  If this
is a yes, then we can go forward with the project no matter how much
time it takes to make it working. 

Thanks.


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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