aMule Forum
English => aMule Help => Topic started by: FlyHigh on April 23, 2016, 02:16:23 PM
-
I follow this wiki page:
http://wiki.amule.org/wiki/Firewall
For setting up aMule, I'm tutored to make a bash script including lines below:
iptables -t nat -A PREROUTING -i $EXTIF -p tcp --destination-port $EMULEPORT -j DNAT --to-destination $EMULEHOST:$EMULEPORT
iptables -t nat -A PREROUTING -i $EXTIF -p udp --destination-port $EMULEUDP -j DNAT --to-destination $EMULEHOST:$EMULEUDP
iptables -t nat -A PREROUTING -i $EXTIF -p udp --destination-port $EMULEUDP2 -j DNAT --to-destination $EMULEHOST:$EMULEUDP2
as well as these three lines:
iptables -A FORWARD -i $EXTIF -o $INTIF -p tcp --dport $EMULEPORT -d $EMULEHOST -j ACCEPT
iptables -A FORWARD -i $EXTIF -o $INTIF -p udp --dport $EMULEUDP -d $EMULEHOST -j ACCEPT
iptables -A FORWARD -i $EXTIF -o $INTIF -p udp --dport $EMULEUDP2 -d $EMULEHOST -j ACCEPT
I save the script file and then execute it, but I get these error messages:
Bad argument `tcp'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `udp'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `udp'
Try `iptables -h' or 'iptables --help' for more information.
I can't figure out where the errors locate, frankly I know only a bit of scripts about iptables. Though '-p' implying protocol is absolutely legal in iptables usage. How come a protocal name right behind that indicator is a bad argument?
-
Did you read the page correctly? What are you trying to do? Just open the ports in IPTables?
TCP port 4662 is used for client to client transfer. (This is needed to obtain HighID on ED2K)
UDP port 4665 is used for global server queries.
UDP port 4672 is used for KAD and extended ED2K quires. (This is needed to obtain Ok status on KAD along side TCP 4662)
1) /sbin/service iptables save
This will dump the current table on file.
2) vi /etc/sysconfig/iptables
This will open IPTable config file with VI editior.
3) PRESS 'i'
This will enable INSERT mode so you can write to the file.
4) -A INPUT -p tcp -m state --state NEW --match multiport --dport 4662 -j ACCEPT
5) -A INPUT -p udp -m state --state NEW --match multiport --dport 4665,4672 -j ACCEPT
This will add multi-ports on IPTable. Place this under *filter section.
6) PRESS [Esc]
7) :wq
This will write to the file and exit VI editor.
8) service iptables restart
This will restart the IPTable service.
-
I wanna exactly open tcp port 4662, therefore my client can receive a high ID as I learn. I've forwarded accordingly ports in my router. And yet kad server log tells to open tcp port 4662 and udp port which I've configured to port 4673. I think firewall rule fail my client to get a high ID. Though there are a couple of tutorial pages for specific OS users inside that wiki page, I still found it doesn't work for my Fedora workstation after I've done what it demonstrates. Could someone do me a favour for telling me what I've got wrong?
-
Did you do what I told you?
-
Yes, I manage to do but things don't go on well and I can't fix.
Of this command, /sbin/service iptables save, I get this message:
'The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.'
And yet I don't understand how to place a configured IPTable file under *filter section. Do you mean the filter table inside IPTable? Nevertheless, I don't know how to do that.
Another problem is when I type in 'service iptables restart', it tells:
'Redirecting to /bin/systemctl restart iptables.service
Failed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.'
Thanks to you
-
Ok ill make this very easy, open cli and as root type these cmds below:
1: systemctl enable iptables
2: systemctl start iptables
3: iptables -F
4: iptables -A INPUT -p tcp -m state --state NEW --match multiport --dport 4662 -j ACCEPT
5: iptables -A INPUT -p udp -m state --state NEW --match multiport --dport 4665,4672 -j ACCEPT
6: /sbin/iptables-save
7: iptables -L -v -n --line-numbers
This will enable and start IPTables and as I don't know what you did so it will flush all current rules and then add the ports. Which after you will save and you can view it was added. Post back if you still have problem.
-
Problem occurs just from the first command line:
'systemctl enable iptables
Failed to execute operation: No such file or directory'
I make it a go as a root user as you told.
Thank you by the way.
-
From your first post I assumed you disabled firewalld and installed iptables. So in your case if you didn't then as root using YUM install it.
1: yum install iptables
2: yum install iptables-services
This will install iptables and systemd scripts for iptables services. After its installed repeat the last post and post back if you still have problems.
-
I've installed those two packages and continue with your instructions. Then new problems occur:
'systemctl enable iptables
Created symlink from /etc/systemd/system/basic.target.wants/iptables.service to /usr/lib/systemd/system/iptables.service.'
I thought the process above is not a problem somehow. Rather this proceeding:
'systemctl start iptables
Job for iptables.service failed because the control process exited with error code. See "systemctl status iptables.service" and "journalctl -xe" for details.'
Therefore I type in "systemctl status iptables.service" and then I get lines of report:
'systemctl status iptables.service
● iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2016-04-24 19:19:05 CST; 50s ago
Process: 320 ExecStart=/usr/libexec/iptables/iptables.init start (code=exited, status=1/FAILURE)
Main PID: 320 (code=exited, status=1/FAILURE)
Apr 24 19:19:03 localhost.localdomain systemd[1]: Starting IPv4 firewall with...
Apr 24 19:19:04 localhost.localdomain iptables.init[320]: iptables: Applying ...
Apr 24 19:19:05 localhost.localdomain iptables.init[320]: [FAILED]
Apr 24 19:19:05 localhost.localdomain systemd[1]: iptables.service: Main proc...
Apr 24 19:19:05 localhost.localdomain systemd[1]: Failed to start IPv4 firewa...
Apr 24 19:19:05 localhost.localdomain systemd[1]: iptables.service: Unit ente...
Apr 24 19:19:05 localhost.localdomain systemd[1]: iptables.service: Failed wi...
Hint: Some lines were ellipsized, use -l to show in full.'
It's tremendous information for me. I hope you can work it out. Always thanks to you.
-
Sorry I was asleep. But do the following cmds as root in cli and then do the original 7steps again after.
1) systemctl disable firewalld
2) systemctl stop firewalld
This will disable and stop the new firewalld so you can start iptables now thus no conflict. Post back if more problems.
-
Those two command lines are successfully proceeded. And then I go back to follow your instructions.Yet no problem occurs from the first line. Things appeared the same way after that:
'systemctl start iptables
Job for iptables.service failed because the control process exited with error code. See "systemctl status iptables.service" and "journalctl -xe" for details.'
I managed to see the details which reads almost no difference with last one:
'systemctl status iptables.service -l
● iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2016-04-25 11:47:21 CST; 23s ago
Process: 7735 ExecStart=/usr/libexec/iptables/iptables.init start (code=exited, status=1/FAILURE)
Main PID: 7735 (code=exited, status=1/FAILURE)
Apr 25 11:47:21 localhost.localdomain systemd[1]: Starting IPv4 firewall with iptables...
Apr 25 11:47:21 localhost.localdomain iptables.init[7735]: iptables: Applying firewall rules: iptables-restore: line 1 failed
Apr 25 11:47:21 localhost.localdomain iptables.init[7735]: [FAILED]
Apr 25 11:47:21 localhost.localdomain systemd[1]: iptables.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 11:47:21 localhost.localdomain systemd[1]: Failed to start IPv4 firewall with iptables.
Apr 25 11:47:21 localhost.localdomain systemd[1]: iptables.service: Unit entered failed state.
Apr 25 11:47:21 localhost.localdomain systemd[1]: iptables.service: Failed with result 'exit-code'.'
Thanks to you.
-
Maybe there is something wrong in the current iptable rules so try this.
1: iptables -F
2: iptables -A INPUT -p tcp -m state --state NEW --match multiport --dport 4662 -j ACCEPT
3: iptables -A INPUT -p udp -m state --state NEW --match multiport --dport 4665,4672 -j ACCEPT
Step 1-3 will flush the current iptable rules and implement rule 2/3. Then do the following:
4: iptables -L -v -n --line-numbers
5: /sbin/iptables-save
With step 4 you can verify that rules have been amended and with 5 you save it. Post back if more problems.
-
Things are going well. No more problems so far. What do I need to do right now? Anyway, great thanks to you.
-
Ok so whats the current status? Right now according to the first post you made you should have the ports open using IPTables.
-
Hi, HKM, how do you do?
I'm sorry that I'm absent for such a long time. However, I'm always concerned on this post and our discussion. :)
Today, I come to review our threads for closing my question which is still unresolved. :-[
I go to follow your instructions at very beginning. The reason for doing this is that the conditon is not the same as before, which will be explained below.
1) /sbin/service iptables save
This will dump the current table on file.
2) vi /etc/sysconfig/iptables
This will open IPTable config file with VI editior.
3) PRESS 'i'
This will enable INSERT mode so you can write to the file.
4) -A INPUT -p tcp -m state --state NEW --match multiport --dport 4662 -j ACCEPT
5) -A INPUT -p udp -m state --state NEW --match multiport --dport 4665,4672 -j ACCEPT
This will add multi-ports on IPTable. Place this under *filter section.
6) PRESS [Esc]
7) :wq
This will write to the file and exit VI editor.
8) service iptables restart
This will restart the IPTable service.
I'd like to say all stuff is OKAY. After that, I manage to reconnect aMule. Sadly, in Kad info section, it's told to open tcp port 4662 and in edk2 section, I can only get a low ID.
Should I get your help once again?
-
Well lets start from the top since I don't fully remember so little background. Now aMule is deployed on which platform? are you using full aMule or just daemon? Are the ports fully open on the machine and gateway (modem/router)?
-
My laptop is working with Fedora 23. I remembere I installed aMule from default repository using dnf. I feel like it's full version. Otherwise, how to differ? ;D
Now I gotta try to open specific ports in router. For modern, I'm afraid that I'm less than able to set up, cos its interface seems so professional. :-[
P.S.:
As I set to manage the setting in the router, I surprisely found that in UPnP setting, those three ports are being open automaticly for aMule using. Is that the way we gonna get it on?
-
So is it fully working? I wouldn't trust UPnP as its good as the firmware and you don't know how old it is if its very old switch/gateway. I highly recommend you take the time and setup full cone NAT/PAT and assign it to static LAN. Then check your config and make sure ports are fully open on the machine. You have already setup correct ports on the machine now just do it on the router/modem. If you need help we can start from top to bottom that way all will be taken care of as everything will have full passthrough.
-
I've read your last post and understand clearly. I'd leave UPnP utility aside as you recommend.
The most highly related feature I found in my router I would say is ' Virtual Server'. The router help manual explains that it used to be set up for internal servers being accessed by the rest of the network beyond the router. My question is that can I suppose my aMule is a kind of internal server planted in my system? And what kind of internal server is it? For setting purpose, server type is needed to be selected, including DNS, FTP, HTTP etc.
Thank you for your help.
-
Well the first step would be to make sure the PC is always given static LAN-IP by DHCP server running on gateway (modem/router). The point of that is to have static route for packets to be sent/received to single specified address which will be always same. Then you need to define the service port which would be normally name and port ranges. The last thing would be to enable the service and assign it to the same static LAN-IP.
What is the model number for your gateway? I can look up the web interface and tell you howto correctly setup PAT/NAT as majority of units now have IDS/SPI built in firewall which filters and by default blocks incoming connections while allowing outgoing.
-
My device is designed and sold in China, I'd love to tell you it's Mercury MW300R. Though I'm much afraid that you could not able to find the multi language interface of that model.
I gave a try to settup service ports as I've assigned my machined to a static IP address distrubuted from DHCP server. Strangely it's told port 4662 conflicts with other ports, but never tells what ports. I have no idea what that means.
P.S.(once again): I've located the problem. After I turned off UPnP service, I'm able to add service ports in virtual server section.
-
Did you open all 3 service ports required?
TCP port 4662 is used for client to client transfer. (This is needed to obtain HighID on ED2K)
UDP port 4665 is used for global server queries.
UDP port 4672 is used for KAD and extended ED2K quires. (This is needed to obtain Ok status on KAD along side TCP 4662)
Depending on how the device handles session timeout it will release used ports unless already defined. Which shouldn’t be problem if anything you can post me the screenshots. So add 3 new service with the ports defined and listed on top and then bind it to the static LAN-IP of the PC where aMule is deployed. Which should now have ports open since you enabled IPTables and opened them. If you still have problem post back we will change the ports just incase your ISP is blocking them since well known service ports.
-
How do I paste image on the forum? Does the forum have a paste bin? :-[
New founding: After I added three specifi ports in virtual server along UPnP service yet being turn off, aMule can't access UDP service. And global queries disable. So I decided to delete the contents associated with UDP ports. Surprisely to me, warnings to open UDP ports disappear and global queries resume normal. To conclude, I'd like to say that setting up in virtual server doesn't make any sense, otherwise it's drawback to aMule's running. Is it the same way to the TCP port? If so, configuring virtual server is unnecissary. The problem must be in other ways. Let me guess, is it blocked by ISP as you supposed in your last post?
-
When you post look at the bottom you will see attachment, just browse to the image file or you can upload it to image hosting site.
-
Thank you for your help, again and again.
I think it's not necessary to upload image to be reviewed right now. Have you ever read my last modified(usually, ;)) post?
-
Is there any details regarding the functionality of 'virtual server'. Normally you would see port forwarding section and all you have to do is define it by name (ex: amule) and select the type of protocol (ex: tcp) and port (ex: 4662). Once the rule is defined then you enable that service and forward it to a selected PC which would have its own LAN-IP. Far as ISP blocking goes that we can rule out after you went ahead and did everything and opened the ports. I want you to take screenshots of your menu hopefully its English.
-
I provided you screenshots from my own end so you can better see and understand how ports scheme are setup. As each device connected has to have it set for it to be fully functional before it even reaches the machine. As you can see from my modem/switch/router.
-
Comparing my router screenshot with your modem's, besides the language factor, are they highly likely? At least I think so. The most obvious ever difference is the service name area in my router is unable to be named.
-
Well that seems to be similar section. Now the PC thats using aMule make sure its IP is 192.168.10.103 for now try connecting to ED2K network. Also can you do 'netstat -ntap' and paste me the output here from your command terminal so I can see if ports are open.
-
Below is the output copy of command:
netstat -ntap
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:50000 0.0.0.0:* LISTEN 3488/amule
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:4662 0.0.0.0:* LISTEN 3488/amule
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN -
tcp 0 0 192.168.10.102:59406 83.47.229.139:38787 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:42072 54.213.112.246:443 TIME_WAIT -
tcp 1 1 192.168.10.102:37970 93.156.34.190:85 LAST_ACK -
tcp 0 0 192.168.10.102:56858 5.224.24.217:34341 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:39496 54.182.5.52:443 ESTABLISHED 3556/firefox
tcp 0 1 192.168.10.102:49620 199.30.80.32:80 SYN_SENT 3556/firefox
tcp 0 0 192.168.10.102:58414 87.14.201.108:4665 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:40892 36.237.120.247:12345 ESTABLISHED 3488/amule
tcp 0 1 192.168.10.102:46964 74.125.23.113:443 SYN_SENT 2062/chrome
tcp 0 0 192.168.10.102:50054 95.62.85.91:4662 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:52546 193.153.166.112:12047 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:40564 90.127.44.35:37215 TIME_WAIT -
tcp 1 1 192.168.10.102:59944 178.113.106.249:49152 LAST_ACK -
tcp 0 0 192.168.10.102:60408 54.148.104.15:443 ESTABLISHED 3556/firefox
tcp 0 0 192.168.10.102:41358 46.27.150.106:61473 ESTABLISHED 3488/amule
tcp 0 226 192.168.10.102:45172 61.70.212.209:4662 ESTABLISHED 3488/amule
tcp 0 1 192.168.10.102:49262 46.82.174.68:443 SYN_SENT 2062/chrome
tcp 0 1 192.168.10.102:45454 216.34.181.96:80 LAST_ACK -
tcp 0 1 192.168.10.102:49624 199.30.80.32:80 SYN_SENT 3556/firefox
tcp 0 0 192.168.10.102:38982 104.16.54.15:443 ESTABLISHED 2062/chrome
tcp 0 0 192.168.10.102:40836 83.61.161.155:51261 ESTABLISHED 3488/amule
tcp 0 32 192.168.10.102:44682 140.211.169.206:443 LAST_ACK -
tcp 0 0 192.168.10.102:48750 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.102:48756 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.102:55088 114.42.108.68:30778 TIME_WAIT -
tcp 0 1 192.168.10.102:48760 80.249.163.1:80 FIN_WAIT1 -
tcp 0 0 192.168.10.102:48754 80.249.163.1:80 TIME_WAIT -
tcp 1 1 192.168.10.102:42356 114.39.106.95:7555 LAST_ACK -
tcp 0 0 192.168.10.102:44926 58.152.239.18:13270 ESTABLISHED 3488/amule
tcp 0 1 192.168.10.102:55994 117.18.237.29:80 LAST_ACK -
tcp 0 1 192.168.10.102:48554 74.125.23.102:443 SYN_SENT 2062/chrome
tcp 0 1 192.168.10.102:49118 46.82.174.68:443 SYN_SENT 2062/chrome
tcp 0 0 192.168.10.102:39304 81.203.40.221:55954 ESTABLISHED 3488/amule
tcp 0 1 192.168.10.102:48748 80.249.163.1:80 FIN_WAIT1 -
tcp 0 1 192.168.10.102:57722 216.58.199.110:443 SYN_SENT 3556/firefox
tcp 0 0 192.168.10.102:40462 203.208.41.32:443 ESTABLISHED 3556/firefox
tcp 0 1 192.168.10.102:46962 74.125.23.113:443 SYN_SENT 2062/chrome
tcp 0 0 192.168.10.102:45166 190.247.196.237:58861 TIME_WAIT -
tcp 0 0 192.168.10.102:51754 121.175.242.150:6703 TIME_WAIT -
tcp 0 0 192.168.10.102:48752 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.102:43304 119.32.64.217:7551 TIME_WAIT -
tcp 0 0 192.168.10.102:52326 5.153.240.89:4662 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:52618 203.208.40.143:443 ESTABLISHED 2062/chrome
tcp 0 0 192.168.10.102:52798 82.238.199.129:12887 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:35464 93.150.166.73:7036 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:60404 54.148.104.15:443 ESTABLISHED 3556/firefox
tcp 0 0 192.168.10.102:47930 91.200.42.46:1176 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:52812 63.243.244.17:80 ESTABLISHED 3556/firefox
tcp 1 1 192.168.10.102:50278 113.12.83.5:80 LAST_ACK -
tcp 0 0 192.168.10.102:44588 88.21.105.104:85 TIME_WAIT -
tcp 0 1 192.168.10.102:57720 216.58.199.110:443 SYN_SENT 3556/firefox
tcp 0 0 192.168.10.102:52104 67.5.168.118:52966 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:51818 192.168.10.1:1900 TIME_WAIT -
tcp 0 1 192.168.10.102:36276 216.58.197.109:443 SYN_SENT 2062/chrome
tcp 0 0 192.168.10.102:36884 114.32.109.10:61587 TIME_WAIT -
tcp 0 1 192.168.10.102:48098 36.235.35.115:24011 FIN_WAIT1 -
tcp 0 0 192.168.10.102:56706 218.5.235.178:64205 TIME_WAIT -
tcp 0 0 192.168.10.102:48758 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.102:59470 209.132.181.28:443 ESTABLISHED 3369/reporter-urepo
tcp 0 0 192.168.10.102:54846 126.22.36.249:3338 FIN_WAIT2 -
tcp 0 0 192.168.10.102:45930 188.172.202.24:443 ESTABLISHED 3556/firefox
tcp 0 0 192.168.10.102:60406 54.148.104.15:443 ESTABLISHED 3556/firefox
tcp 0 0 192.168.10.102:37808 64.233.188.188:443 ESTABLISHED 2062/chrome
tcp 0 0 192.168.10.102:48754 82.52.48.61:16393 ESTABLISHED 3488/amule
tcp 0 1 192.168.10.102:54308 121.143.233.143:38805 FIN_WAIT1 -
tcp 1 1 192.168.10.102:34894 78.220.48.36:24771 LAST_ACK -
tcp 0 1 192.168.10.102:36278 216.58.197.109:443 SYN_SENT 2062/chrome
tcp 0 0 192.168.10.102:40308 203.208.41.56:443 ESTABLISHED 3556/firefox
tcp 0 0 192.168.10.102:35058 95.89.252.247:50000 TIME_WAIT -
tcp 0 0 192.168.10.102:52750 83.57.19.174:4661 ESTABLISHED 3488/amule
tcp 0 0 192.168.10.102:48714 80.249.163.1:80 ESTABLISHED 3556/firefox
tcp 0 32 192.168.10.102:44738 140.211.169.206:443 LAST_ACK -
tcp 0 0 192.168.10.102:33446 140.205.153.54:443 ESTABLISHED 2062/chrome
tcp 0 0 192.168.10.102:54292 5.2.166.185:28928 ESTABLISHED 3488/amule
tcp6 0 0 :::3306 :::* LISTEN -
tcp6 0 0 :::50000 :::* LISTEN 3488/amule
tcp6 0 0 ::1:631 :::* LISTEN -
By the way, my machine got some wrong with static IP address, so I changed it to dynamic for successful wi-fi connection.
-
Now I yet assigned my PC to a statci IP address 192.168.10.120, seemingly workable. :)
I do that command again:
netstat -ntap
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:50000 0.0.0.0:* LISTEN 3488/amule
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:4662 0.0.0.0:* LISTEN 3488/amule
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN -
tcp 0 0 192.168.10.120:50050 91.200.42.46:1176 TIME_WAIT -
tcp 0 0 192.168.10.120:39850 80.249.163.1:80 TIME_WAIT -
tcp 0 1 192.168.10.120:58732 59.24.3.173:443 SYN_SENT 3556/firefox
tcp 0 1 192.168.10.120:58734 59.24.3.173:443 SYN_SENT 3556/firefox
tcp 0 0 192.168.10.120:39852 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.120:39858 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.120:39854 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.120:39856 80.249.163.1:80 FIN_WAIT2 -
tcp 0 0 192.168.10.102:59470 209.132.181.28:443 ESTABLISHED 3369/reporter-urepo
tcp 0 0 192.168.10.120:39848 80.249.163.1:80 TIME_WAIT -
tcp 0 0 192.168.10.120:39842 80.249.163.1:80 ESTABLISHED 3556/firefox
tcp 0 0 192.168.10.120:34368 212.83.184.152:7111 ESTABLISHED 3488/amule
tcp6 0 0 :::3306 :::* LISTEN -
tcp6 0 0 :::50000 :::* LISTEN 3488/amule
tcp6 0 0 ::1:631 :::* LISTEN -
-
So whats your current status right now? Able to fully connect with HighID? I also see port 50000 open which is used by aMule for UPnP and forwards port so you may want to disable that as it seem to be enabled. Is your static LAN-IP set and MAC enforced? If you don't have that option you may want to do it locally from the PC under IPv4 custom settings.
-
Sadly to say, I've never ever got a HighID. I extremely wanna, but something is not okay yet.
-
So lets make sure and you understand this.
1) You set static LAN-IP and verified it on PC = same?
2) Open ports on gateway match same static LAN-IP = confirmed?
3) Ports are open on PC = confirmed?
What country are you in and who is the ISP? Do they allocate you IPv4/IPv6?
-
I'm in China and ISP is China Telecom. My internet connection is going up through PPPoE service. Actually I'm so dissapointed. Life in aMule is not easy for me. :( I'm even thinking is it more right to uninstall for ever?
-
Your problem is not aMule or ED2K but its THE great firewall of China and as majority of your ISPs run DPI switch to censor. I suggest for you do disable KAD network fully and connect to ED2K which will yield LowID. Which just means you will be able to use HighID user as source since other LowID to LowID is not still fully supported yet.
1) You can use NeoLoader which is eMule Mod that supports multi platform and has IPv6 and LowID2LowID support.
2) Connect aMule through VPN or run aMule on VPS remotely and then connect from PC to VPS via SFTP.