Outline · [ Standard ] · Linear+ Define outgoing ports, Define outgoing ports

[Zom]

From what I have read eMule+ uses the ephemeral ports range for outgoing connections.

In order to ensure specific routing for outgoing traffic through an alternate public IP, so that I can ensure correct routing for incoming traffic trough that same public IP, I would like to specify the range of ports used for outgoing UDP and TCP connections to a set different from the standard ephemeral port range.

How can I do this?

This post has been edited by Zom: May 3 2010, 04:22

[muleteer]

eMule Plus only assigns random ports on first install. After that they remain the same unless changed manually.

To change, click preferences, and then the connections tab. Change TCP and UDP ports as desired. Advisable to restart the client. Some firewalls need you to reboot the computer as well.

[Zom]

eMule Plus only assigns random ports on first install. After that they remain the same unless changed manually.

Thanks - but I am talking about outgoing ports, not incoming ports. I know how to set the "client" ports and what that setting does. Those settings do not influence the "outgoing" traffic ports.

Any other ideas?

[Aw3]

It uses what system networking stack is allocating by default -- kind of arbitrary port number for outgoing connections.
There's no way to specify a range of the ports to use for this application.

The other think I don't understand is if you want to send packets over 2 different connections out, how do you expect to get anything back?

Or maybe you just want to use a particular connection for the eMule Plus only. In this case it uses the default system connection to communicate.

[Zom]

use a particular connection for the eMule Plus only

Sort of. I want to use a separate public IP for all P2Ps, including eMule Plus.

To do that for eMule Plus I need to steer all outgoing connections via that IP so that the responding incoming connections use the same IP. I can do it for servers by specifying routings for their IPs, but I cant do it for other clients because I cant know their IPs and I cant route all ephemeral ports. It would work if I could route a specified port range.

Is there any chance this feature could be included in a future version? I think others would use it if it was there.

[Aw3]

One thing is too have default system connection for P2P . That way it will be automatically.
The other thing which can be done is to bind application connections to the particular interface through its IP address. Official eMule has some code to do that, but I can't say how to use it (it could be through manual editing of preferences.ini file).

Technically, it can be ported, but I personally don't even have an environment to test it.

[Zom]

Thanks for taking an interest.

One thing is too have default system connection for P2P . That way it will be automatically.

Unfortunately, without knowing the ports used, P2P content can only be determined AFTER the connection is made. That is OK for shaping and blocking, but not for routing.

The other thing which can be done is to bind application connections to the particular interface through its IP address. Official eMule has some code to do that, but I can't say how to use it (it could be through manual editing of preferences.ini file).

That sounds like an ideal solution. If eMule Plus could be told which gateway/publicIP to use it would solve my problem elegently.

Technically, it can be ported, but I personally don't even have an environment to test it.

I do. If you want to throw something at me to test that feature - please do. I am willing to spend as much time as is reasonably required to achieve a solution.

[Aw3]

I will take a look, but I don't promise.

[Zom]

I will take a look, but I don't promise.

That is all I can ask. Let me know if I can help.

[Aw3]

I have some code ready for you to try. Do you build yourself or you need a binary?

[Zom]

I have some code ready for you to try. Do you build yourself or you need a binary?

Most excellent! That was quick!

I don't normally build, so it would be great if you could do a binary for me to test.

[Aw3]

Here's the build.
You need to add BindAddr=<IP> to the [eMule] section of the preferences.ini.

I moved the following connections to be on the specific interface:
- TCP/UDP p2p
- TCP/UDP server communication
- WebServer
- IRC
- LanCast
- MobileMule

I'm not sure how much you can try, but it would be nice if you can try at least IRC and WebServer.

Please post here how it goes.

This post has been edited by Aw3: May 16 2010, 20:04

[Zom]

Please post here how it goes.

Installed the new version tonight. So far it works.

I havent tried everything yet, but basic server and p2p comms binds as expected and can be routed as required.

The webserver appears on the bound IP as expected and can be NATted accordingly.

I have never used IRC, LanCast or MobileMule. I will have a readup and see if I can readily test them.

So far very good.

[Zom]

Please post here how it goes.

MobileEmule works as expected, appears on the bound IP and can be NATted.

This post has been edited by Zom: May 16 2010, 15:14

[Aw3]

I don't think you can really test LanCast, but for IRC you can just click Connect button on the IRC page. If you get the list of channels and connect to the default one (emule+, if I remember correctly), we can assume it works.

Thanks a lot for trying it out.