aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Ports forwarded/allowed, still low ID.  (Read 2458 times)

xaxat

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Ports forwarded/allowed, still low ID.
« on: June 02, 2007, 07:41:48 PM »
A couple of weeks ago I installed aMule. I set it up so ports 4672 UDP and 4662 TCP were forwarded. I used Firestarter to allow inbound traffic on port 4662. When I first tested the set up at http://www.amule.org/testport.php, I got the green everything is OK message and for the first couple of days I got Hi IDs.

For the last week though, I only get low IDs and flunk the port test. I haven't changed anything with the set up. Could it be that my ISP (Verizon) has only now decided to block those ports, or is it something else?
Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Ports forwarded/allowed, still low ID.
« Reply #1 on: June 03, 2007, 12:11:27 PM »
Hello xaxat, I feel something like that when I leave my network a lot of time without restarting my router; I think ISP do it that for break traffic for networks without supervision. Please try resenting your router so IP changes (and cross your fingers!  :))

Do you stop your machine or it is running continously?

Byeee!!!
Logged

HyperNode

  • Guest
Re: Ports forwarded/allowed, still low ID.
« Reply #2 on: June 03, 2007, 07:40:09 PM »
Well keep in mind these day it is more complex this is how my setup is. Now my modem does act as a firewall/router enable NAT trigger on selected port and forward all inbound and outbound to a selected local address. Now I also have a swtich board which is another type of firewall that is connected to a AMD 750mhz system that act as a packet sniffer. Then check your OS now I am using Suse which has its own firewall maybe if you are using diff distro you are using IPChan or IPTable now mostly all will allow outbound traffic and block out inbound.

This is my total setup:
WAN(Internet 0.0.0.0)> Modem(192.168.1.254)> Switch(192.168.0.1)> Sniffer(192.168.0.2)> Local systems(192.168.0.3-192.168.0.100)> OS Firewall (OFS, IPTable, IPChan)

Try to track it down by each hoops now if it supports logging check it. Start with the modem ect till you get to OS. This is just my home networking lol and we are not yet in to tunneling and encryption.

I will post my rules script maybe confusing for you so ill try to explain in words:
1. ED2K-Client: Allow traffic (inbound/outbound) on TCP port 4662  from selected Sys on trigger.
2. ED2K-Server: Allow traffic (inbound/outbound) on UDP port 4665 from selected Sys on trigger.
3. ED2K-xMule: Allow traffic (inbound/outbound) on UDP port 4672  from selected Sys on trigger.
« Last Edit: June 03, 2007, 07:50:23 PM by HyperNode »
Logged

xaxat

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: Ports forwarded/allowed, still low ID.
« Reply #3 on: June 04, 2007, 02:23:55 AM »
Thanks for the replies, Crakem I have reset my router during this period for reasons unrelated to my amule problem and still get low IDs. HyperNode, your reply is a bit technical for me, but amule actually worked when i had my router's firewall set at medium. Since I have had problems, I tried it with the router firewall off and on with no luck. I'm running Ubuntu, which I believe uses IPTable and I think I have that set up right using Firestarter.
Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Ports forwarded/allowed, still low ID.
« Reply #4 on: June 04, 2007, 04:35:30 PM »
Hello, I read your post slowly and I don't understand how you get Hi-ID if you haven't got UDP port open too (?)
I suppose you have read wiki: http://www.amule.org/wiki/index.php/Get_HighID and you have allowed inbound traffic at your firewall and have all router's ports open. If you have that; please try 1820 TCP and 1821,1822 (both) UDP (another ports that you have now, that ports listed are my ports)

Byee!!
Logged