public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire2.x build hangs already on ICMPv6
Date: Sat, 01 Nov 2014 23:02:10 +0100	[thread overview]
Message-ID: <1414879330.18021.4.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1414768134.5218.2.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

Hi!

On Fri, 2014-10-31 at 16:08 +0100, Sascha Kilian wrote:
> Hi,
> 
> after some time i was not here, i am back :)
> 
> I build IPFire again from Scratch and it already hangs on Nagios 3.0.6
> 
> Log Snipp
> 
> checking for ping... /bin/ping
> checking for ping6... no
> checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s
> checking for ICMPv6 ping syntax... 

This has never caused any problems as far as I am concerned. That may
only depend on the kernel configuration of your host distribution.

We were planning to drop the nagios package any ways as long as there is
not a maintainer who takes care of it.

We also do have icinga and don't need both.

> I have sended a lfs patch for Nagios and other modules to remove IPV6
> Support from IPFire 2.x to compile IPFire 2.x success.
> 
> I rebuild my Patches and give u the github Repository from me :)

Where are they?

> If there a other Workaround for this bug?
> 
> best regards
> 
> Sascha
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

       reply	other threads:[~2014-11-01 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1414768134.5218.2.camel@localhost>
2014-11-01 22:02 ` Michael Tremer [this message]
2014-11-02 18:47   ` Sascha Kilian

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=1414879330.18021.4.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