[Mldonkey-users] No Overnet peers

[Garvin Hicking]

Hi!


Ever since I am using mldonkey I never successfully connected to any  
overnet peer. I experimented a lot with mldonkey 2.00 with the help of the  
donkey-forum but didn't really succeed.

Now I tried again with 20021129a pango-patched release because I saw so  
many people who got the thing to work with overnet.

My linux-box is used as a router and has no ports blacklisted. Few ports  
are bound to LAN-IPs, but none between 4660 and 4670. I get HighID- 
Connections to Donkey-Servers, so I guess this is correctly so far. I use  
a Debian 3.0 woody system with a 2.4.19 kernel (single processor).

I use a very small serverlist with about 200 servers and cleanup the  
servers.ini every mldonkey-restart (which is about once every 2 days  
because sometimes I have to get all the bandwidth available). The servers  
which are listed there mostly work correclty and let me connect to them.

My main options in my downloads.ini are:

verbose_overnet                 true
max_hard_upload_rate            5
max_hard_download_rate          15
port                            4662
max_opened_connections          300
max_upload_slots                10
propagate_sources               true
propagate_servers               true
max_sources_per_file            1500
protocol_version                61
new_upload_system               true
overnet_port                    4669
overnet_max_known_peers         2000
overnet_search_keyword          true
overnet_search_sources          true
overnet_max_connected_peers     50
overnet_search_timeout          120
overnet_max_search_hits         200
overnet_max_waiting_peers       50

When I use the command 'ovweb' I can get the following entries in my  
Logfile:

?C?C?C?C-cQUERY URL http://overnet.wiretapped.us/contact.ocl
Resolving overnet.wiretapped.us ...done
-!C-cLast upload slot reserved for creditors
?Csend_small_block 185298944 4096
U[IN]-!C-c?CLast upload slot reserved for creditors
Resolving 217.3.8.161 ...done
Sending UDP to 217.3.8.161:10494
ascii: [(227)(10) ~ & {(232)(4) M(171)(215)(146)(19) ! %  (251) L u(0)(0)(0)(0) 
}(174)(0)]
dec: 
[(227)(10)(126)(38)(123)(232)(4)(77)(171)(215)(146)(19)(33)(37)(32)(251)(76)(117)(0)(0)(0)(0)(125)(174)(0)]

Resolving 80.63.103.12 ...done
Sending UDP to 80.63.103.12:12467
ascii: [(227)(10) ~ & {(232)(4) M(171)(215)(146)(19) ! %  (251) L u(0)(0)(0)(0) 
}(174)(0)]
dec: 
[(227)(10)(126)(38)(123)(232)(4)(77)(171)(215)(146)(19)(33)(37)(32)(251)(76)(117)(0)(0)(0)(0)(125)(174)(0)]

Resolving 212.202.178.188 ...done
Sending UDP to 212.202.178.188:5649
ascii: [(227)(10) ~ & {(232)(4) M(171)(215)(146)(19) ! %  (251) L u(0)(0)(0)(0) 
}(174)(0)]
dec: 
[(227)(10)(126)(38)(123)(232)(4)(77)(171)(215)(146)(19)(33)(37)(32)(251)(76)(117)(0)(0)(0)(0)(125)(174)(0)]

and so on, for each ov the listed boot-nodes. I get the same results if I  
manually use 'boot <ip> <port>'.

Ovstats returns:

Overnet statistics:
  Connected Peers: 0
  Search hits: 0
  Source hits: 0

client_stats returns:

Uptime: 3798 seconds (0 days, 1 hours, 3 minutes)

Total seens: 1678
           eDonkey: 5 (0.30 %)
      mldonkey 1.x: 153 (9.12 %)
      mldonkey 2.x: 35 (2.09 %)
           Overnet: 0 (0.00 %)
         old eMule: 0 (0.00 %)
         new eMule: 1485 (88.50 %)
            server: 0 (0.00 %)

Total filerequests: 6403
      From eDonkey: 28 (0.44 %)
 From mldonkey 1.x: 3812 (59.53 %)
 From mldonkey 2.x: 594 (9.28 %)
      From Overnet: 0 (0.00 %)
    From old eMule: 0 (0.00 %)
    From new eMule: 1969 (30.75 %)
       From server: 0 (0.00 %)

Total downloads: 5030459
      From eDonkey: 2490939 (49.52 %)
 From mldonkey 1.x: 0 (0.00 %)
 From mldonkey 2.x: 0 (0.00 %)
      From Overnet: 0 (0.00 %)
    From old eMule: 0 (0.00 %)
    From new eMule: 2539520 (50.48 %)
       From server: 0 (0.00 %)

Total uploads: 10432512
        To eDonkey: 0 (0.00 %)
   To mldonkey 1.x: 1159168 (11.11 %)
   To mldonkey 2.x: 0 (0.00 %)
        To Overnet: 0 (0.00 %)
      To old eMule: 0 (0.00 %)
      To new eMule: 9273344 (88.89 %)
         To server: 0 (0.00 %)


And my servers.ini contains not a single overnet-peer in overnet_peers = [] - 
this is, what concerns me most.

Is something wrong with my number of connections? Maybe none of the peers  
get listed because mldonkey does something different the whole time? I can  
get not a single clue out of the logfiles...anything I could have to  
lookout for?

Thanks for any advices. Would like to get this thing worked somehow. I  
also once compiled my own 2.00 version, tried 3 different pango-binary so  
I think this is not a binary-file issue any more...