New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advanced DC++ doesn't seem to work with PtokaX hubs--will there be testing/fixing? #249

Closed
dchmelik opened this Issue Jun 24, 2017 · 19 comments

Comments

Projects
None yet
2 participants
@dchmelik

dchmelik commented Jun 24, 2017

I said (then maksis replied: )

One says PtokaX DC Hub 0.5.2.1.

Thanks, that's what I wanted to know. I'm not aware of any special issues caused by that hubsoft, unless it has been configured to block transfers. The hubsoft is written for a legacy protocol though, which may cause different types of issues. You may always connect to the dev/support hub at adcs://web-dev.airdcpp.net:1511 and ask for someone to try browsing your filelist. [...]

So, no Advanced DC++ software I tried (AirDC++, EiskaltDC++, LinuxDC++) worked with those PtokaX hubs, but after conversation above, I was able to use AirDC++ web-client with the AirDC++ developers' hub just fine, then didn't do/change anything else until trying PtokaX hubs, and they put me in passive mode. This does seem to be a problem of the legacy protocol. Are there any plans to test that and see how AirDC++ could be fixed, or if just PtokaX is incompatible now, or if you have to do certain setup? (I tried all sorts of stuff, like running on ports only up to 32,000, or using port 412 for the two main things and 413 for TLS as descriptions of old protocols seemed to imply you should do.)

@maksis

This comment has been minimized.

Collaborator

maksis commented Jun 24, 2017

Ptokax is the hubsoft that I use for testing NMDC compatibility, so it should be working just fine. However, hubs use different settings that may also affect transfers. In how many Ptokax hubs have you tested downloading? Can you download from users in hub dchub://dc-united.sytes.net:4111 that I've confirmed to be working correctly with AirDC++?

@maksis maksis added the question label Jun 24, 2017

@dchmelik

This comment has been minimized.

dchmelik commented Jun 24, 2017

Two hubs earlier, now the one you mentioned. There I couldn't get a list from other passive users (unless it was going to take several more minutes than already) which according to one of the other hub administrators means I have a problem, i.e. am in passive mode (which it also says) so basically can't share much. So, I have the same problem there.

@maksis

This comment has been minimized.

Collaborator

maksis commented Jun 24, 2017

So you are passive in NMDC hubs but active in ADC hubs? That's new to me. Are you having the issue with other NMDC hubsofts? Hubs to test: johtajat.no-ip.org (Aquila), talsi.sytes.net (Verlihub)

Additional information that might be helpful (can also be sent privately in the dev hub):

  • Your full IPv4 connectivity settings
  • Full protocol messages including the hub connect process and initiating of the transfer connection (you can view those in the server console after starting the client with --cdm-hub and --cdm-client parameters)
@dchmelik

This comment has been minimized.

dchmelik commented Jun 25, 2017

Situation is same on those two hubs: I was passive, couldn't get file list from passive users after several minutes. These are my IPv4 settings: router with static IP address 206.63.237.146 (which my PC also has when I check sites that give your IP address,) and entered in AirDC++ web-client ‘External/WAN IP.’ My PC's LAN address is 192.168.1.101 (which I have set static from the router) and shown in ifconfig, and entered in AirDC++ web-client ‘bind address.’ I opened ports 30000 (TCP & UDP) and 30001 (TCP) in the router and entered those for the three AirDC++ ports (well, 30000 used for the first two and 30001 for TLS.)

@maksis

This comment has been minimized.

Collaborator

maksis commented Jun 25, 2017

I'd like to get the protocol messages and possibly your DCPlusPlus.xml file as well as I don't currently know that what's happening there

@maksis

This comment has been minimized.

Collaborator

maksis commented Jun 25, 2017

Oh, and obvious question: does this also happen if you connect to those hubs with a clean installation without any manual config?

@dchmelik

This comment has been minimized.

dchmelik commented Jul 7, 2017

Yes. Your development hub doesn't list me as passive, but the ones I tried, and you suggested above, do.

@dchmelik

This comment has been minimized.

dchmelik commented Jul 10, 2017

I found the file, but don't know where those messages are; what should I do next?

@maksis

This comment has been minimized.

Collaborator

maksis commented Jul 10, 2017

I found the file, but don't know where those messages are

See #249 (comment)

@dchmelik

This comment has been minimized.

dchmelik commented Jul 11, 2017

So apparently you mean a standard OS terminal console with a shell, not a console within airdcppd... Ok; I'll look at that. Is it safe to upload that XML file as it is (only, it doesn't have my password, right?) in another comment here? (or you want me to use that Github pastebin?)

@maksis

This comment has been minimized.

Collaborator

maksis commented Jul 11, 2017

Is it safe to upload that XML file as it is (only, it doesn't have my password, right?)

Web server passwords aren't stored in that file but you might still want to skim it through. I wouldn't paste large text files directly into comments but it's ultimately up to you.

@dchmelik

This comment has been minimized.

dchmelik commented Jul 12, 2017

@maksis

This comment has been minimized.

Collaborator

maksis commented Jul 12, 2017

There is no protocol communication in the log. Some clarifications to comment #249 (comment):

  • Launch the application with command airdcppd --no-auto-connect --cdm-hub --cdm-client > output.txt
  • Connect to a hub that is causing issues. To minimize the amount of extra protocol messages, you should rather connect to a small hub. Note that all information exchanged between the application, hubs and other clients will be logged so I don't recommend testing with the most secret hub you have (or with hubs where you have a registered account).
  • Quit the application and upload the generated log
@maksis

This comment has been minimized.

Collaborator

maksis commented Jul 12, 2017

Update: launch with airdcppd --no-autoconnect --cdm-hub --cdm-client > output.txt that will skip the hub auto-connect correctly (the parameter name listed in --help is incorrect)

@dchmelik

This comment has been minimized.

dchmelik commented Jul 24, 2017

Oops, ok, I replaced my old gist log of that with a new file that has the debugging output and connects to all the hubs you suggested test, including one with PtokaX.

@dchmelik

This comment has been minimized.

dchmelik commented Aug 20, 2017

Did anyone check my revised file? Is it taking a lot of debugging, or I did something wrong, or people forgot?

@maksis

This comment has been minimized.

Collaborator

maksis commented Aug 20, 2017

The active flag is being sent correctly to the hub and the hub forwards it correctly as well, so everything looks normal there.

Additional questions:

  • What kind of system are you running the client on (operating system, CPU...)?
  • Are you using the precompiled binary or have you compiled one by yourself? (you could test both)
  • Are you able to test the app on other systems? In case you have a Windows machine available, have you tested the Windows app?
@dchmelik

This comment has been minimized.

dchmelik commented Aug 20, 2017

I'm running precompiled airdcppd-webclient on a stable major GNU/Linux OS distribution with i6700K CPU. Before, I had compiled airdcppd-webclient, realized I didn't have to, then uninstalled & reinstalled. I can't test on anything else now... maybe a BSD, later, if available.

@maksis

This comment has been minimized.

Collaborator

maksis commented Oct 23, 2018

Next version should display the the connectivity mode correctly for own user in NMDC hubs (I'm not sure if actual transfers were affected)

@maksis maksis added the bug label Oct 23, 2018

@maksis maksis added this to the 2.4.0 milestone Oct 23, 2018

maksis added a commit that referenced this issue Oct 23, 2018

Squashed 'airdcpp-core/' changes from 20c545f30..c2c19ea58
c2c19ea58 Ensure that there's a whitespace after the nick in NMDC chat messages
bc80bdafa Fix incorrect total file count in NMDC partial lists
fa2588236 Cleanup
f563b7b26 Fix passive mode detection for own user in NMDC hubs (closes #249)
de35b8ab2 Remove UI code from OnlineUser

git-subtree-dir: airdcpp-core
git-subtree-split: c2c19ea5806cd23f23ae508ef78020948c777b35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment