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

[spiralvoice]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

/**************************************************************************/
[bugs #1579] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 19:23 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice






/**************************************************************************/
[bugs #1579] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=1579>
Project: mldonkey, a free e-Donkey client
Submitted by: 0
On: Sat 11/02/2002 at 06:17

Category:  Core
Severity:  5 - Average
Item Group:  None
Resolution:  None
Assigned to:  None
Status:  Closed
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: Tue 12/02/2003 at 19:23       By: spiralvoice
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice

-------------------------------------------------------
Date: Thu 09/11/2003 at 12:07       By: None
***CORRECTIONS***



82.0.0.0/8 now has a valid assigment (whois.ripe.net)

222.0.0.0/8 now has a valid assignment (whois.apnic.net)





-------------------------------------------------------
Date: Thu 07/03/2003 at 13: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 12:09       By: None
Obviously, what is required is a generic "list of netmasks to ban", so that 
users can add custom netmasks...














For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=1579>

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