DMB04 Wrote:
Anyone care to explain to me how to fix my firewall issues? I can't browse certain people's files because I'm on a linksys router. Something about opening up a port, right?
Before I was on a router Soulseek was nothing less than amazing. Even with these issues it rarely lets me down.
I got the new Daft Punk queued up!
Cut and paste from old thread, hope it helps:
There have been problems with slsk but today was great for stuff with a bunch of obner types on-line.
http://forums.slsknet.org/BB2/viewtopic ... sc&start=0Quote:
After such an exchange of kind words, maybe I can add my point of view?
Soulseek 155 is a major evolution regarding the internal engine of the client. Many things have been changed.
Many things except the search system for example. That part of the code hasn't been changed at all, not even the smallest bytes or bit.
What has change and is related to search is:
- Random listening port. 2234 is not the default port anymore. Make sure you forward the port your Soulseek is configured to use. If Soulseek 155 detects you are upgrading from 152 or older, it will default itself to 2234 to avoid headaches. You can then change that setting, if you like, in the General Options panel
- Different executable. Sounds silly but slsk.exe has changed in size and content. Many firewall will default to block until you reset your settings for that application. Some firewall calls this action "Refresh"
- Overlapped Socket manager. This is a major change, it allows the client to be extremelly effective in dealing with hundred of simultaneous connections. We have found that some poorly written LSP (plugin for network interface in Windows) can't cope with that. The X-Fire Instant Messaging application installs one of those LSP. Crash or poor performance will happend if you keep it installed while running Soulseek. Its not Soulseek's fault, we are doing everything the way it should but third-party applications can impact your overal experience
- "lowid" client like they would say on the eDonkey network. We have an increasing number of users with non-open port. Either because they cant figure out what is a port, how to open it or for security reason but it's a reality. Getting these client to participate actively into the Network is more difficult and it may explain why the amount of global results as lowered lately. Hopefully, to help with this situation, we have introduced the UPnP manager that will help many people to set up their port right without fiddling with their router for 2 weeks.
- Server Search Skipping. Non-privileged users searches are not sent to every supernodes on the network. Only a small subset, constantly changing every few seconds, get the search and replicate it to their child. Why? Because that's the only way to do it performance wise, there is just too many searches every seconds to send them to everybody, the server would (and has in the past) just collapse under the load. This isn't a new 155 feature, it has been there for almost a year now but the tuning is now much more dynamic. According to the server load, your searches will be sent to more or less supernodes. During peak hours, you will get fewer results and at night, much more. That's the price to pay for a real-time community where everybody can talk to everybody and participate in chat rooms. Please note that Userlist search and Room search *do not use search skipping*
That was my point of view. Basically the Global Search is not going to get any better soon, it will even eventually go worse as more users get on board. Hopefully in 155 you now have new tools for much more efficient searches than in the past: Userlist and Room search.
Also is your router set up right?
http://testic.demon.co.uk/slsk-howto/
