aMule Forum

English => aMule Help => Topic started by: paolinux on December 15, 2004, 11:48:54 AM

Title: Why cannot I use the port 22 as Client TCP port ?
Post by: paolinux on December 15, 2004, 11:48:54 AM

Hi all,

I am behind a departmental firewall (and of course I can't change its configuration) that accepts connections from outside only on port 22 (usually used from SSH).

To avoid getting a LOWID, with xMule I was successful in disabling ssh demon and in setting xMule's client TCP port to 22. Unfortunately, with aMule it looks like it is impossible to choose any port below 80.

Is that true ?

Why did you adopt this policy ?

Is there any workaround ?

Thanks a lot!  :baby:

Paolo

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: thepolish on December 15, 2004, 11:58:06 AM

Hi,

Just to ask you a question: Do u think the administrator of the department firewall will let u use the 22 port, (or any other < 1024 port) for aMule without any problem ? If i was, i surely won't...

You d better find a workaround for cops :D

Thepolish

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: paolinux on December 15, 2004, 12:01:23 PM

yes,

as I wrote with xmule, it works greatly. The firewall simple closes ports but it does not analyze the traffic  :D

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: thepolish on December 15, 2004, 01:57:21 PM

I cannot answer u on the technical aspect, Kry should, but it was just to warn u  on the political aspect :)

p2p doesnt have a good reputation, and if u take the 22 ports bandwith with mule pakets, u will make network admins even more angry against it...

Thepolish

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: deltaHF on December 15, 2004, 07:46:02 PM

maybe i'll change it tomorrow .. but remember - running amule as root is unsecure

cheers

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: Jacobo221 on December 16, 2004, 02:03:55 AM

deltaHF, please do not change other things than that in muuli.wdr
I have lots of changes in my muuli.wdr waiting for rc8 to commit ;)

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: deltaHF on December 16, 2004, 02:25:37 AM

then change it yourself (start from 21)  :P

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: Jacobo221 on December 16, 2004, 09:53:19 AM

"then change it yourself (start from 21)"

y system is broken and i can't use wx, so wxDesigner, same as aMule, sylpheed and others, won't launch, just crash :-(

i have no time to see whyt this is happening ;) I'm deidcated to exams :P

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: GonoszTopi on December 16, 2004, 09:04:09 PM

If you ever change it, start it from 0. Thus no more user complaining "I cannot use port ##!!!" (Where is ## is an low enough port number, just to be under what we set...)

Or increase the limit to 1024 and make amule refuse to run as root :)

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: deltaHF on December 16, 2004, 10:57:02 PM

Quote

Originally posted by GonoszTopi
Or increase the limit to 1024 and make amule refuse to run as root :)

we had it before but don't remember when i changed it.
and it got changed because of ->

Quote

Originally posted by GonoszTopi
 "I cannot use port ##!!!"

back to the roots? :P

cheers

Title: Re: Why cannot I use the port 22 as Client TCP port ?
Post by: deltaHF on December 29, 2004, 08:02:54 AM

u can use now every port you like (just get amule cvs or wait for the next release)

cheers