mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: connectivity to bkbits.net?
Date: 29 Nov 2002 08:55:00 +0200	[thread overview]
Message-ID: <8anf-3Gmw-B@khms.westfalen.de> (raw)
In-Reply-To: <as6aks$amj$1@ncc1701.cistron.net>

miquels@cistron.nl (Miquel van Smoorenburg)  wrote on 28.11.02 in <as6aks$amj$1@ncc1701.cistron.net>:

> In article <20021128211347.D27234@flint.arm.linux.org.uk>,
> Russell King  <rmk@arm.linux.org.uk> wrote:
> >On Thu, Nov 28, 2002 at 06:53:00PM +0200, Kai Henningsen wrote:
> >> >From two or three traceroutes, that problem seems to be at the SGI end.
> >> >I
> >> can't get to them either (nothing after the same IP as for you, at hop
> >> #17, some place at Genuity), but you are practically next door.
> >
> >Lesson #1 of firewalling: drop everything.
> >Lesson #2 of firewalling: only accept what you absolutely have to.
>
> Lesson#3 of firewalling: due to #1 and #2 most admins block
> ICMP_UNREACH_NEEDFRAG as well (ICMP == ping == bad) breaking
> path MTUd. http://alive.znep.com/~marcs/mtu/

Lesson #4 of firewalling: a friendly firewall will (unless there are  
*specific* reasons to do otherwise) allow for ICMP_UNREACH_NEEDFRAG (and  
some similar things), ping, and traceroute. That's how I usually set them  
up. (ping == good)

MfG Kai

      reply	other threads:[~2002-11-29  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 16:25 Larry McVoy
2002-11-28 16:53 ` Kai Henningsen
2002-11-28 21:13   ` Russell King
2002-11-28 23:59     ` Miquel van Smoorenburg
2002-11-29  6:55       ` Kai Henningsen [this message]

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=8anf-3Gmw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®