mrtg fails without IPv6 perl modules

[Jo Rhett]

As originally reported in this e-mail (with no response)
     https://lists.oetiker.ch/pipermail/mrtg/2006-May/031566.html

MRTG manual page says that it will disable IPv6 if the perl modules  
aren't available.  Instead, it crashes and won't run at all.

Unfortunately, some other projects are doing the Right Thing and  
enabling IPv6 if those modules are available.  So I have to install  
IPv6 perl modules to get mrtg to run, and I have to deinstall it to  
get these components to stop trying to use IPv6.

This is yet another case of everyone's favorite playtoy being so  
important that production systems are being screwed so that someone  
can play with IPv6 in their home network.  (no production big iron  
supports IPv6 queries)

--
Jo Rhett
senior geek

Silicon Valley Colocation
Support Phone: [phone]

[Jo Rhett]

On Aug 1, 2007, at 10:41 AM, Jo Rhett wrote:
> This is yet another case of everyone's favorite playtoy being so
> important that production systems are being screwed so that someone
> can play with IPv6 in their home network.  (no production big iron
> supports IPv6 queries)

I'm sorry, I was being bitter.  To be specific, can we please disable  
IPv6 by default until it is supported by at least one vendor?  And  
even then, can it allow it to be disabled completely by request?

Don't try to be smart.  Don't try to be helpful.  Allow me to disable  
it completely, please.

--
Jo Rhett
senior geek

Silicon Valley Colocation
Support Phone: [phone]

[Simon Leinen-3]

Jo Rhett writes:
> As originally reported in this e-mail (with no response)
>      https://lists.oetiker.ch/pipermail/mrtg/2006-May/031566.html

> MRTG manual page says that it will disable IPv6 if the perl modules  
> aren't available.  Instead, it crashes and won't run at all.

It shouldn't.  Which version of SNMP_Session.pm (and Windows MRTG)
are you using?
--
Simon.

[Jo Rhett]

On Aug 21, 2007, at 1:40 PM, Simon Leinen wrote:

> Jo Rhett writes:
>> As originally reported in this e-mail (with no response)
>>      https://lists.oetiker.ch/pipermail/mrtg/2006-May/031566.html
>
>> MRTG manual page says that it will disable IPv6 if the perl modules
>> aren't available.  Instead, it crashes and won't run at all.
>
> It shouldn't.  Which version of SNMP_Session.pm (and Windows MRTG)
> are you using?

Windows?  Ain't no windows here.

$ pkg_info |grep SNMP_Session
p5-SNMP_Session-1.08 A perl5 module providing rudimentary access to  
SNMPv1 and v

--
Jo Rhett
senior geek

Silicon Valley Colocation
Support Phone: [phone]

[Simon Leinen-3]

Jo Rhett writes:
> On Aug 21, 2007, at 1:40 PM, Simon Leinen wrote:
>> Jo Rhett writes:
>>> As originally reported in this e-mail (with no response)
>>> https://lists.oetiker.ch/pipermail/mrtg/2006-May/031566.html
[...]
> Windows?  Ain't no windows here.

> $ pkg_info |grep SNMP_Session
> p5-SNMP_Session-1.08 A perl5 module providing rudimentary access to
> SNMPv1 and v

Then why the funny backslashes in the error messages you quote on the
Web page you mentioned?

2006-05-25 13:45:21 -- Started mrtg with config '\configs\mrtg.cfg'
2006-05-25 13:45:21 -- Can't locate Socket6.pm in @INC (@INC contains:
c:/mrtg/bin\..\lib\mrtg2 c:/mrtg/bin C:/Perl/lib C:/Perl/site/lib .) at
c:/mrtg/bin\..\lib\mrtg2/SNMP_Session.pm line 136.
--
Simon.

[Jo Rhett]

On Aug 21, 2007, at 1:54 PM, Simon Leinen wrote:

> Jo Rhett writes:
>> On Aug 21, 2007, at 1:40 PM, Simon Leinen wrote:
>>> Jo Rhett writes:
>>>> As originally reported in this e-mail (with no response)
>>>> https://lists.oetiker.ch/pipermail/mrtg/2006-May/031566.html
> [...]
>> Windows?  Ain't no windows here.
>
>> $ pkg_info |grep SNMP_Session
>> p5-SNMP_Session-1.08 A perl5 module providing rudimentary access to
>> SNMPv1 and v
>
> Then why the funny backslashes in the error messages you quote on the
> Web page you mentioned?

Don't know, don't care.  Problem is identical on FreeBSD.  I just  
didn't want to ask without referencing a post from someone who  
observed the same thing.

--
Jo Rhett
senior geek

Silicon Valley Colocation
Support Phone: [phone]