I'm still trying to get attention from some knowledgeable person.I don't like your tone, pal, and I doubt somebody who can't get it running himself should try to coach new users. ::)
Failing so far.
Has any Ubuntu or Debian (or Linux) user successfully used a D-Link DIR-300 router to port forward and then received a ED2K high ID?Did you use different ports for TCP and UDP ?
Sorry about the tone.I'm still trying to get attention from some knowledgeable person.I don't like your tone, pal, and I doubt somebody who can't get it running himself should try to coach new users. ::)
Failing so far.
If I read ZioNemo's post correctly, he similarly was not able to get a high ID using an emule on wine approach
I do sincerely apologize about the tone.Easy, man. I just told you my opinion, and everything is cool. 8)
when I'm given the "did You remember to insert the plug in the wall before turning on your computer?" routine.The plug in the wall (or something similar) is very often the very reason. So we have to try simple things first, then move on to more complicated ones. And it's usually impossible to guess a users level of knowledge from a few posts.
my command of the English language might just be worse than I like to thinkYour English is fine, just like that of all people who express this concern. :)
(English isn't my first language)Welcome to the club. There's hardly any native speaker here.
I sat up the same ports in both cases (it is not exactly possible, but I went for "closest").A TCP port for other clients to connect to you, and a UDP port for Kad. Same both for eMule and aMule. The server UDP port is not so important.
Presumably, absent NAT, port forwarding is required.
- Or disable NAT on your router and forward the correct ports on your modem to the machine running aMule. This way you don't have to configure your router to add additional ports for other programs.
Modem | Router | |
Situation 1: | aMule ports forwarded to computer | Access point, NAT off, no port forwarding |
Situation 2: | aMule ports forwarded to router | Router, NAT on, ports forwarded to computer |
Local IP | Protocol | Port | Comment | Enable | Remote Host | Port | Interface |
192.168.1.4 | TCP | 4662 | amule | Enable | WAN IP or empty | 4462 | --- |
192.168.1.4 | TCP | 4465 | amule | Enable | WAN IP or empty | 4462 | --- |
192.168.1.4 | UDP | 4463 | amule | Enable | WAN IP or empty | 4462 | --- |
Modem Router Situation 1: aMule ports forwarded to computer Access point, NAT off, no port forwarding Situation 2: aMule ports forwarded to router Router, NAT on, ports forwarded to computer
I will explain for situation 1. In the port forwarding list, Local IP means the IP address of your computer. Remote Host means the WAN IP of your modem. Since you said you have a dynamic WAN IP you could also also try to leave this empty. The list would then show as follows:
Local IP Protocol Port Comment Enable Remote Host Port Interface 192.168.1.4 TCP 4662 amule Enable WAN IP or empty 4462 --- 192.168.1.4 TCP 4465 amule Enable WAN IP or empty 4462 --- 192.168.1.4 UDP 4463 amule Enable WAN IP or empty 4462 ---
Is there any choice you can make at the Interface column?
nc -l <port>
It will listen to any tcp port you specify. Forward the tcp port and then run the test tool for that port.