to share or not to share is still the question

[sharer!]

have installed the dual patch, have gone primary, have upped allocated bandwidth to the winmx peer network to 11 Kb/s outgoing and 16.6 incoming too , installed the new blocklist for peer guardian 2 , and am not using mx monitor here either for all its 'who is' callouts.

am still hearing ALL PEOPLE ON PRIMARY CONNECTION UNSHARE FILES !!

PLEASE UNSHARE ALL FILES AND STOP ANY U/L AND D/L YOU MAY HAVE RUNNING...WinMX needs to be stabilized before we can begin to share files again.Your cooperation is needed to speed this along,Thank You for helping in this effort  ...

 stories the servers that have been working may crash !
come on guys, whats the REAL STORY here

[sharer!]

it took some thinking. concerns the peer cache servers become overloaded and crash is an unknown. I'm no genius but know some.

true: once a connection is established it becomes a direct connection.
files DO NOT run through the cache servers after introducing 2 pc's.

true: people in your cue "waiting for network reply" is handled by those     cache servers, verifying the availability periodically, for everyone cued.

true: opening folders to a friend so they can browse and connect direct for the transfer and then unsharing the folder will keep long cues from forming, and also lighten load to caches "waiting for network reply"

true: files you are waiting for with auto find sources time set LOW like every 10 minutes, is handled by the peer cache servers too.

true: setting longer times for auto find sources on files in upper transfer screen will also lighten loadings to the peer cache servers for you cueing.

true: having fewer files in cue and cued to fewer people will also lighten loadings in your "waiting for network reply" to those cache servers.

true: MX monitor with all it's 'who is' calls is also running through those cache servers to check somewhat who is cueing your files.

IF- there IS a real concern that the peer cache servers will crash for becoming overloaded, THEN- these are real considerations for users.

so to all you users running around telling everyone to ..
STOP SHARING AND STOP ALL FILE TRANSFERS...
maybe you need to wake up that theres NO POINT in being
IN WinMX AT ALL if there is NOT files being shared.

WinMX is a filesharing community !
you either need to stop telling people that and just leave mx youself,
OR maybe consider REAL WAYS MENTIONED to lighten loadings
to those precious peer cache servers. think about it, I did.

that the cache servers might overload and crash may only be a rumor
and I'm sure as hell glad the network is running again now.
IF - you are worried about the 'nasty organizations' against sharing
THEN - dont leave all your goodies in plain view all the time makes sense.

MX is NOT MX without sharing FILES. so what are YOU gonna do?

[Me Here]

AMEN !!!!!!!!!  

I have only 2 things to add to this

1) Your on the right track however, it actully has even LESS to do with the peer caches then you think.

https://forum.winmxworld.com/viewtopic.php?p=2362#2362

2) if you want to lighten the load on WinMX  GET PEER GUARDIAN  found here  

https://www.winmxworld.com/

Please Add BOTH files to your lists that are also listed there for download, If your really want to help WinMX!

[kitty =^..^=]

me here

I can only connect on a secondary since I'm on a LAN, should I still get peerguardian or is that for primary connection users only?


PS: I'm glad you guys got us up and running again, I tried ares and filetopia and was getting totally frustrated because I NEED my WinMx LOL

[KM]

the real concern right now is for primary users to block the flooders, not because of the flooding, but because they are still making as many connections as they did before - but there are now nowhere near as many primary users... instead of having 2 or 3 flooders connected to each primary (leaving 9 or 10 slots free for users) it is at the point were many primaries have 9 or 10 flooders connected leaving only 1 or 2 slots free for users... which is causing a problem for secondary users as they cant connect to primaries that are full

so on secondary it doesn't really matter, but on primary it is important that the flooders clients get blocked from as many primaries as possible - using whichever method you chose...

[sharer!]

hey, for sure done all that... and peer guardian is blocking a LOT.

globix,xworks,sympatico,btcentralplus,fuzion colo,covad,DSL.net,inc, xeex, panasonic network services, alabama supercomputer network,

these arent incoming things at all !  it is all originating from this pc here
 origin local, blocked sending to thise names IP#'s at a really high frequency..  every couple seconds.  and they are through my port designated for WinMX, which is not standard number either.

normally, if my machine was blocking this many hits with peer guardian
INCOMING... I'd format the machine and reload everything, maybe see 10 blocks a day. again, this is all outgoing, and constant. SPOOKY !

[mx user]

sharer!

I'm seeing mostly xeex, saavis, time warner, city of gainesville, cable & wireless, XO Communications and comverse inc.

All the addys start the same : 192.168.2.4.     only the last 4 digits are diffrent

what does this mean? what's going on?

[Me Here]

those are dangerous IP..known flooders

Its working great  

[sharer!]

did you catch what I said?

IF "they" were flooding, peer guardian would be blocking INCOMING HITS
every block I see, the SOURCE is MY PC, NOT FROM ELSEWHERE !

its working great ?!!  what kind of TROJAN is built into the WinMX program that you arent telling us about ?!

[sharer!]

I posted similar at winmx unlimited that a trojan may be buried in the win mx program trying to send outbound reports, that peer guardian was NOT blocking incoming hits.. and that we aint being told about it.

 and its not there suddenly now..  gee imagine that.

[sharer!]

I posted similar at winmx unlimited that a trojan may be buried in the win mx program trying to send outbound reports, that peer guardian was NOT blocking incoming hits.. and that we aint being told about it.

 and its not there suddenly now..  gee imagine that.

[KM]

it could be that your peer guardian is not blocking the inbound data only the response, or you could have a load of fake files waiting to download that keep trying to connect...

[sharer!]

not waiting on any fake files here at all fer sher, and peer guardian is working like its supposed to, but stopping outgoing signals every second
and only if any attempt to go primary, dont even need connect, can click to secondary and it continues rolling too. it isnt the case if starting out on secondary connection (that I can see) but from the moment I click primary
its all stopped outbound signals. and yes this is alarming.

[jabberwockey]

My PG2 is working just fine. I have a nice log of all the aforementioned flooders being blocked.

QUESTION:

When you browse someone and they have a bazillion partially downloaded files, are they flooding the network? Should they be cancelled until they finish some of those files?

[Me Here]

Only if you see alot of ones that are 0% .. those are probably files that are Fakes so never downloaded.  They however, do not pose a threat to you.. only to the user with the files.. when they look for sources.. well thousands of results a second in the transfers screen usually will crash your WinMX...

[sharer!]

maybe look again, source = my own IP# TO those destinations.
it begins instant I click to go primary before a connection is even established, trying to send OUT. can immediately swap to secondary and it continues blocking outgoing signals. not stopping incoming, outgoing!
 before primary even connects!  look again at SOURCE
 isnt that YOUR IP# there ?!

[Me Here]

as I mentioned earlier this means its working..

I am looking at mine right now ..

Name:  Globix
Source: 192.168.0.2
Destination:  204.193.128.47
Protocol: TCP
ACTION: Blocked

The reason its stated as the source is confusing and I now see your point as I look at it closer.  

But the source of the block is your machine.  Your machine is saying NO.. and its the source of the answer for request of connection.  The destination of the answer NO is the flooders.

The flooders start by asking for a connection.  That information is not what PeerGuardian is giving.. the infomation PeerGuardian IS giving in the logs is what answer it gave for the request.. NO

Hope that makes it a little clearer.. and believe me everyone in the world right now using Peerguardian sees  the information the same as you..

So again I say.... Its working great!

[sharer!]

TYVM !!

and am wanting to be able to see those requests blocked really, the tough part on that is only seeing my own IP# trying to send being blocked..
 not those incoming pings requesting connections.
 the other observation, those outgoing blocks begin instantly before any connection is even established P= or S= .  and it continues even if I immediately click for secondary connection. nonstop. this does not happen if entering mx strictly secondary.

[Me Here]

Well there are literally thousands of requests for connections when your on the internet .. as you may know.  Peerguardian just didnt see the relevance of logging all of these and shows the information about blocked or allowed connections only.

The flooders are on High speed servers.  If you do a search and Ping all results you will see that the pings are very fast.  The reason they are not showing as often or as quickly on a secondary connection is simple, thats not what they are looking for.

They attach themselves to our networks primaries waiting to do their dirty work...