From dad7dc307fce9539b7a58d8a6fab97f7ae456875 Mon Sep 17 00:00:00 2001 From: Franco Fichtner Date: Thu, 13 Sep 2018 03:52:13 +0200 Subject: [PATCH] net/samplicator: sync with upstream Taken from: HardenedBSD --- net/samplicator/Makefile | 3 ++- net/samplicator/files/patch-rawsend.c | 15 +++++++++++++++ 2 files changed, 17 insertions(+), 1 deletion(-) create mode 100644 net/samplicator/files/patch-rawsend.c diff --git a/net/samplicator/Makefile b/net/samplicator/Makefile index 2812c39bc4c..88dc079a52e 100644 --- a/net/samplicator/Makefile +++ b/net/samplicator/Makefile @@ -2,9 +2,10 @@ PORTNAME= samplicator DISTVERSION= 1.3.8rc1 +PORTREVISION= 1 CATEGORIES= net -MAINTAINER= me@falz.net +MAINTAINER= ath@heybey.org COMMENT= Receives UDP datagrams and redistributes them to a set of receivers LICENSE= GPLv2 diff --git a/net/samplicator/files/patch-rawsend.c b/net/samplicator/files/patch-rawsend.c new file mode 100644 index 00000000000..4e8a83a15d1 --- /dev/null +++ b/net/samplicator/files/patch-rawsend.c @@ -0,0 +1,15 @@ +--- rawsend.c.orig 2015-04-28 22:22:02 UTC ++++ rawsend.c +@@ -118,9 +118,9 @@ raw_send_from_to (s, msg, msglen, saddr_generic, daddr + /* Depending on the target platform, te ip_off and ip_len fields + should be in either host or network byte order. Usually + BSD-derivatives require host byte order, but at least OpenBSD +- since version 2.1 uses network byte order. Linux uses network +- byte order for all IP header fields. */ +-#if defined (__linux__) || (defined (__OpenBSD__) && (OpenBSD > 199702)) ++ since version 2.1 and FreeBSD since 11.0 use network byte ++ order. Linux uses network byte order for all IP header fields. */ ++#if defined (__linux__) || (defined (__OpenBSD__) && (OpenBSD > 199702)) || (defined (__FreeBSD_version) && (__FreeBSD_version > 1100030)) + ih.ip_len = htons (length); + ih.ip_off = htons (0); + #else