Gnutella Forums - CPU usage

Gnutella Forums (https://www.gnutellaforums.com/)

- Support (https://www.gnutellaforums.com/support/)

- - CPU usage (https://www.gnutellaforums.com/support/7902-cpu-usage.html)

just remember. gnutella is all about sharing. so you should share to anyone regardless of who they are or what there circumstances. you might feel differently if you were a student who's network administrator blocked that port dont you think?

Quote:

Originally posted by mrgone4662

True, but I find it difficult to see much benefit in that. Though I'm sure all the poor students who's admins are blocking 6346 would love me for using a different port.

Yes good idea!

Morgwen

Yeah Morgwen, important feature!
Choosing another port then 6346 is a great feature of Gnutella, it is much harder to get blocked if many do. Actually, I run my Gnutella on port 443 and/or 563, this allows ppl behind a SOCKS or especially behind a HTTP proxy (e.g. a simple 'squid') to download files from me. Well explanation is tricky, the squid default configuration of Linux distributions allows to tunnel connections to this destination ports.

acl SSL_ports port 443 563
http_access deny CONNECT !SSL_ports

So, if an official host on your university runs a squid, you're fine and could download from me (assuming your Gnutella client has a buildin HTTP1.1 proxy support, Godxblue add this to the TODO list plz). Think geek!

Greets, Moak

Hehe...

Moak I have a "GOOD" advisor! ;)

Are there ports which we cannot use, because they are reserverd for other applications?

Morgwen

Quote:

Are there ports which we cannot use, because they are reserverd for other applications?

Yes and No.

'Yes' means some ports are reserved, but 'No' means as long as no service is running on your local PC on such a port you can use those reserved ports too.

Okay, this is tricky freestyle (some will call it abuse), but using such an unused "reserved port" can fool most firewalls. Yes, still many firewalls are stupid and filter static (on ports) and not dynamic (on protocoll). Stupid may be the wrong phrase, static firewalls are cheap in CPU consumption and wide spread, dynamic firewalls with full state inspectation and application gateways are new and need more CPU. Also application gateways (e.g. HTTP proxies) can be abused, see my post above. However, using a so called "reserved port" opens possibilities! Oh - before some blocked readers at a university/school get excited: The typical high traffic from Gnutella always points back to your local LAN IP, so the admin of your local network can always track you back no matter how stupid he or the firewall is. Don't expect that downloading of GBs will remain undiscovered, grin.

GodxBlue: I suggest to add to TODO list: choose_port (manual user input or INI), force_ip (manual user input or INI), auto_force_ip (via v0.6 connect handshake), auto_choose_port (if choosen port is allready in use, scan for the next free one)

/Moak

Quote:

Originally posted by RaaF
And I saw my IP twice as beeing connected to in the connections screen with port nrs 6346 and 1227 ( not really shure about the port nrs), but I disconnected from myself :p and it did not happen again.

This bug should be fixed!

Please report if this happen again!

Thank you! :)

Morgwen

I am running XP Pro on a dual 800Mhz system. Peeranha consistently consumes around 40% of both processors. I don't really mind it because it works so well.

I too have seen my own system in the active connections. At least it didn't try to download from itself :D .

hi,

please download the new PEERanha 1.41 beta! Is lower CPU-Power needed? Please send a report to me.

- godXBlue

1.4.1 Beta fails as soon as it is loaded. I get the startup screen and then it crashes.

hi colonist,

did you got the beta from 10.02.?
please send me the text og the error dialog !
Which OS do you use?

- godXBlue