From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 7b757df70fb4caa70eb0f3a0e0cd1af7c9adaea1
Date: Mon, 08 Feb 2016 02:32:39 +0000 [thread overview]
Message-ID: <20160208023239.693F81081BC7@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2651 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 7b757df70fb4caa70eb0f3a0e0cd1af7c9adaea1 (commit)
via c1bf984e05ff9c523121d459cd58154d3d37a34a (commit)
from 8260fb7e0eac021a9be1c120d39ecb8e4a76c2a2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 7b757df70fb4caa70eb0f3a0e0cd1af7c9adaea1
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Feb 8 01:52:18 2016 +0000
core98: Ship changed /etc/ppp/ip-up
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit c1bf984e05ff9c523121d459cd58154d3d37a34a
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Sun Feb 7 13:45:32 2016 +0100
New IP-address of 'ping.ipfire.org'
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>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/98/filelists/files | 1 +
src/ppp/ip-up | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/98/filelists/files b/config/rootfiles/core/98/filelists/files
index ad5d9a7..3e5063a 100644
--- a/config/rootfiles/core/98/filelists/files
+++ b/config/rootfiles/core/98/filelists/files
@@ -1,5 +1,6 @@
etc/system-release
etc/issue
+etc/ppp/ip-up
etc/rc.d/init.d/firewall
etc/rc.d/init.d/networking/dhcpcd.exe
etc/modprobe.d/nf_conntrack.conf
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
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-02-08 2:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160208023239.693F81081BC7@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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