firewall: fix TCP MSS settings issue (#40)
This commit is contained in:
parent
c37d3b72d9
commit
fe7a87ec25
@ -13,9 +13,9 @@ PKG_RELEASE:=2
|
|||||||
|
|
||||||
PKG_SOURCE_PROTO:=git
|
PKG_SOURCE_PROTO:=git
|
||||||
PKG_SOURCE_URL=$(PROJECT_GIT)/project/firewall3.git
|
PKG_SOURCE_URL=$(PROJECT_GIT)/project/firewall3.git
|
||||||
PKG_SOURCE_DATE:=2021-03-23
|
PKG_SOURCE_DATE:=2022-02-17
|
||||||
PKG_SOURCE_VERSION:=61db17edddb1f05e8107f0dbef6f7d060ce67483
|
PKG_SOURCE_VERSION:=4cd7d4f36bea731bf901cb067456f1d460294926
|
||||||
PKG_MIRROR_HASH:=b2eb09816640e14e2dae21fb54ea05c33858fe0004844fe8d99e541a2e19e9c0
|
PKG_MIRROR_HASH:=ce9e8ac1bcf22afbb0a80c3da1a8e8e887851299681097e3dfbfc347f2c4c80f
|
||||||
PKG_MAINTAINER:=Jo-Philipp Wich <jo@mein.io>
|
PKG_MAINTAINER:=Jo-Philipp Wich <jo@mein.io>
|
||||||
PKG_LICENSE:=ISC
|
PKG_LICENSE:=ISC
|
||||||
|
|
||||||
|
@ -3,7 +3,7 @@ config defaults
|
|||||||
option input ACCEPT
|
option input ACCEPT
|
||||||
option output ACCEPT
|
option output ACCEPT
|
||||||
option forward REJECT
|
option forward REJECT
|
||||||
option fullcone 2
|
option fullcone 0
|
||||||
# Uncomment this line to disable ipv6 rules
|
# Uncomment this line to disable ipv6 rules
|
||||||
# option disable_ipv6 1
|
# option disable_ipv6 1
|
||||||
|
|
||||||
|
@ -1,38 +0,0 @@
|
|||||||
From df1306a96127e91ff2d513a0a67345baaf61d113 Mon Sep 17 00:00:00 2001
|
|
||||||
From: Florian Eckert <fe@dev.tdt.de>
|
|
||||||
Date: Fri, 19 Nov 2021 09:51:02 +0100
|
|
||||||
Subject: [PATCH] firewall3: fix locking issue
|
|
||||||
|
|
||||||
By calling the command 'fw3 reload' several times at the same time, I
|
|
||||||
noticed that the locking was not working properly. It happened from time
|
|
||||||
to time that some firewall rules were present twice in the system!
|
|
||||||
|
|
||||||
By removing the 'unlink' systemcall, this error no longer occurred on my
|
|
||||||
systems.
|
|
||||||
|
|
||||||
Since fw3 does not run as a service, it makes no sense to delete this
|
|
||||||
lock file every time a filehandler is no longer open on this lock file,
|
|
||||||
because fw3 binary is not running.
|
|
||||||
|
|
||||||
If fw3 does run as a service then we can remove this lock file on
|
|
||||||
service stop. But this is not the case for fw3.
|
|
||||||
|
|
||||||
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
|
|
||||||
---
|
|
||||||
utils.c | 1 -
|
|
||||||
1 file changed, 1 deletion(-)
|
|
||||||
|
|
||||||
diff --git a/utils.c b/utils.c
|
|
||||||
index 17d5bf9..92e966c 100644
|
|
||||||
--- a/utils.c
|
|
||||||
+++ b/utils.c
|
|
||||||
@@ -397,7 +397,6 @@ fw3_unlock_path(int *fd, const char *lockpath)
|
|
||||||
warn("Cannot release exclusive lock: %s", strerror(errno));
|
|
||||||
|
|
||||||
close(*fd);
|
|
||||||
- unlink(FW3_LOCKFILE);
|
|
||||||
|
|
||||||
*fd = -1;
|
|
||||||
}
|
|
||||||
--
|
|
||||||
2.30.2
|
|
Loading…
x
Reference in New Issue
Block a user