Great Circle Associates Firewalls
(January 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Re[2]: NT NAT
From: Carl Karlsson <ckn @ findata . se>
Date: Sun, 5 Jan 1997 01:16:33 +0100 (MET)
To: firewalls @ GreatCircle . COM
In-reply-to: <3 . 0 . 32 . 19970104111733 . 006caf34 @ lint . cisco . com>
Reply-to: Carl Karlsson <ckn @ findata . se>

On Sat, 4 Jan 1997, Paul Ferguson wrote:

> At 09:43 AM 1/4/97 -0600, Peter da Silva wrote:
> 
> >> Please correct me if I'm wrong here but I was under the impression that
> >> the 192.168.x.x-addresses was 'non-routable' or whatever the term is.
> >> Under what circumstances can an external intruder gain access to my
> >> internal 192.168.x.x-machines? 
> >
> >Source routed packets.
> 
> Which are easily stopped.

You guys have a cool terse way of discussing interesting things. :) I was
thinking that source routed packets was the answer to my question, and I
was also believing that they could be stopped. Do I need to care about
source routed packets if my upstream provider has everything configured
as they should? If I am using for example Linux, would it be enough to
configure the linux kernel to drop source routed packets? To configure the
linux firewall to ignore localnet packets from the external link?
Many questions.. I'll accept an RTFM answer if someone also tells me WTFM
is. :)

  Calle



Follow-Ups:
References:
Indexed By Date Previous: RE: Huh? I musta misread this!
From: Gene Lee <genel @ inforamp . net>
Next: Re: Re[2]: NT NAT
From: Paul Ferguson <pferguso @ cisco . com>
Indexed By Thread Previous: Re: Re[2]: NT NAT
From: Paul Ferguson <pferguso @ cisco . com>
Next: Re: Re[2]: NT NAT
From: peter @ baileynm . com (Peter da Silva)

Google
 
Search Internet Search www.greatcircle.com