aMule Bug Tracker - aMule
View Issue Details
0000382aMuleExternal Connpublic2005-04-21 17:122005-04-22 13:54
Hetfield 
Kry 
normalmajoralways
closedreopened 
SVN 
 
0000382: why amule (amuled too) keeps using an unix socket for external connection ?
and...why it binds *:4712 and has no possibility to set the listening tcp socket
No tags attached.
Issue History
2005-04-21 17:12HetfieldNew Issue
2005-04-21 17:14HetfieldNote Added: 0000881
2005-04-22 00:03KryStatusnew => assigned
2005-04-22 00:03KryAssigned To => Kry
2005-04-22 00:03KryStatusassigned => closed
2005-04-22 00:03KryNote Added: 0000885
2005-04-22 11:28HetfieldStatusclosed => feedback
2005-04-22 11:28HetfieldResolutionopen => reopened
2005-04-22 11:28HetfieldNote Added: 0000893
2005-04-22 13:54KryStatusfeedback => closed
2005-04-22 13:54KryNote Added: 0000901

Notes
(0000881)
Hetfield   
2005-04-21 17:14   
sorry for buggy reports, i'm using a bugged framebuffer (no X) browser
(0000885)
Kry   
2005-04-22 00:03   
aMule does not use a unix socket for EC

aMule has an option to change the EC port.
(0000893)
Hetfield   
2005-04-22 11:28   
wait wait...

i meant... not the port but the listen address

actually if you check netstat you find:
*: <port you can change>

ok...but we should let people set a listening address like: 127.0.0.1

so netstat will show: 127.0.0.1:<port>

why amule EC should be opened to whole world by default?
you need firewall to stop that bla bla bla....
(0000901)
Kry   
2005-04-22 13:54   
Is not my problem if people can't use a firewall properly when they want stuff to be closed.