public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Wiki-Link leads to chrisbenton
Date: Mon, 27 Aug 2018 07:11:49 +0100	[thread overview]
Message-ID: <6627186b5d704bc83c37688a379bf585c240aec0.camel@ipfire.org> (raw)
In-Reply-To: <2b40374e-1a06-eb94-e44b-1b8716913de6@jwsss.com>

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]

Hi,

I am sure that some other places have talked about this and that there might be
an alternative article.

Or maybe one of you wants to just summarize the post a little bit on an own page
on our wiki?

Best,
-Michael

On Sun, 2018-08-26 at 15:55 -0700, jim stephens wrote:
> Perhaps replace with a note and this link to the archive.org?
> 
> Looks like it may have been junk since 2014, FWIW in the archive.org.  
> 302 redirects, no content since then.
> 
> 
https://web.archive.org/web/20140603031911/http://www.chrisbrenton.org/2009/07/why-firewall-reject-rules-are-better-than-firewall-drop-rules/
> 
> On 8/26/2018 7:08 AM, Matthias Fischer wrote:
> > Hi!
> > 
> > This just came to my view:
> > 
> > The current link for "Drop vs Reject" on
> > https://wiki.ipfire.org/configuration/firewall/start leads to
> > 
http://www.chrisbrenton.org/2009/07/why-firewall-reject-rules-are-better-than-firewall-drop-rules/
> > .
> > 
> > But this URL only shows a big, white page on chrisbenton.org: "Diese
> > Domain kaufen".
> > 
> > No relevant contents at all.
> > 
> > Deleted without warning!?
> > 
> > Best,
> > Matthias
> > 
> > 
> 
> 


       reply	other threads:[~2018-08-27  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2b40374e-1a06-eb94-e44b-1b8716913de6@jwsss.com>
2018-08-27  6:11 ` Michael Tremer [this message]
     [not found] <bbccbb44-a96f-2710-b449-d0383c0cfd9b@jwsss.com>
2018-08-27  6:53 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6627186b5d704bc83c37688a379bf585c240aec0.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox