Re: Unknown token: smux

2008-04-04 Thread Thomas Anders
lanas wrote: > [M1> ./snmpd -H 2>&1 | grep smux > /usr/local/share/snmp/snmpd.conf: line 14: Warning: Unknown token: smux. "smux" isn't a supported config token for SMUX, only "smuxpeer" and "smuxsocket" are. These don't appear in your output which suggests that you *don't* have SMUX support com

Re: Unknown token: smux

2008-04-04 Thread lanas
Le Vendredi, 04 Avril 2008 11:02:41 +0200, Thomas Anders <[EMAIL PROTECTED]> a écrit : > lanas wrote: > > [M1> ./snmpd -H 2>&1 | grep smux > > /usr/local/share/snmp/snmpd.conf: line 14: Warning: Unknown token: > > smux. > > "smux" isn't a supported config token for SMUX, only "smuxpeer" and > "sm

Re: Unknown token: smux

2008-04-05 Thread Thomas Anders
lanas wrote: > And then I chdir to /usr/local/sbin/ and: > > ./snmpd -Dsmux,smux_init,smux_conf > > [M1> /usr/local/share/snmp/snmpd.conf: line 14: Warning: Unknown token: smux. I cannot reproduce this over here. Are you sure you don't have any other net-snmp installation on your system? What's

Re: Unknown token: smux

2008-04-06 Thread lanas
Le Samedi, 05 Avril 2008 15:56:36 +0200, Thomas Anders <[EMAIL PROTECTED]> a écrit : > lanas wrote: > > And then I chdir to /usr/local/sbin/ and: > > ./snmpd -Dsmux,smux_init,smux_conf > > > > [M1> /usr/local/share/snmp/snmpd.conf: line 14: Warning: Unknown > > token: smux. > > I cannot reprodu

Re: Unknown token: smux

2008-04-06 Thread Thomas Anders
lanas wrote: > I don't have this system now. But I've rebuild on a quite similar > system (Fedora 8 x86) this one running inside VmWare. This time, > instead of using the defalt /usr/local/ prefix I've specified /usr. > And this time I do not see the warning as above. > > I'm still trying to mak

Re: Unknown token: smux

2008-04-07 Thread Dave Shield
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 instal

Re: Unknown token: smux

2008-04-07 Thread lanas
Le Lundi, 07 Avril 2008 07:26:08 +0200, Thomas Anders <[EMAIL PROTECTED]> a écrit : > lanas wrote: >> >> I'm still trying to make OSPF talk with net-snmp, though. > Could you try it on the VM system, please? It gives the following: -bash-3.2# cd /usr/sbin -bash-3.2# ldd snmpd libnetsnm

Re: Unknown token: smux

2008-04-07 Thread Dave Shield
On 04/04/2008, lanas <[EMAIL PROTECTED]> wrote: > [M1> cat snmpd.conf [snip] > smuxpeer .1.3.6.1.4.1.3317.1.2.5 quagga_ospfd > [M1> ./snmpd -Dsmux,smux_init,smux_conf >line 14: Warning: Unknown token: smux. The thing that strikes me about this is that your snmpd.conf file contains

Re: Unknown token: smux

2008-04-07 Thread lanas
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 i

Re: Unknown token: smux

2008-04-08 Thread Dave Shield
On 08/04/2008, lanas <[EMAIL PROTECTED]> wrote: > 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 ot

RE: Unknown token: smux

2008-04-08 Thread Mike Ayers
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of lanas > Sent: Monday, April 07, 2008 4:28 PM > 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 bo

Re: Unknown token: smux

2008-04-08 Thread lanas
Le Mardi, 8 Avril 2008 12:00:33 -0700, "Mike Ayers" <[EMAIL PROTECTED]> a écrit : > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of lanas > > Sent: Monday, April 07, 2008 4:28 PM > > > Yes, it was, after installing openSSL. But I'm still getting the > > same darn co