From owner-freebsd-isp Fri Dec 1 10: 5:18 2000 Delivered-To: freebsd-isp@freebsd.org Received: from gate1.noc.usmc.mil (gate1.noc.usmc.mil [192.156.71.34]) by hub.freebsd.org (Postfix) with ESMTP id D669E37B400 for ; Fri, 1 Dec 2000 10:05:12 -0800 (PST) Received: by gate1.noc.usmc.mil; id SAA00175; Fri, 1 Dec 2000 18:04:11 GMT Received: from host014.noc.usmc.mil(192.156.77.14) by gate1.noc.usmc.mil via smap (V5.0) id xma029567; Fri, 1 Dec 00 18:03:11 GMT Received: by host014.noc.usmc.mil with Internet Mail Service (5.5.2650.21) id ; Fri, 1 Dec 2000 13:02:17 -0500 Message-ID: <1988A7BBBD55D3119B4A00902771C45404A01365@host014.noc.usmc.mil> From: Bird Mr Gregory L To: "'freebsd-isp@FreeBSD.ORG'" Subject: RE: Danger Ports Date: Fri, 1 Dec 2000 13:02:17 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C05BC0.D75C1B00" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C05BC0.D75C1B00 Content-Type: text/plain; charset="iso-8859-1" Yes there is overlap...I am not quite sure where you learned how to subnet...but the rest of the world does it: access-list lines: access-list 110 deny ip 172.16.0.0 0.15.255.255 any log access-list 110 deny ip 172.31.0.0 0.0.255.255 any log 172.16.0.0 0.15.255.255 = 172.16.0.0:255.252.0.0 = 172.16.0.0 - 172.31.255.255 so there is overlap. You might want to refresh yourself a little on your subnetting...or fully caffeinate yourself. Greg Bird Senior Network Security Engineer -----Original Message----- From: William Sommers [mailto:sommers@sfo.com] Sent: Friday, December 01, 2000 11:06 AM To: freebsd-isp@FreeBSD.ORG Subject: Re: Danger Ports At 12:28 AM 12/1/00 -0600, Butch Evans wrote: >> > > access-list 110 deny ip 172.16.0.0 0.15.255.255 any log >> > > access-list 110 deny ip 172.31.0.0 0.0.255.255 any log >> >> > access-list 110 deny ip any 172.16.0.0 0.15.255.255 log >> > access-list 110 deny ip any 172.31.0.0 0.0.255.255 log >> >> Is it me? Isn't the second network in each a subset of the first? >> > Now that I re-read your question, I see what you are saying...You are > correct. Um, unless I'm not yet fully caffeinated: 172.16.0.0 0.15.255.255 matches 176.16.0.0 - 176.30.255.255 172.31.0.0 0.0.255.255 matches 176.31.0.0 - 176.31.255.255 No overlap at all. -wfs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message ------_=_NextPart_001_01C05BC0.D75C1B00 Content-Type: text/html; charset="iso-8859-1" RE: Danger Ports

Yes there is overlap...I am not quite sure where you learned how to subnet...but the rest of the world does it:


access-list lines:
access-list 110 deny   ip 172.16.0.0 0.15.255.255 any log
access-list 110 deny   ip 172.31.0.0 0.0.255.255 any log


172.16.0.0 0.15.255.255 = 172.16.0.0:255.252.0.0 = 172.16.0.0 - 172.31.255.255

so there is overlap. You might want to refresh yourself a little on your subnetting...or fully caffeinate yourself.


Greg Bird
Senior Network Security Engineer



-----Original Message-----
From: William Sommers [mailto:sommers@sfo.com]
Sent: Friday, December 01, 2000 11:06 AM
To: freebsd-isp@FreeBSD.ORG
Subject: Re: Danger Ports


At 12:28 AM 12/1/00 -0600, Butch Evans wrote:

 >> > > access-list 110 deny   ip 172.16.0.0 0.15.255.255 any log
 >> > > access-list 110 deny   ip 172.31.0.0 0.0.255.255 any log
 >>
 >> > access-list 110 deny   ip any 172.16.0.0 0.15.255.255 log
 >> > access-list 110 deny   ip any 172.31.0.0 0.0.255.255 log
 >>
 >> Is it me? Isn't the second network in each a subset of the first?
 >>
 > Now that I re-read your question, I see what you are saying...You are
 > correct.

Um, unless I'm not yet fully caffeinated:

172.16.0.0 0.15.255.255 matches 176.16.0.0 - 176.30.255.255
172.31.0.0 0.0.255.255  matches 176.31.0.0 - 176.31.255.255

No overlap at all.


  -wfs



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message

------_=_NextPart_001_01C05BC0.D75C1B00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message