From 57557e909d90bb4b36f1896fff9958d6126c6345 Mon Sep 17 00:00:00 2001 From: John Crispin Date: Thu, 14 Apr 2016 18:03:49 +0200 Subject: [PATCH] docs: fix some links Signed-off-by: John Crispin --- docs/uci_firewall.txt | 6 +++--- docs/uci_system.txt | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/uci_firewall.txt b/docs/uci_firewall.txt index e310ddd..feaf573 100644 --- a/docs/uci_firewall.txt +++ b/docs/uci_firewall.txt @@ -223,7 +223,7 @@ CAUTION: Since custom iptables rules are meant to be more specific than the gene === IP Sets -The UCI firewall version 3 supports referencing or creating [[http:_ipset.netfilter.org/|ipsets]] to simplify matching of +The UCI firewall version 3 supports referencing or creating http://ipset.netfilter.org/[ipsets] to simplify matching of huge address or port lists without the need for creating one rule per item to match, The following options are defined for _ipsets_: @@ -727,7 +727,7 @@ If traffic is _rejected_, the router will respond with an ICMP error message ("d When connection attempts are _dropped_ the client is not aware of the blocking and will continue to re-transmit its packets until the connection eventually times out. Depending on the way the client software is implemented, this could result in frozen or hanging programs that need to wait until a timeout occurs before they're able to continue. -Also there is an interesting article which that claims dropping connections doesnt make you any safer - link:http:_www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject[Drop versus Reject] +Also there is an interesting article which that claims dropping connections doesnt make you any safer - link:http://www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject[Drop versus Reject] **DROP** @@ -751,7 +751,7 @@ By default, the firewall will disable connection tracking for a zone if no masqu CAUTION: _NOTRACK_ will render certain ipables extensions unusable, for example the _MASQUERADE_ target or the _state_ match will not work! -If connection tracking is required, for example by custom rules in '/etc/firewall.user', the 'conntrack' option must be enabled in the corresponding zone to disable _NOTRACK_. It should appear as 'option 'conntrack' '1' ' in the right zone in '/etc/config/firewall'. For further information see http:_security.maruhn.com/iptables-tutorial/x4772.html . +If connection tracking is required, for example by custom rules in '/etc/firewall.user', the 'conntrack' option must be enabled in the corresponding zone to disable _NOTRACK_. It should appear as 'option 'conntrack' '1' ' in the right zone in '/etc/config/firewall'. For further information see http://security.maruhn.com/iptables-tutorial/x4772.html . == Debug generated rule set diff --git a/docs/uci_system.txt b/docs/uci_system.txt index 6cb7479..fe295a4 100644 --- a/docs/uci_system.txt +++ b/docs/uci_system.txt @@ -43,8 +43,8 @@ These options can be set in the system section: | {{:meta:icons:tango:48px-outdated.svg.png?nolink}} | In '/etc/config/system' 'busybox-rdate' (was invoked by scripts) has been replaced with 'busybox-nptd' (can run as a daemon) to avoid race condition and also to use current NTP. The remote time is since configured in '/etc/config/system' and not in '/etc/config/timeserver' any longer. -* WARNING: Old scripts first checked if a lease time server is defined for the interface in the [[doc:uci:network|network config]]. -* WARNING: If not available or syncing fails, then it searches for time servers in the [[doc:uci:timeserver|timeserver config]] that are either explicitly defined for that interface or via the global setting in the system config. +* WARNING: Old scripts first checked if a lease time server is defined for the interface in the network config. +* WARNING: If not available or syncing fails, then it searches for time servers in the timeserver config that are either explicitly defined for that interface or via the global setting in the system config. ---- config 'timeserver' 'ntp' -- 2.30.2