Re: [Mldonkey-users] Possibility to ignore reserved IP servers?

[Goswin Brederlow]

Stefan Stammler <address@hidden> writes:

> I regularly detect some server entries having an IP address starting
> with "192.168." in the server list. mldonkey keeps trying to connect
> to those servers, although it's obvious it will never get any
> connection.

As a workaround block them in your firewall so any connect attempt
immediatly fails.

There are 3 such networks specified in RFC1819:
     10.0.0.0        -   10.255.255.255  (10/8 prefix)
     172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
     192.168.0.0     -   192.168.255.255 (192.168/16 prefix)

> Is there a possibility to prevent mldonkey from connecting to certain
> IP ranges? If not, wouldn't this be a nice feature, at least as a
> triggerable config option (i.e. "no_reserved_ip_servers")?

They are called rfc1918 network or private networks and the default
hsould be to forget any such IPs that are not on the clients own
network with an option to disable it.


While were at it, I would like filtering of IPs extending over those
rfc1918 networks.

IP:Port filter: The DFN blocks the normal donkey ports, so any IP:Port
                with the default port can't be connected. I would like
                to filter those out.

DNS filter: Many servers are on dialup connections. I would like to
            forget any *.dip.t-dialin.net server/clients after a short
            time or after an unsuccessful connect attempt. The dynamic
            IPs should be made much more volatile than static ones.

MfG
        Goswin