From owner-freebsd-security Mon Aug 17 15:57:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12690 for freebsd-security-outgoing; Mon, 17 Aug 1998 15:57:25 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from kjsl.com (Limpia.KJSL.COM [198.137.202.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12668 for ; Mon, 17 Aug 1998 15:57:16 -0700 (PDT) (envelope-from javier@kjsl.com) Received: (from javier@localhost) by kjsl.com (8.8.5/8.8.5) id PAA27265; Mon, 17 Aug 1998 15:56:36 -0700 (PDT) Date: Mon, 17 Aug 1998 15:56:36 -0700 (PDT) Message-Id: <199808172256.PAA27265@kjsl.com> From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Palle Girgensohn Cc: freebsd-security@FreeBSD.ORG Subject: private network on router's external NIC? In-Reply-To: <35D8A7E8.2DC50695@partitur.se> References: <35D8A7E8.2DC50695@partitur.se> X-Mailer: VM 6.33 under Emacs 19.34.1 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Palle Girgensohn writes: > Makes sense to me. So, how do these ip numbers get out on the Internet? Talk to your upstream peer, he's the one sending them to you. They could originate from within his network. > How do they get routed anywhere; they're supposed to be private? I've seen packets destined for 172.16 also, another one of the "private" networks. They're probably crafted packets with a bogus source IP address. -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message