Official eMule-Board: Testing Emule 0.60 (completed) - Official eMule-Board

Jump to content


  • (17 Pages)
  • +
  • « First
  • 15
  • 16
  • 17

Testing Emule 0.60 (completed) Community version

#321 User is offline   stoatwblr 

  • Member
  • PipPip
  • Group: Members
  • Posts: 38
  • Joined: 15-February 13

Posted 20 June 2021 - 10:40 AM

New bug: Bindaddr

This is only binding the TCP port. The UDP ports (TCP+4 and kad port) are binding to 0.0.0.0

$ netstat -apn | grep -i wine
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)

tcp 2 0 10.16.128.127:6822 0.0.0.0:* LISTEN 1264795/wineserver6

udp 0 0 0.0.0.0:6826 0.0.0.0:* 1264795/wineserver6
udp 134912 0 0.0.0.0:6832 0.0.0.0:* 1264795/wineserver6

The significance of this is that if the host has multiple default route metrics the program will likely select the lowest one and send using the "wrong" IP
0

#322 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4840
  • Joined: 13-May 07

Posted 20 June 2021 - 12:46 PM

holysmoker,
it would be great if you answer to the question above: Does it differ from 0.50a?

stoatwblr,
external IP is unknown when a socket is created; especially in case of multiple network adapters.
0

#323 User is offline   stoatwblr 

  • Member
  • PipPip
  • Group: Members
  • Posts: 38
  • Joined: 15-February 13

Posted 21 June 2021 - 04:40 PM

View Postfox88, on 20 June 2021 - 01:46 PM, said:

stoatwblr,
external IP is unknown when a socket is created; especially in case of multiple network adapters.


You are correct, however if the bindaddr directive is being used then the TCP/UDP and Kad UDP ports should _all_ use them.

The directive specifically exists for the purpose of allowing manual control of the IP address the program may otherwise use or listen on

(there are good reasons why you may want to bind the webUI port to other interfaces, such as for internal network control etc, so it's best left listening on 0.0.0.0 or have a separate directive, as amule does)
0

#324 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4840
  • Joined: 13-May 07

Posted 22 June 2021 - 12:24 PM

View Poststoatwblr, on 21 June 2021 - 07:40 PM, said:

if the bindaddr directive is being used then the TCP/UDP and Kad UDP ports should _all_ use them.

Does it look different if Windows build of amule was run under Wine?
0

#325 User is offline   stoatwblr 

  • Member
  • PipPip
  • Group: Members
  • Posts: 38
  • Joined: 15-February 13

Posted 22 June 2021 - 01:22 PM

View Postfox88, on 22 June 2021 - 01:24 PM, said:

View Poststoatwblr, on 21 June 2021 - 07:40 PM, said:

if the bindaddr directive is being used then the TCP/UDP and Kad UDP ports should _all_ use them.

Does it look different if Windows build of amule was run under Wine?


It's no longer built for windows (*nix/macos only). I'll check with some older binaries and get back to you

...
This is using a 2.3.2 contributed binary

netstat -apn | grep :46[0-9][0-9] | grep wine
tcp 0 0 10.172.65.13:4662 0.0.0.0:* LISTEN 1152762/wineserver6
udp 0 0 0.0.0.0:4665 0.0.0.0:* 1152762/wineserver6
udp 0 0 0.0.0.0:4672 0.0.0.0:* 1152762/wineserver6

So it looks like this is a wine/windows issue

Additionally, TCPdump shows no UDP traffic on the "unwanted" IP addresses(*), so it looks to be a false alarm


(*) The test host has one main address using nm-team and a bunch of macvlan attachments behind it with real world IPv4 addresses (doing this gives each interface its own mac address which simple IP aliasing doesn't do - that makes firewalling much easier)

This post has been edited by stoatwblr: 22 June 2021 - 01:39 PM

0

#326 User is offline   stoatwblr 

  • Member
  • PipPip
  • Group: Members
  • Posts: 38
  • Joined: 15-February 13

Posted 22 June 2021 - 01:49 PM

Harking back to an earlier subtopic - the "bogus" emule 0.6 of many years ago - and MorphXT etc blacklisting it

I've verified (side by side comparions of connections) that MorphXT users still comprise a good chunk of the ed2k cloud and are blacklisting all emule 0.6* that they see

It's going to be virtually impossible to get people to update their MorphXT builds even if notices are posted on all the usual forums


As such, in order to prevent continued network fragmentation: I strongly urge renaming to 0.7 and skipping any further use of the 0.6 name
0

  • Member Options

  • (17 Pages)
  • +
  • « First
  • 15
  • 16
  • 17

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users