From: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
To: "Michael J. Tubby B.Sc. (Hons) G8TIC" <mike.tubby@thorcom.co.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: External IP addresses on internal network
Date: Thu, 28 Aug 2003 12:19:36 -0400 [thread overview]
Message-ID: <3F4E2B98.7090003@Loudoun-Fairfax.com> (raw)
In-Reply-To: <008e01c36d7c$6218ca70$6401a8c0@int.thorcom.com>
Hey Mike,
Michael J. Tubby B.Sc. (Hons) G8TIC wrote:
>What you should be filtering is packet egress, that is your 192.168 or
>whatever internal LAN leaking 'naked' (un-NATted) to the internet at
>large.
>
>
Yes, I do this. I also filter coming from the LAN on the INPUT table
since I consider any box a potential risk.
>I do this in two places, on the main firewall box between out "inside"
>and "outside" in iptables and then again at the Cisco router facing
>PSInet with an ACL that drop & log any packets from anything other
>than our PSInet Class-C, so there's no way we can "leak" on to the 'net.
>
>
My DSL provider owns and maintains my router. I never thought about
filtering at the router. Hmm, I'll have to ask about that.
Jeff
next prev parent reply other threads:[~2003-08-28 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 22:43 External IP addresses on internal network George Vieira
2003-08-27 1:10 ` Jeffrey Laramie
2003-08-27 16:54 ` Jim Carter
2003-08-27 18:50 ` Jeffrey Laramie
2003-08-28 14:19 ` Chris Brenton
2003-08-28 15:43 ` Jeffrey Laramie
2003-08-28 14:56 ` Ramin Dousti
2003-08-28 16:21 ` Jeffrey Laramie
[not found] ` <3F4E2844.2050108@Loudoun-Fairfax.com>
2003-08-28 18:17 ` Ramin Dousti
2003-08-28 19:24 ` Jeffrey Laramie
2003-08-28 15:52 ` Michael J. Tubby B.Sc. (Hons) G8TIC
2003-08-28 16:19 ` Jeffrey Laramie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-26 15:57 Jeffrey Laramie
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=3F4E2B98.7090003@Loudoun-Fairfax.com \
--to=jalaramie@loudoun-fairfax.com \
--cc=mike.tubby@thorcom.co.uk \
--cc=netfilter@lists.netfilter.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