"
[SOLVED]
Ok, so, it's my fault for misunderstanding how the P2P clients manage their ports and their communications with servers.
First of all, here's how to set up a generic port forwarding rule for a P2P client:
- Firewall -> NAT -> Port Forward -> Add a new rule:
> Interface: WAN
> TCP/IP Version: IPv4
> Protocol: TCP/UDP (in Torrent's case)
> Destination: WAN address
> Destination port range: (other), use the port that you set in the P2P client
> Redirect target IP: the IP of the computer that hosts the P2P client
> Redirect target port: (other), use the port that you set in the P2P client
> Description: name this rule in a relevant way so to recognise it at a glance
> Filter rule association: Add association filter rule (firewall rule that will be created automatically according to this port forwarding)
To be NOTED: while Torrent lets you set a single port number for both TCP and UDP, eMule allows you to pick two separate ones; hence you're supposed to set two forwarding rules, one for TCP and one for UDP.
Alternatively, you can fill the two fields with the same port number and make a single TCP/UDP rule; actually, I'm just relaying what I've picked up from a single post among the tens I perused: I'm not 100% sure this would work, maybe there's a reason why they built the interface with two separate fields.
You can test it yourself, if you wish, it's not like you're gonna break the Internet ("IT Crowd" reference).
My mistake was assuming that P2P clients use specific, pre-established ports on the WAN side that must be NAT'd toward the port(s) declared in the client itself.
In my defence, I have a fever, a sore throat and I feel absolutely wasted because of all the coughing of the last week. ^^'
My most sincere gratitude to the two users of the "homelab." Discord server that showed an outstanding patience in helping me to achieve englightenment.
Ok, so, it's my fault for misunderstanding how the P2P clients manage their ports and their communications with servers.
First of all, here's how to set up a generic port forwarding rule for a P2P client:
- Firewall -> NAT -> Port Forward -> Add a new rule:
> Interface: WAN
> TCP/IP Version: IPv4
> Protocol: TCP/UDP (in Torrent's case)
> Destination: WAN address
> Destination port range: (other), use the port that you set in the P2P client
> Redirect target IP: the IP of the computer that hosts the P2P client
> Redirect target port: (other), use the port that you set in the P2P client
> Description: name this rule in a relevant way so to recognise it at a glance
> Filter rule association: Add association filter rule (firewall rule that will be created automatically according to this port forwarding)
To be NOTED: while Torrent lets you set a single port number for both TCP and UDP, eMule allows you to pick two separate ones; hence you're supposed to set two forwarding rules, one for TCP and one for UDP.
Alternatively, you can fill the two fields with the same port number and make a single TCP/UDP rule; actually, I'm just relaying what I've picked up from a single post among the tens I perused: I'm not 100% sure this would work, maybe there's a reason why they built the interface with two separate fields.
You can test it yourself, if you wish, it's not like you're gonna break the Internet ("IT Crowd" reference).
My mistake was assuming that P2P clients use specific, pre-established ports on the WAN side that must be NAT'd toward the port(s) declared in the client itself.
In my defence, I have a fever, a sore throat and I feel absolutely wasted because of all the coughing of the last week. ^^'
My most sincere gratitude to the two users of the "homelab." Discord server that showed an outstanding patience in helping me to achieve englightenment.
