[PATCH] New IP-address of 'ping.ipfire.org'

[PATCH] New IP-address of 'ping.ipfire.org'

[Matthias Fischer]

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

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(a)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
-- 
2.7.1

Re: [PATCH] New IP-address of 'ping.ipfire.org'

[Michael Tremer]

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

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(a)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

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

Re: [PATCH] New IP-address of 'ping.ipfire.org'

[Matthias Fischer]

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

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