Notes |
|
(0001220)
|
rg3
|
2005-08-14 00:33
|
|
|
|
(0001223)
|
Kry
|
2005-08-14 01:19
|
|
You mean the EC port or any aMule port? |
|
|
(0001224)
|
Kry
|
2005-08-14 02:13
|
|
Ok, I just added support for opening EC and aMule ports just on selected ips.
Please test it (I did some tests, but I'd like you to try):
Open a new CVS aMule (from 14/08/2005)
Close it
open ~/.aMule/amule.conf
There are 2 lines: Address= and ECAddress=. Put there the ips (i.e. for your problem just set ECAddress=127.0.0.1)
Try connecting to EC from localhost and from outside.
And please report the results. :) |
|
|
(0001225)
|
rg3
|
2005-08-14 02:19
|
|
Thanks, I'll do some tests when I come back to my workplace and post the results. :) |
|
|
(0001226)
|
Kry
|
2005-08-14 02:49
|
|
|
|
(0001227)
|
Kry
|
2005-08-14 02:51
(edited on: 2005-08-14 07:39) |
|
P.S: Notice this is only for listening connections. Outgoing connections must be routed properly.
This is not a problem on EC, but it is on aMule, where we do connect to remote instead of beign connected.
edited on: 08-14-05 07:39 |
|
|
(0001228)
|
rg3
|
2005-08-14 12:31
|
|
Er... sorry for my bad explanation. I was referring exclusively to the EC address:port pair, eventhough I suppose being able to specify the address in other listening ports and connections would be eventually useful. I'm now rereading everything I wrote and realizing the confusion I created, sorry. |
|
|
(0001229)
|
Kry
|
2005-08-14 16:33
|
|
You did still not report :P |
|
|
(0001230)
|
rg3
|
2005-08-14 23:37
|
|
Well, Kry, a big big thanks (and $10!) for implementing it. It seems to work alright for me. I'm anticipating the next stable release. |
|
|
(0001231)
|
Kry
|
2005-08-14 23:50
|
|
|
|
(0001244)
|
Kry
|
2005-08-20 23:32
|
|
Are you still around? If you are, mind I changed the position of the item on amule.conf, so it's reset, but I added a new item on gui to set it. Make sure you set it back (by, i.e., closing amule, updating, running it again, closing it, and editing amule.conf) |
|