Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
mlDHT bug: changes port after a while
#1
5401_b03 + mlDHT 1.5.5

After some hours run something borked in mlDHT (vuze?)

Tons of missguided traffic on wrong port 1047
Since the last 10h 58k+ packets on wrong port

example from my firewall:
udp      17 127 src=172.16.0.104 dst=119.95.3.214 sport=49132 dport=39189 packets=2 bytes=190 src=119.95.3.214 dst=176.10.212.217 sport=39189 dport=1047 packets=1 bytes=94 [ASSURED] mark=0 use=2 *1
udp      17 116 src=119.95.3.214 dst=176.10.212.217 sport=39189 dport=49132 packets=1 bytes=131 src=172.16.0.104 dst=119.95.3.214 sport=49132 dport=1143 packets=1 bytes=307 mark=0 use=2

My mlDHT port is 49132 and the guy send from 39189 but somehow he "thinks" the target port is 1047 and when my mlDHT "thinks" his recieve port is 1143....when he send it on 39132!!

(*1 = auto assured because my machine send it)

 

 
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Vuze sends port=0 to trackers when both IPv4 and IPv6 tracker/announce exists supercoolman 0 20 Yesterday, 05:06 PM
Last Post: supercoolman
  Torrents will not stop on command bug neinome 2 1,508 10-22-2017, 06:25 AM
Last Post: Havokdan



Users browsing this thread: 1 Guest(s)