Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[aMuX]

I get "Kad ok" (two arrows green" when I set aMule 2.1.3 on a Mac with local IP as 192.168.1.2 (the Mac is linked to a NAT router, together with other Mac).

But I only get one arrow green (the left one; the right arrow becomes yellow with "Kad firewalled" or even red with "Kad off") if I set aMule on a Mac with local IP 192.168.1.3.

In other words, I can get the two arrows green if the Mac is on local IP 192.168.1.2, but only one arrow green if the Mac is on other local IP, like for instance 192.168.1.3.

 Is there a way to fix it (to get aMule with two green arrows on a Mac with local IP 192.168.1.3)?

I want to do it because I have two Macs (both with Mac OS X 10.4. connected to the router and Azureus 2.5.0.0 only gets fully connected (three green circles) when the computer from where it runs is on the local IP 192.168.1.2. Does aMule have the same issue or could this be fixed somehow?

Thanks.

[wuischke]

Hi aMux!

Did you forward the ports properly to the ports you use on each computer? This looks like you forgot to forward the UDP-port (default: 4672) to your 192.168.1.3 machine.

[aMuX]

Thanks. As far as I know, the ports are set OK:

Mac with aMule: left arrow green and right arrow yellow (Kad firewalled) and eventually red (Kad off):
IP: 192.168.1.3
TCP: 5662, 5665
TDP: 5665, 5672

Mac with Azureus (all green OK):
IP: 192.168.1.2
TCP: 4662, 4665
TDP: 4665, 4672

I can get aMule all green as well, but only if I set the Mac from where it runs as IP 192.168.1.2

My questions are:

1. Is this normal?

2. Is it possible to get both arrows green with aMule on a Mac with IP 192.168.1.3?

3. Any problem to run aMule on one Mac (IP 192.168.1.3) and Azureus on other (IP 192.168.1.2) when both are linked to a NAT router? I mean, to get all green OK...

Thanks again.

[lionel77]

Is it possible that even the aMule that runs on your *.2 machine is using the ports that are forwarded to your *.3 machine?

In principle, there should be no reason why aMule would work properly on the one machine but not on the other.  And the particular local ip address assigned should not matter at all. All what should matter is if the proper ports are forwarded to a given machine.

[aMuX]

Thanks. The ports are open on the Router for each Mac (IP) and then on the Mac (System Preferences/Sharing/Firewall). Each Mac has thefore inique ports open.

[lionel77]

Yes, but what I'm asking is if you also changed the ports *within aMule* appropriately on your *.3 machine.

[aMuX]

Originally posted by lionel77
Yes, but what I'm asking is if you also changed the ports *within aMule* appropriately on your *.3 machine.

Yes, I did. Even more: I have only two Macs connected to the NAT-Router and when I shut down one Mac and then boot the other one, all goes green OK. But when the two are on, only the one with the local IP ending in ".2" is the one that gets all green OK.

The Mac with local IP ending in ".3" is running aMule 2.1.3.
The Mac with local IP ending in ".2" is running Azureus 2.5.0.0.

So, it seems that Azureus and aDonkey do not like each other...

[lionel77]

Well that's really interesting now. Say, what happens when both Macs are running but Azureus is not running on the other Mac, does your *.3 Mac still get highID? If that was the case, we would really have to look at Azureus. Maybe Azureus uses up too much resources of your router, so that aMule does not function properly anymore.

You could try reducing the number of connections and the bandwidth limits in Azureus and then see if aMule works better. I don't think there is a general problem with running aMule and Azureus on the same network, occasionally, I run both Azureus and aMule on my own machine, and don't recall ever having had any problems.

[aMuX]

Thanks. In such a case (Azureus off in the ".2" Mac), I get all green OK on aMule on the ".3" Mac. So the problem arises only when Azureus is running on the ".2" Mac. I have tried to reduce the Azureus oad to no avail. At least in my local network based on a NAT-Router, aMule and Azureus do not like each other...

UPDATE: when the issue arises, Azureus is all green OK on the Mac with ".2", but aMule has green the left arrow and red the right arrow of the globe (lower bar) and then the legend: Whatever (Kad: off) on the Mac with ".3".

[lionel77]

Which settings did you reduce in Azureus to reduce it's network load?

Did you include:
- Preferences->Connection->Advanced Network Settings->Max simultaneous outbound connection attempts
- Preferences->Transfer->Max connections per torrent
- Preferences->Transfer->Max connections globally
?

[aMuX]

Thanks. Yes, and left only one torrent running to check with the smallest possible load.

- Preferences->Connection->Advanced Network Settings->Max simultaneous outbound connection attempts: from 8 to 1
- Preferences->Transfer->Max connections per torrent: from 250 to 1
- Preferences->Transfer->Max connections globally: from 250 to 1

[aMuX]

UPDATE:

It may sound amazing, but I can run both aMule and Azureus in the same Mac and both of them get all green OK (aMule in seconds, and Azureus after a while; even aftter 2 hours or so, but eventually becomes all green OK).

But when one Mac runs aMule and the other Azureus in the same local network connected to an ADSL-Router with NAT on an ADSL 2+ line (16 Mbps download/1 Mbps upload), then only the Mac having a local IP ending on ".2" gets all green for aMule (or Azurerus). The other Mac gets yellow or red for Azurerus (or aMule) and has an IP ending on ".3". The router always ends on ".1".

Could that be fixed? Thanks.