New IP-address of 'ping.ipfire.org'
Message ID | 1454849132-5872-1-git-send-email-matthias.fischer@ipfire.org |
---|---|
State | Accepted |
Commit | c1bf984e05ff9c523121d459cd58154d3d37a34a |
Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (hedwig.ipfire.org [172.28.1.200]) by web02.ipfire.org (Postfix) with ESMTP id 7355661BFD for <patchwork@ipfire.org>; Sun, 7 Feb 2016 13:45:40 +0100 (CET) Received: from mail01.ipfire.org (localhost [IPv6:::1]) by mail01.ipfire.org (Postfix) with ESMTP id B93BB9C5; Sun, 7 Feb 2016 13:45:39 +0100 (CET) Received: from Devel.localdomain (p578D1939.dip0.t-ipconnect.de [87.141.25.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id A14199B0 for <development@lists.ipfire.org>; Sun, 7 Feb 2016 13:45:36 +0100 (CET) From: Matthias Fischer <matthias.fischer@ipfire.org> To: development@lists.ipfire.org Subject: [PATCH] New IP-address of 'ping.ipfire.org' Date: Sun, 7 Feb 2016 13:45:32 +0100 Message-Id: <1454849132-5872-1-git-send-email-matthias.fischer@ipfire.org> X-Mailer: git-send-email 2.7.1 X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <http://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <http://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
Message
Matthias Fischer
Feb. 7, 2016, 11:45 p.m. UTC
Telekom gateways (e.g.) don't answer 'pings', therefor '/etc/ppp/ip-up'
uses 'ping.ipfire.org' for the 'gateway Graph' in 'Status / Network (other'.
After moving the infrastructure, several IP addresses were changed.
'178.63.73.246' doesn't work anymore for 'ping.ipfire.org', its now '81.3.27.38'.
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
---
src/ppp/ip-up | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
Hi, this is right. Usually the systems should never reach the code where the name cannot be resolved. We have moved to a new data center, so that IP address has to be updated, too. I don't know why this is hard-coded though. I don't like it. Merged. Best, -Michael On Sun, 2016-02-07 at 13:45 +0100, Matthias Fischer wrote: > Telekom gateways (e.g.) don't answer 'pings', therefor '/etc/ppp/ip- > up' > uses 'ping.ipfire.org' for the 'gateway Graph' in 'Status / Network > (other'. > After moving the infrastructure, several IP addresses were changed. > '178.63.73.246' doesn't work anymore for 'ping.ipfire.org', its now > '81.3.27.38'. > > Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org> > --- > src/ppp/ip-up | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/ppp/ip-up b/src/ppp/ip-up > index fdd204b..b059a29 100644 > --- a/src/ppp/ip-up > +++ b/src/ppp/ip-up > @@ -74,7 +74,7 @@ else > echo "$FIRE gateway" >> /tmp/hosts > else > #DNS lookup failed use direct ip > - echo "178.63.73.246 gateway" >> /tmp/hosts > + echo "81.3.27.38 gateway" >> /tmp/hosts > fi > fi > mv /tmp/hosts /etc/hosts
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=6&t=15432&hilit=telekom+gateway).
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=6&t=15432&hilit=telekom+gateway&start=15#p93043).
Best,
Matthias