From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Nagios Plugins Compile Hangs up
Date: Fri, 15 Aug 2014 11:48:00 +0200 [thread overview]
Message-ID: <1408096080.2114.120.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1404897504.3604.3.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Hi,
Yes, we do not support IPv6 in IPFire 2 right now. However we compile it
in if it doesn't hurt because some users set up IPv6 manually.
Could you please put this into a branch that I can merge? You may also
want to apply the same to the icinga add-on.
-Michael
On Wed, 2014-07-09 at 11:18 +0200, Sascha Kilian wrote:
> missing patch ...
>
>
>
>
> Am Mittwoch, den 09.07.2014, 11:15 +0200 schrieb Sascha Kilian:
> > Hi,
> >
> > i have a problem with the nagios-plugin compilation,
> >
> > it hangs up by checking icmpv6 ping syntax.
> >
> > i try to compile nagios without ipv6 and sends a patch. I remember that
> > IPFire-2.x comes without ipv6 support by default ?!
> >
> > best regards
> >
> > Sascha
> >
> > _______________________________________________
> > Development mailing list
> > Development(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/development
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2014-08-15 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 9:15 Sascha Kilian
2014-07-09 9:17 ` Sascha Kilian
2014-07-09 9:18 ` Sascha Kilian
2014-08-15 9:48 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1408096080.2114.120.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox