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