~> ov_boot <peer ip> <peer udp port>
Each Overnet peer maintains a local list of known peer addresses, that is updated with addresses found during normal peer communications (searches, publishing, etc.).
Once you know some valid peer addresses, this is fully automatic; But at first you need one valid address to start from, manually adding that address is called \"booting\" or \"bootstrapping\" the Overnet network ().
Things to try :
Check  for peers addresses.
Older bootstrap addresses :
~> ov_boot overnet.dyndns.org 4665%%%
~> ov_boot overnet.gotdns.com 4665%%%
~> ov_boot overnet.no-ip.com 4664%%%
~> ov_boot overnetbc.d2g.com 5298%%%
~> ov_boot dvdmag.dns2go.com 10247%%%
~> ov_boot nictuku.kicks-ass.net 4664%%%
~> ov_boot dboy.dnip.net 10861%%%
~> ov_boot 22.214.171.124 8368%%%
~> ov_boot greed.zapto.org 4780%%%
~> ov_boot fudge.punkcookies.com 12000
Even if one address is enough, starting from a larger list of peers using the ov_web command should help building a good list of peers faster.
This command used to be called boot prior to MLdonkey 2.5-23.