aMule Forum
English => aMule Help => Topic started by: heuving on January 03, 2006, 09:14:39 AM
-
I have problems using amulegui through a firewall.
If I start amulegui on the same computer I'm using amule, everything is fine. It shows me the current down- and uploads, I can enter searches etc.
But if I'm using amulegui from another computer outside of the LAN, I get an initial connection and the program shows me the actual status, but it get's never updated.
If I enter a search, there's a new tab for my query, but it doesn't show any results.
On the firewall I opened the port 6712. What do I miss?
-
kinda teh same problem here aswell, alltho mine has no firewall inbetween only a wlan access point...
if i connect the lan cable works just fine from the same pc, but I am pretty sure this worked over wlan at least a couple days/weeks ago...
-
what version amulegui are we talking about - linux or win ?
stefanero: please explain your setup little more. I understand that it works thru localhost. What about lan ?
-
lan works aswell but wireless-lan does not anymore....
from winXP to linux
-
Originally posted by lfroen
what version amulegui are we talking about - linux or win ?
Both are linux. The box with amule running is a SuSE9.0 with wxGTK2.4, the other one
a SuSE9.2 with a freshly compiled wxWidgets2.6.2. On both I compiled 2.1.0.
-
stefanero: if I see correctly, the only difference between lan vs wlan is bandwidth/latency. Is that correct ?
heuving: can you describe your network setup in little more detail ?
-
yup, its teh same pc once connected thruw wlan and once lan....
over wlan on my side it loads teh config file, and also the server.met from teh amule running on linux, but thats about it...
-
It could very well be possible, that my problems (http://forum.amule.org/thread.php?postid=47333#post47333) with amulegui on WinXP are based on the same things.
I have direct LAN connection to my Debian box, but all the problems I experience seem to come from some network troubles. Maybe there is some timing dependent bug in the EC protocol. That could very well explain everything!
-
well lfroen told my my w-lan access point sux, so I resetted it a little, and all of the sudden my remote-gui works again
I guess an uptime of 58days for an d-link access point is a little to much :]
-
Maybe there is some timing dependent bug in the EC protocol
EC have part where it tries to avoid network congestion. When EC "thinks" that network is slow - it stops sending update requests.
Quite possible this part is buggy somewhere.
-
@Ifroen
If you think of my problem with the "socket would block" error message, I think we can take such network timing issues for granted.
If you have any suggestions or some patches to produce some helpful trace output, I would try it.
The problem seems to be highly reproducible in my environment, though I have no idea, why! I normally don't have any network troubles except from time to time the usual things with SAMBA shares.
I'm on standard 100 Mbit/s-Ethernet with a 24-port-Switch for all of my equipment. No WLAN, no exotic hardware active (at the moment :-) ).
-
Radek: do you still have this error in current svn snapshot ?
-
@Ifroen
No, this error (or to be precise: the error message) seems to be gone.
I just mentioned this error here again, because it seems to hint in the same direction: that at my place some (imagined ?) network congestion in internal LAN has effects on EC (or general socket communication).
And in my mind I make the connection to this other problems I am having with the communication of amulegui to amuled. See this post (http://forum.amule.org/thread.php?postid=47333#post47333).
It seems to me, as if the communication between amulegui and amuled is somehow disturbed. But there are no error messages, I could see. I didn't try the current snapshots, though. I'm still using 2.1.0