Hello community,

here is the log from the commit of package clatd for openSUSE:Factory checked 
in at 2018-12-13 19:48:09
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/clatd (Old)
 and      /work/SRC/openSUSE:Factory/.clatd.new.28833 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "clatd"

Thu Dec 13 19:48:09 2018 rev:1 rq:655876 version:1.4

Changes:
--------
New Changes file:

--- /dev/null   2018-10-29 14:05:42.522318975 +0100
+++ /work/SRC/openSUSE:Factory/.clatd.new.28833/clatd.changes   2018-12-13 
19:48:09.736722856 +0100
@@ -0,0 +1,4 @@
+-------------------------------------------------------------------
+Sun Dec  2 20:37:20 UTC 2018 - mar...@gmx.de
+
+- Initial package, version 1.4

New:
----
  0001-nm-dispatcher-only-act-on-iface-up-down-events.patch
  0002-Update-siit-dc-eam-I-D-references-to-RFC-numbers.patch
  clatd-1.4.tar.gz
  clatd.changes
  clatd.conf
  clatd.spec

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ clatd.spec ++++++
#
# spec file for package clatd
#
# Copyright (c) 2018, Martin Hauke <mar...@gmx.de>
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#


Name:           clatd
Version:        1.4
Release:        0
Summary:        CLAT / SIIT-DC Edge Relay implementation for Linux
License:        MIT
Group:          Productivity/Networking/System
URL:            https://github.com/toreanderson/clatd
#Git-Clone:     https://github.com/toreanderson/clatd.git
Source:         
https://github.com/toreanderson/%{name}/archive/v%{version}.tar.gz#/%{name}-%{version}.tar.gz
Source1:        clatd.conf
Patch0:         0001-nm-dispatcher-only-act-on-iface-up-down-events.patch
Patch1:         0002-Update-siit-dc-eam-I-D-references-to-RFC-numbers.patch
BuildRequires:  NetworkManager
BuildRequires:  perl
BuildRequires:  systemd-rpm-macros
Requires:       iproute2
Requires:       iptables
Requires:       perl
Requires:       tayga
Requires:       perl(File::Temp)
Requires:       perl(IO::Socket::INET6)
Requires:       perl(Net::DNS)
Requires:       perl(Net::IP)
BuildArch:      noarch

%description
clatd implements the CLAT component of the 464XLAT network architecture
specified in RFC 6877. It allows an IPv6-only host to have IPv4
connectivity that is translated to IPv6 before being routed to an upstream
PLAT (which is typically a Stateful NAT64 operated by the ISP) and there
translated back to IPv4 before being routed to the IPv4 internet.

%prep
%setup -q
%patch0 -p1
%patch1 -p1

%build
pod2man --name clatd --center "clatd - a CLAT implementation for Linux" 
--section 8 README.pod clatd.8
sed -i "s,%{_sbindir}/clatd,%{_sbindir}/clatd -c %{_sysconfdir}/clatd.conf," 
scripts/*

%install
install -D -m 0755 clatd %{buildroot}%{_sbindir}/clatd
install -D -m 0644 clatd.8 %{buildroot}%{_mandir}/man8/clatd.8
install -D -m 0644 %{SOURCE1} %{buildroot}%{_sysconfdir}/clatd.conf
install -D -m 0755 scripts/clatd.networkmanager 
%{buildroot}%{_sysconfdir}/NetworkManager/dispatcher.d/50-clatd
install -D -m 0644 scripts/clatd.systemd %{buildroot}%{_unitdir}/%{name}.service
ln -s %{_sbindir}/service %{buildroot}%{_sbindir}/rcclatd

%pre
%service_add_pre %{name}.service

%post
%service_add_post %{name}.service

%preun
%service_del_preun %{name}.service

%postun
%service_del_postun %{name}.service

%files
%license LICENCE
%doc README.pod
%{_sbindir}/clatd
%{_sbindir}/rcclatd
%config(noreplace) %{_sysconfdir}/clatd.conf
%{_sysconfdir}/NetworkManager/dispatcher.d/
%{_mandir}/man8/clatd.8%{?ext_man}
%{_unitdir}/%{name}.service

%changelog
++++++ 0001-nm-dispatcher-only-act-on-iface-up-down-events.patch ++++++
>From fb4587bfd6d0f6e034d1421a70639cc97a11307b Mon Sep 17 00:00:00 2001
From: Tore Anderson <t...@fud.no>
Date: Mon, 28 Mar 2016 08:26:20 +0200
Subject: [PATCH 1/2] nm-dispatcher: only act on iface up/down events

Ensure other events (like hostname changes, DHCP lease renewals, etc.)
are ignored as they are very unlikely to be relevant for clatd.
---
 scripts/clatd.networkmanager | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/clatd.networkmanager b/scripts/clatd.networkmanager
index 4187959..8a815ba 100644
--- a/scripts/clatd.networkmanager
+++ b/scripts/clatd.networkmanager
@@ -14,6 +14,11 @@
 # committing suicide from the restarts below
 [ "$DEVICE_IFACE" = "clat" ] && exit 0
 
+# We're only acting on interface "up" or "down" events. NM will run the
+# dispatcher scripts for other events we're not interested in, like the
+# hostname being set or a DHCP lease being renewed. Ignore those.
+[ "$2" != "up" ] && [ "$2" != "down" ] && exit 0
+
 # We simply restart clatd in all situations, as no matter if an interface
 # goes up or down, it may mean that the PLAT device changes, it may mean
 # native IPv4 appearing or disappearing, or it may mean that DNS64 became
-- 
2.16.4

++++++ 0002-Update-siit-dc-eam-I-D-references-to-RFC-numbers.patch ++++++
>From 18dca086c2c4279195bad9a38991b0b2360ca449 Mon Sep 17 00:00:00 2001
From: Tore Anderson <t...@fud.no>
Date: Mon, 28 Mar 2016 08:38:56 +0200
Subject: [PATCH 2/2] Update siit-dc/eam I-D references to RFC numbers

The three I-Ds that describe SIIT-DC and SIIT-EAM have been published as
RFCs, so update the references accordingly. Also update once occurrence
of old terminology ("Host Agent") with the new and final one ("Edge
Relay").
---
 README.pod | 25 ++++++++++++-------------
 clatd      |  4 ++--
 2 files changed, 14 insertions(+), 15 deletions(-)

diff --git a/README.pod b/README.pod
index 41591c8..0cd227d 100644
--- a/README.pod
+++ b/README.pod
@@ -14,11 +14,11 @@ make use of DNS64 (for example because they use legacy 
AF_INET socket calls,
 or if they are simply not using DNS64).
 
 B<clatd> may also be used to implement an SIIT-DC Edge Relay as described in
-I<I-D.ietf-v6ops-siit-dc-2xlat>. In this scenario, the PLAT is in reality a
-SIIT-DC Border Relay (see I<I-D.ietf-v6ops-siit-dc>) instead of a Stateful
-NAT64 (see I<RFC6146>). When used as a SIIT-DC Edge Relay, you will probably
-want to manually configure the settings I<clat-v4-addr>, I<clat-v6-addr>, and
-I<plat-prefix> to mirror the SIIT-DC Border Relay's configuration.
+I<RFC 7756>. In this scenario, the PLAT is in reality a SIIT-DC Border Relay
+(see I<RFC 7755>) instead of a Stateful NAT64 (see I<RFC6146>). When used as a
+SIIT-DC Edge Relay, you will probably want to manually configure the settings
+I<clat-v4-addr>, I<clat-v6-addr>, and I<plat-prefix> to mirror the SIIT-DC
+Border Relay's configuration.
 
 It relies on the software package TAYGA by Nathan Lutchansky for the actual
 translation of packets between IPv4 and IPv6 (I<RFC 6145>) TAYGA may be
@@ -183,11 +183,11 @@ will bind to this address when communicating with 
external IPv4 destinations.
 In a standard 464XLAT environment with a stateful NAT64 serving as the PLAT,
 there should be no need to change the default.
 
-When using B<clatd> as an SIIT-DC Edge Relay (I<I-D.ietf-v6ops-siit-dc-2xlat>),
-you will want to set this to the IPv4 Service Address configured in the SIIT-DC
-Border Relay. This way, local applications can correctly identify which public
-address they'll be using on the IPv4 internet, and will be able to provide
-fully functional references to it in application-level payload, and so on.
+When using B<clatd> as an SIIT-DC Edge Relay (I<RFC 7756>), you will want to
+set this to the IPv4 Service Address configured in the SIIT-DC Border Relay.
+This way, local applications can correctly identify which public address
+they'll be using on the IPv4 internet, and will be able to provide fully
+functional references to it in application-level payload, and so on.
 
 The default address is one from I<RFC 7335>.
 
@@ -436,8 +436,7 @@ SOFTWARE.
 
 ip(8), ip6tables(8), tayga(8), tayga.conf(5)
 
-RFC 6052, RFC 6145, RFC 6146, RFC 6877, RFC 7050, RFC 7335
-
-I-D.ietf-v6ops-siit-dc, I-D.ietf-v6ops-siit-dc-2xlat, I-D.ietf-v6ops-siit-eam
+RFC 6052, RFC 6145, RFC 6146, RFC 6877, RFC 7050, RFC 7335 RFC 7755, RFC 7756,
+RFC 7757
 
 =cut
diff --git a/clatd b/clatd
index 9831d57..8af83ad 100755
--- a/clatd
+++ b/clatd
@@ -665,8 +665,8 @@ for (my $i = 0; $i < @ARGV;) {
     next;
   } elsif($ARGV[$i] =~ /^(-h|--help)$/) {
     print <<"EOF";
-clatd v$VERSION - a 464XLAT (RFC 6877) CLAT and SIIT-DC Host Agent
-             (I-D.anderson-v6ops-siit-dc-2xlat) implementation for Linux
+clatd v$VERSION - a 464XLAT (RFC 6877) CLAT and SIIT-DC Edge Relay
+             (RFC 7756) implementation for Linux
 EOF
     print "\n";
     print "  Usage:    clatd [-q] [-d [-d]] [-c config-file] ",
-- 
2.16.4

++++++ clatd.conf ++++++
# Default clatd.conf
# See clatd(8) for a list of config directives

Reply via email to