Print

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

[dealcorn]

- 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.

While I do not know how to edit a prior post to correct  a forwarded port #  from 4462 to 4662, you are suggesting that I do what is already done.  NAT is disabled on my router (192.168.1.2).   I forwarded ports 4662 and 44662 from my  modem  (192.168.1.1) to my computer running aMule (192.168.1.4).  I configured aMule with standard client TCP  port 4662 and then verified that port 4662 was blocked.  As an alternative I then configured aMule with standard client port 44662 and then verified that port 44662 is also blocked.    As a supplemental check I then configured the router to forward  ports 1-60000 to my PC running aMule and verified that the ports 4662 and 44662  were still blocked though I performed this test with firestarter enabled with appropriate inbound policies.  My question is if I  disabled NAT on my  router and forwarded the correct ports on your modem to the machine running aMule, why is my port still blocked?

[woutermense]

	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?

[Stu Redman]

Now you've confused even me. Shouldn't it be
Local IP   Protocol      Port   Comment      Enable      Remote Host   Port   Interface
192.168.1.4   TCP   4465   amule   Enable   WAN IP or empty   4465   ---
192.168.1.4   UDP   4463   amule   Enable   WAN IP or empty   4463   ---
?

[woutermense]

You're right, I misread the TCP+3 line in the preferences panel. Of course that second line should be UDP. Since the post-modification-timeout has passed, please feel free to edit my previous post for me

[dealcorn]

	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?

Boy do I want to agree.  My router is in access point mode with NAT turned off and no ports forwarded.  The modem can not forward the dynamic WAN IP with static rule because on modem reboot to enable the rule the IP changes making the forwarding rule wrong.  However, contrary to my first impression, the modem can forward a "blank" remote host as follows.

Local          Local         Remote   Public
IP Address    Protocol Port    Comment Enable    Host    Port    Interface
192.168.1.4    TCP     4662    amule    Enable       4662    ---
192.168.1.4    TCP     4665    amule    Enable       4665    ---
192.168.1.4    UDP     4663    amule    Enable       4663    ---

The interface parameter offers choices of either "any" or "pppO".  I chose any. Prior to testing ports I started amule and verified that standard client TCP port was set to 4662 and the extended port was set to 4665.  With this configuration and firestarter turned off, http://www.amule.org/testport.php reports that ports 4662, 4663 and 4665 are blocked.

[dealcorn]

Now I am  perhaps confused but happy.   With no change to my immediate prior post, I swapped the Dlink router for an Asus RT16N also in access point mode and  port checker  still reports that 4662 is blocked.  However,  I observe  a eD2K high id on aMule  on 4662 with firestarter enabled.   Perhaps it will be intermittent due to ISP quality issues but structurally, I suspect I have the best  possible result.     I will give the current set up some time before I try to swap back the  DLink but notwithstanding the outcome, the configuration I currently have may be optimal.

[woutermense]

aMule (or something) needs to be running and listening at the port you want to test or else the test will fail at the final level, because nothing responds to the tester. If you like you could run additional tests with netcat like this:

Code: [Select]

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.

[dealcorn]

In this context, the reason I care about port forwarding and port unblocking is to get a high id.  I now have a high id  and am happy, but I may be getting confused by protocol obfuscation.  While ED2K info shows a high id on 4662, the aMule log show connections on obscure ports like 1616  which is neither forwarded not unblocked by firestarter.  In Amulegui the obscure port connection is reported which suggests forwarding is not working correctly,.    Is this typical behavior?

[Kry]

Ports you connect to/from are random. The forwarded port is only to contact you.