aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: bind to another port than 0.0.0.0  (Read 3203 times)

Codeman

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 5
bind to another port than 0.0.0.0
« on: November 08, 2006, 10:54:35 AM »
Hi,

I tried to take a fast look into the sources to implement an option which realizes an option for  setting the intzerface which aMule should bind to (if you have mor than one interface).

But I didn't found the right place where to do this... I think this would be very simple to implement if someone knows where to insert this in the code.  :baby:

Regards, Code
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
RE: bind to another port than 0.0.0.0
« Reply #1 on: November 08, 2006, 02:34:40 PM »
Codeman,

This has already been discussed here, if you search you will find messages about this.

Why would you want aMule to bind to a specific interface? Binding to 0.0.0.0 means it receives from any interface, even if you have more than one, you are bound to all of them.

Cheers!
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: bind to another port than 0.0.0.0
« Reply #2 on: November 08, 2006, 07:57:59 PM »
Didn't I do that already? If not, I can do it in like 5 seconds. It's done for EC and amuelweb at least.
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: bind to another port than 0.0.0.0
« Reply #3 on: November 09, 2006, 04:28:31 AM »
Well, I still don't understand what is the advantage. Ok, any connections initiated from the outside world will be on the bound interface, but connections initiated by the client will have to submit themselves to the route the system will choose. Maybe worse, you may end up sending something in one interface and receiving the answer on the other interface. Linux discards this kind of reply by default, you need to configure your kernel to accept this.

Cheers!
Logged

leuk_he

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 25
Re: bind to another port than 0.0.0.0
« Reply #4 on: November 10, 2006, 03:16:06 PM »
It is useful with people with 2 internet connections. (which happens more and more with all those open wireless networks). The the ed2k protocol only allows one ip per cleint......

(and i do not knwo if amule supports it, or just lacks a proper gui for setting the bindip)
« Last Edit: November 10, 2006, 03:16:53 PM by leuk_he »
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: bind to another port than 0.0.0.0
« Reply #5 on: November 15, 2006, 05:03:27 AM »
leuk_he,

aMule does support it, code was already implemented, GUI was missing.

Tomorrow CVS shall have the proper configuration in "Preferences->Connection->Bind Address".

Codeman, please give it a try.

Cheers!
Logged