Hi, I've just updated amule-daemon from a CVS debian package using apt-get under Ubuntu Server 7.10.
Here's what I did so far:
I copied my config file from a monolithic install I did as a test on another box (CVS) and replaced back the values from the previous 2.1.3 amule.conf (nothing major, just the client's name and EC password, basically)
I started the daemon, so far so good, the daemon is up, I can connect using amulecmd locally.
I installed the CVS amule-utils-gui on another remote box (also Ubuntu 7.10).
I start amulegui and I get the connection box and input the proper address and port, and password (which works under amulecmd, so I know it's the right one)
Then nothing happens.
I tried running it with --verbose, but I'm not getting anything more, except some locale error with wx (which doesn't hamper the monolithic aMule, so my guess is it's irrelevant...)
All I get from starting it in a terminal is "going to event loop..." and it just stays there.
Any thoughts? Thing is, I'm able to connect from my Windows laptop using an old windows build of the 2.1.3 remote GUI, go figure...
ETA: Installed amulecmd CVS on the remote box, and wasn't able to connect. Found out I was previously able to connect *locally* using amulecmd because I was still using the 2.1.3 version.
Bottom line: External connections to the CVS amule-daemon only seem to work using 2.1.3 stable utils (amulecmd and amulegui). When using amulecmd CVS locally *or* remotely I now get this output:
This is amulecmd CVS Thu Nov 15 07:01:55 CET 2007
Enter password for mule connection:
Creating client...
ReadPacket: packet have invalid flags 0
Connection Failed. Unable to connect to the specified host
My guess is this is the same problem preventing amulegui from working as well...