aMule Forum
English => aMule Help => Topic started by: dukeofnukem on March 28, 2006, 11:06:55 AM
-
Alohá!
Just installed amuled 2.1.1-2 from the debian sarge apt-sources along with amule (monolithic), made my settings, imported my ed2k-temp-files, everything looking great.
Really nice work, I used to run the smurfified ed2k-clcs but this is looking good.
Here's the problem though:
Trying to remote control amuled (as I don't plan on installing any X on the final destination machine) and reading around the wiki a bit, I decided to go for amuleWEB instead of remoteGUI.
When starting up amuled (or amule for that matter) the status reports the socket listening, so does netstat and there is communication between my browser and the amuleWEB component
playground:~# tcpdump -ntvi eth0 | grep 4712
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
IP (tos 0x0, ttl 128, id 50965, offset 0, flags [DF], length: 40) 172.16.32.42.1365 > 172.16.32.253.4712: F [tcp sum ok] 2742359292:2742359292(0) ack 384643285 win 65535
IP (tos 0x0, ttl 64, id 57334, offset 0, flags [DF], length: 40) 172.16.32.253.4712 > 172.16.32.42.1365: F [tcp sum ok] 1:1(0) ack 1 win 6432
IP (tos 0x0, ttl 128, id 50966, offset 0, flags [DF], length: 40) 172.16.32.42.1365 > 172.16.32.253.4712: . [tcp sum ok] ack 2 win 65535
IP (tos 0x0, ttl 128, id 50983, offset 0, flags [DF], length: 48) 172.16.32.42.1395 > 172.16.32.253.4712: S [tcp sum ok] 3801684527:3801684527(0) win 65535
IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 48) 172.16.32.253.4712 > 172.16.32.42.1395: S [tcp sum ok] 1070212150:1070212150(0) ack 3801684528 win 5840
IP (tos 0x0, ttl 128, id 50984, offset 0, flags [DF], length: 40) 172.16.32.42.1395 > 172.16.32.253.4712: . [tcp sum ok] ack 1 win 65535
IP (tos 0x0, ttl 128, id 50985, offset 0, flags [DF], length: 450) 172.16.32.42.1395 > 172.16.32.253.4712: P 1:411(410) ack 1 win 65535
IP (tos 0x0, ttl 64, id 1496, offset 0, flags [DF], length: 40) 172.16.32.253.4712 > 172.16.32.42.1395: . [tcp sum ok] ack 411 win 6432
unfortunately the page stays blank.
Is this the same problem with broken EC connection between amuleWEB and amule(d) that's haunting the CVS builds? Or has anybody sucessfully installed and used amuled with amuleWEB from the current debian sarge apt sources?
THX
-
I guess you're talking about the packages from amule-debian.dyndns.org, those are my packages and I just checked it:amuleweb, amulecmd and amuleguiwork fine here with both amule and amuled and I haven't heard of such a problem until now...
-
Yep, I added deb http://amule-debian.dyndns.org/ debian/ to my sources list and simply aptituded them in :-)
On the testing machine I have icewm running through vncserver as the X environment, RAM is 512MB, Kernel 2.6.8-3-686-SMP.
- Does it possibly have to do with SMP?
- Does amuleWEB require anything on the client side (Firefox 1.5.1, JavaVM 1.5.0.06 on XP up2date)
- When making settings with amule, those are written to a common config and used by amuled as well, correct?
- Is there a way to observe whether amuleWEB connects to amuled? Didn't see anything listening on 4711, just 4712
Thanks for Your help
-
Originally posted by dukeofnukem
- Does it possibly have to do with SMP?
No idea, I'm one of those unlucky guys who still have to bear with a single-CPU single-core non-hyperthreading system ^^
- Does amuleWEB require anything on the client side (Firefox 1.5.1, JavaVM 1.5.0.06 on XP up2date)
That should be ok.[/quote]
- When making settings with amule, those are written to a common config and used by amuled as well, correct?
Yes, both use ~/.aMule/amule.conf to save their settings, so as long as they are run by the same user they use the same settings.
- Is there a way to observe whether amuleWEB connects to amuled? Didn't see anything listening on 4711, just 4712
Did you enable "Run amuleweb on startup"? Then it should be listening on 4711. If not try starting amuleweb manually to see the output.
-
if its still not working post your
amule.conf adn remote.conf if you have one here, I will have a look
-
No idea, I'm one of those unlucky guys who still have to bear with a single-CPU single-core non-hyperthreading system ^^
That system is a dual Celeron Mendocino 300 oc-ed to 450 by using a FSB of 100MHZ instead of the default 66MHZ (tape off Pin B21). In order to make the Celeron SMP-capable You still had to drill into the processor die and connect a pipeline to the Socket with a thin wire - those were adventurous days. Back then though a Celeron 300 would cost DM 130 while a PII 450 came to around DM 1200 a piece, so it was worth it :] And I was lucky enough being able to test around a dozen CPUs with a looped kernel compile (2.2 was fresh then) and select two that ran stable at the original voltage. These days I guess I'd simply work the hours I spent testing and buy myself the next bigger thing. Way less cool but much more convenient 8)
Did you enable "Run amuleweb on startup"?
Yep
If not try starting amuleweb manually to see the output.
Will try that when I get home.
regards & l8a
-
Originally posted by stefanero
if its still not working post your
amule.conf adn remote.conf if you have one here, I will have a look
Will do that too :)
Thanks guys!
-
btw its not like thedude0001 said, when you lunch amuleweb seperate, it uses remote.conf instead of amule.conf
there are some options for amuleweb, to create a remote.conf file from amule.conf if you need to run it seperatly try --help
-
Eureka!
I have absolutely no idea what happened but when I booted up my testing system yesterday night and started amule, there was the socket listening on port 4711 and everything was working the way it was supposed to right off the bat.
Fiddled my blocklist into place, found a serverlist but no nodes.dat (difficult these days, not only razorback (and gruk for that matter) are down but I couldn't connect to ocbmaurice or overnet2000 either) but that didn't matter as the donkeyserver was my bootstrapping pal and off it went - rollout to the final destination
Happy as a clam I'll observe the performance and sure will be back with lots of questions soon.
Actually, here's one:
- Is there any way to verify / monitor the blocklist functionality? I can see that starting up the client takes a few seconds longer during which supposedly the 9,4MB list is put into place but is there a log or some other output where one can see the bad guys being kept out?
BTW, I'm really relieved to see the speed with which a list of that size is loaded, inserting the same list via iptables rules takes nearly 36h (!) on an AMD 1600+ as for every insertion the complete ruleset has to be retrieved from Kernelspace, the rule inserted and everything written back. The resulting ruleset is so big that I can't really use iptables-save / -restore as during the period the saved ruleset is restored (15min) there is simply no network connectivity at all (in addition to the fact that those functions are somewhat buggy and sometimes produce very bad things). There also is the problem of changing IPs on a dial-up connection but that can be overcome with a small script in /etc/ppp/ip-up.d/ as long as the external IP isn't used too much in the rest of the ruleset so You would have to flush chains or even whole tables... nevermind, I'm just so happy to see this solved in such a convenient way.
- Is there a Torrent-plugin? Sure, aMule is not Shareaza, I'm just wondering as I'm still looking for a full featured client that doesn't require X or one terminal window / screen per torrent. Yes, I could just kill the process of a finished dl when using the clcs but I like doing things cleanly :P
Thanks for the warm welcome guys, think my recommendation concerning ed2k clients has just changed from the smurfified 1.3.0 to aMule :]
-
Originally posted by dukeofnukem
- Is there a Torrent-plugin? Sure, aMule is not Shareaza, I'm just wondering as I'm still looking for a full featured client that doesn't require X or one terminal window / screen per torrent. Yes, I could just kill the process of a finished dl when using the clcs but I like doing things cleanly :P
No, there isn't. And it's not planned to do. amule is an ed2k client. Period. ^^
-
about the IP-Filter test, you can try to connect to blocked servers like
64.34.* or some other know fake servers, if you cannot connect -> it works
-
Sorry, wasn't intended to be understood as a request.
BT has a somewhat different audience, like soulseek.
I just like the style and true *NIX-ness of aMule so much after coming from a crappy windows port client (that one poor soul mended for the penguins out there to at least make it usable). Take it as a compliment.
No offense meant.