Hello,
this is a post to update you all about the recent developments regarding
the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or
made them unusable so that people started searching for alternatives. In
IPFire 2, a script called setddns.pl [1] is responsible for updating the
dynamic DNS records. This script has grown over the last couple of
months and if you have looked into it you will have noticed that it has
become from ugly to almost un-maintainable. The decision that we don't
want to take this mess with us into the next generation of IPFire was
already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is
much more flexible, cleanly rewritten and easily extensible. It is
cross-platform, cross-distribution and does not need any third-party
python modules.
The basics already written years ago, Stefan Schantl and I worked on
making this ready for IPFire 2 and added all the providers that are
currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so
on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that
this won't take long until DDNS arrives in IPFire 2. That means that we
won't take any patches for the setddns.pl script that add support for
new providers any more.
We appreciate any contribution and as always hope to get some feedback
back from the community!
Best,
-Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5…
Hi,
I build iPerf3 for IPFire, (for reasons look here:
http://forum.ipfire.org/viewtopic.php?f=50&t=15498) and was told that
i should submit changes to the mailing list.
Here is a patch with all changes:
Signed-off-by: Jonatan Schlag <jonatan(a)familyschlag.de>
From a403b42f389cd5617937a0df220c67e279236034 Mon Sep 17 00:00:00 2001
From: jonaschl <jonnyschlag(a)gmail.com>
Date: Wed, 23 Dec 2015 13:43:20 +0100
Subject: [PATCH] new package iPerf 3
email: jonnyschlag(a)gmail.com
author: jonaschl
---
config/rootfiles/packages/iperf3 | 10 +++++
lfs/iperf3 | 84 ++++++++++++++++++++++++++++++++++++++++
make.sh | 1 +
3 files changed, 95 insertions(+)
create mode 100644 config/rootfiles/packages/iperf3
create mode 100644 lfs/iperf3
diff --git a/config/rootfiles/packages/iperf3
b/config/rootfiles/packages/iperf3
new file mode 100644
index 0000000..717cc96
--- /dev/null
+++ b/config/rootfiles/packages/iperf3
@@ -0,0 +1,10 @@
+usr/bin/iperf3
+#usr/include/iperf_api.h
+usr/lib/libiperf.a
+usr/lib/libiperf.la
+usr/lib/libiperf.so
+usr/lib/libiperf.so.0
+usr/lib/libiperf.so.0.0.0
+#usr/share/man/man1/iperf3.1
+#usr/share/man/man3/libiperf.3
+
diff --git a/lfs/iperf3 b/lfs/iperf3
new file mode 100644
index 0000000..b8e0cd2
--- /dev/null
+++ b/lfs/iperf3
@@ -0,0 +1,84 @@
+###############################################################################
+# #
+# IPFire.org - A linux based firewall #
+# Copyright (C) 2007-2015 IPFire Team <info(a)ipfire.org> #
+# #
+# This program is free software: you can redistribute it and/or modify
#
+# it under the terms of the GNU General Public License as published by
#
+# the Free Software Foundation, either version 3 of the License, or #
+# (at your option) any later version. #
+# #
+# This program is distributed in the hope that it will be useful, #
+# but WITHOUT ANY WARRANTY; without even the implied warranty of #
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
+# GNU General Public License for more details. #
+# #
+# You should have received a copy of the GNU General Public License #
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
+# #
+###############################################################################
+
+###############################################################################
+# Definitions
+###############################################################################
+
+include Config
+
+VER = 3.1.1
+
+THISAPP = iperf3-$(VER)
+DL_FILE = $(THISAPP).tar.gz
+DL_FROM = $(URL_IPFIRE)
+DIR_APP = $(DIR_SRC)/$(THISAPP)
+TARGET = $(DIR_INFO)/$(THISAPP)
+PROG = iperf3
+PAK_VER = 1
+
+DEPS = ""
+
+###############################################################################
+# Top-level Rules
+###############################################################################
+
+objects = $(DL_FILE)
+
+$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
+
+$(DL_FILE)_MD5 = 62e3d2a057cca69e88ebfbf35b7483ef
+
+install : $(TARGET)
+
+check : $(patsubst %,$(DIR_CHK)/%,$(objects))
+
+download :$(patsubst %,$(DIR_DL)/%,$(objects))
+
+md5 : $(subst %,%_MD5,$(objects))
+
+dist:
+ @$(PAK)
+
+###############################################################################
+# Downloading, checking, md5sum
+###############################################################################
+
+$(patsubst %,$(DIR_CHK)/%,$(objects)) :
+ @$(CHECK)
+
+$(patsubst %,$(DIR_DL)/%,$(objects)) :
+ @$(LOAD)
+
+$(subst %,%_MD5,$(objects)) :
+ @$(MD5)
+
+###############################################################################
+# Installation Details
+###############################################################################
+
+$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
+ @$(PREBUILD)
+ @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
+ cd $(DIR_APP) && ./configure --prefix=/usr
+ cd $(DIR_APP) && make $(MAKETUNING)
+ cd $(DIR_APP) && make install
+ @rm -rf $(DIR_APP)
+ @$(POSTBUILD)
diff --git a/make.sh b/make.sh
index 39089cd..b184115 100755
--- a/make.sh
+++ b/make.sh
@@ -740,6 +740,7 @@ buildipfire() {
ipfiremake gutenprint
ipfiremake apcupsd
ipfiremake iperf
+ ipfiremake iperf3
ipfiremake netcat
ipfiremake 7zip
ipfiremake lynis
--
2.1.4
I do not know if i do all right, in the moment I am not so familiar
with git and patches.
In addition I have a question. When I build iPerf 3 I run into a bug
(see https://github.com/esnet/iperf/issues/337). I modified the source
package and now iPerf 3 build. There are c flags which are
incompatible. What is the better style to modify the source package and
use this source package or to create a patch (what I try but I fail)
and use the original source package and patch it during the build
process? The source package what I use in the moment could be find
here: http://forum.ipfire.org/download/file.php?id=1853
Yours sincerely Jonatan Schlag
Changelog - in short:
- Security fixes (denial of service):
- Prevent invalid reads in case of corrupt chunk-encoded content.
CVE-2016-1982. Bug discovered with afl-fuzz and AddressSanitizer.
- Remove empty Host headers in client requests.
Previously they would result in invalid reads. CVE-2016-1983.
Bug discovered with afl-fuzz and AddressSanitizer.
Also several bug fixes as well as general, action file, and documentation improvements.
For details see:
http://www.privoxy.org/announce.txt
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
lfs/privoxy | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lfs/privoxy b/lfs/privoxy
index bc4848a..de650a2 100644
--- a/lfs/privoxy
+++ b/lfs/privoxy
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2015 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2016 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,14 +24,14 @@
include Config
-VER = 3.0.23
+VER = 3.0.24
THISAPP = privoxy-$(VER)
DL_FILE = $(THISAPP)-stable-src.tar.gz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = privoxy
-PAK_VER = 2
+PAK_VER = 3
DEPS = ""
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = bbe47d5ff1a54d9f9fc93a160532697f
+$(DL_FILE)_MD5 = 44a47d1a5000db8cccd61ace0e25e7f7
install : $(TARGET)
@@ -53,7 +53,7 @@ download :$(patsubst %,$(DIR_DL)/%,$(objects))
md5 : $(subst %,%_MD5,$(objects))
-dist:
+dist:
$(PAK)
###############################################################################
--
2.7.0
Fixes since 2.0.23 (short version):
Remove release process from README.
Fix missing libc_compat.h in release tarball.
Avoid using SW_VIDEOOUT_INSERT if it isn't available.
Add support for Copy and Restart keys.
Add support for non-glibc libc's. (acpi_listen.c acpid.c event.c
input_layer.c kacpimon/libnetlink.h libc_compat.h libnetlink.c netlink.c
proc.c ud_socket.c) (Brendan Heading <brendanheading(a)gmail.com>)
Fix compiler warnings. (acpi_listen.c event.c sock.c)
Add systemd info to documentation.
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
lfs/acpid | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/acpid b/lfs/acpid
index 476c9a8..963dfb5 100644
--- a/lfs/acpid
+++ b/lfs/acpid
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2015 Michael Tremer & Christian Schmidt #
+# Copyright (C) 2016 Michael Tremer & Christian Schmidt #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 2.0.23
+VER = 2.0.25
THISAPP = acpid-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -41,7 +41,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = d7bcdcdefcd53b03730e50ba842554ea
+$(DL_FILE)_MD5 = 69bb0cc4a0a89eb2dfecc4851087f568
install : $(TARGET)
--
2.7.0
Hi,
so in recent times we had many people who have struggled with sending
in patches. The topic comes up every few weeks and I am not aware why
that is. I find this process with "git send-email" very easy and I am
not sure where the problems could be.
So I would like to start a discussion about where the problems are and
maybe that some of you can share their experiences and solutions. What
tools are you using? Do they need special settings?
The goal of that should be that we can add all the required information
to the documentation. Sending in patches should not be this frustration
experience it is at the moment.
http://wiki.ipfire.org/devel/submit-patches
Best,
-Michael