I am on a network with a cloaked hostname. When I use bouncedcc, and try to dcc chat, I am seeing that the other side receives a request to connect to the cloaked hostname. It should send the real IP of the bouncer (unless useClientIP is set).
I am on a network with a cloaked hostname. When I use bouncedcc, and try to dcc chat, I am seeing that the other side receives a request to connect to the cloaked hostname. It should send the real IP of the bouncer (unless useClientIP is set).
<!-- github-sync-id:789440501 -->
I am seeing that the other side receives a request to connect to the cloaked hostname
Do you have some raw traffic showing this? The DCC protocol cannot really transfer hostnames, I thought...
> I am seeing that the other side receives a request to connect to the cloaked hostname
Do you have some raw traffic showing this? The DCC protocol cannot really transfer hostnames, I thought...
<!-- github-comment-id:764784926 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I am on a network with a cloaked hostname. When I use bouncedcc, and try to dcc chat, I am seeing that the other side receives a request to connect to the cloaked hostname. It should send the real IP of the bouncer (unless useClientIP is set).
Also, maybe this can be merged with #966.
Do you have some raw traffic showing this? The DCC protocol cannot really transfer hostnames, I thought...
Just vaccuming some old issues - i don't have dcc problems anymore.