What I have found is... when doing tests offline, Bearshare stays connected to XoloX, when connected though, I get dropped very quickly... I think XoloX is dropping the handshake in favor of routing queries or downloading files... so BS disconnects. (remember I'm on a 31200 connection, broadband useres may not experience this.)

For my tests I shared a number of files, including all the Win98_##.CAB files from my 98SE CD that = 1802240 bytes (The size of a DMF formatted disk) with which I re-confirmed my note that XoloX only displays the first file of a given size from a single host that matches a query.

I also re-confirmd that XoloX returns a max of 30 hits at a time (not 100) and that for a given query, will return the same 30 hits every time. A better method than starting at the beginning of the shared files index each time a query comes in would be to save the end position and start at the next entry, starting over from the beggining when you reach the end. (but not going past 'maxreturns' or it's current start point)

Last point of notable mention is that XoloX will 1) Let a client connect to it multiple times, allowing outgoing network connections to computers that it already has inbound network connections to, and 2) will let a client make multiple connections to it.

In bearshare I was able to have

Localhost = IN
localhost = OUT
ACB7205E.ipt.aol.com = OUT
172.183.32.94 = OUT

Those last two are the same. BTW, with AOL you don't even need to do a DNS to get an IP... just split up the hostmask ... AC.B7.20.5E is hex for 172.183.32.94 (Nice and easy, but impossible to put up bans for without blocking the entire AOL user base :P)


Expect more bug reporting regarding actual networks and proxies and stuff from me soon, as I have been given another (somewhat dead) computer with which I shall network with my own as soon as I manage to get it working and get a network card for it *bwahaha*