[Mldonkey-bugs] [bug #1579] RFC 1918 IPs + Reserved IPs + DoD IPs in Serverlist

[nobody]

=================== BUG #1579: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1579&group_id=1409

Changes by:  <address@hidden>
Date: Thu 07/03/2003 at 11:22 (GMT)

------------------ Additional Follow-up Comments ----------------------------
then you should know that 172.16.0.0 to 176.31.255.255 are rfc1918 addresses 
too.
Unfortunatly using 255 as a wildcard is not a good idea.
You should use the netmask notation.
It's easier to use 172.16.0.0/16 than 172.16.255.255, 172.17.255.255, 
172.18.255.255 ... 172.31.255.255



=================== BUG #1579: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: mldonkey, a free e-Donkey client
Submitted on: Sat 11/02/2002 at 05:17
Category:  Core                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  2.00                        Release:                              
Platform Version:  Linux i386-i686    Binaries Origin:  Downloaded from Savannah

Summary:  RFC 1918 IPs + Reserved IPs + DoD IPs in Serverlist

Original Submission:  The RFC 1918 IPs 
(http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1918.html)
are in the Server List
But there shouldn't.

I just discovered that those clowns uses Reserved Addresses too. Ask whois
1.0.0.0 - 1.255.255.255 (1.0.0.0/8)
2.0.0.0 - 2.255.255.255 (2.0.0.0/8)
5.0.0.0 - 5.255.255.255 (5.0.0.0/8)
70.0.0.0 - 79.255.255.255 (70.0.0.0/7, 72.0.0.0/5)
82.0.0.0 - 95.255.255.255 (82.0.0.0/7, 84.0.0.0/6,
                           88.0.0.0/5)
96.0.0.0 - 126.255.255.255 ( 96.0.0.0/4, 112.0.0.0/5,
                            120.0.0.0/6, 124.0.0.0/7,
                            126.0.0.0/8)
222.0.0.0 - 223.255.255.255 (222.0.0.0/7)
127.0.0.2 - 127.255.255.255

And (of course) the always liked DoD Addresses !!

U.S. Army Yuma Proving Ground: (will not be routed)
6.0.0.0 - 6.255.255.255 (6.0.0.0/8)
Defense Information Systems Agency: (will not be routed)
7.0.0.0 - 7.255.255.255 (7.0.0.0/8)
Defense Intelligence Agency: (will not be routed)
11.0.0.0 - 11.255.255.255 11.0.0.0/8

I apologise for this third posting, but those Server Guys are realy Clowns.

It's only a wast of time and resources dealing with them.

Ayn

Follow-up Comments
*******************

-------------------------------------------------------
Date: Thu 07/03/2003 at 11:22       By: schmurtz
then you should know that 172.16.0.0 to 176.31.255.255 are rfc1918 addresses 
too.
Unfortunatly using 255 as a wildcard is not a good idea.
You should use the netmask notation.
It's easier to use 172.16.0.0/16 than 172.16.255.255, 172.17.255.255, 
172.18.255.255 ... 172.31.255.255

-------------------------------------------------------
Date: Sun 11/03/2002 at 11:09       By: None
Obviously, what is required is a generic "list of netmasks to ban", so that 
users can add custom netmasks...



CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1579&group_id=1409

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/