From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] New IP-address of 'ping.ipfire.org'
Date: Mon, 08 Feb 2016 09:56:41 +0100
Message-ID: <56B85849.6090405@ipfire.org>
In-Reply-To: <1454896489.2622.4.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5410269437531570396=="
List-Id: <development.lists.ipfire.org>

--===============5410269437531570396==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On 08.02.2016 02:54, Michael Tremer wrote:
> I don't know why this is hard-coded though. I don't like it.

Full ACK.

The problem seems to be the Telekom-gateway: My '217.0.117.111' doesn't
answer to ping-requests. Seems to be normal 'Telekom'-behaviour(?).

So my IPFire usually uses the IP-address of 'ping.ipfire.org', otherwise
the 'gateway'-stats are empty.

Using 'tracepath' and some modifications, we once tried to find another
solution
(https://forum.ipfire.org/viewtopic.php?f=3D6&t=3D15432&hilit=3Dtelekom+gatew=
ay).

But with my (paranoid) configuration (everything is blocked, except...)
this had the effect that 'tracepath' filled my firewall-logs with
blocked REJECT_OUTPUTs on Port 44444 or 4444X
(https://forum.ipfire.org/viewtopic.php?f=3D6&t=3D15432&hilit=3Dtelekom+gatew=
ay&start=3D15#p93043).

Best,
Matthias


--===============5410269437531570396==--